Wayne, since I seem to be blacklisted from your domain, I have to send
this piece publicly.
It contains a warning that trusted-forwarder lists IP addresses that the
respective domain owners do not authorize in their SPF records.
Good bye,
Radu.
Mail Delivery Subsystem wrote:
The original message was received at Sat, 7 May 2005 13:35:36 -0400
from smart.ohmi.org [192.168.1.151]
----- The following addresses had permanent fatal errors -----
<wayne(_at_)schlitt(_dot_)net>
(reason: 550-sender envelope address radu(_at_)ohmi(_dot_)org is locally
blacklisted here. If you)
----- Transcript of session follows -----
... while talking to mail.schlitt.net.:
DATA
<<< 550-sender envelope address radu(_at_)ohmi(_dot_)org is locally
blacklisted here. If you
<<< 550 think this is wrong, get in touch with postmaster
550 5.1.1 <wayne(_at_)schlitt(_dot_)net>... User unknown
<<< 503 valid RCPT command must precede DATA
------------------------------------------------------------------------
Reporting-MTA: dns; sun.ohmi.org
Received-From-MTA: DNS; smart.ohmi.org
Arrival-Date: Sat, 7 May 2005 13:35:36 -0400
Final-Recipient: RFC822; wayne(_at_)schlitt(_dot_)net
Action: failed
Status: 5.1.1
Remote-MTA: DNS; mail.schlitt.net
Diagnostic-Code: SMTP; 550-sender envelope address radu(_at_)ohmi(_dot_)org
is locally blacklisted here. If you
Last-Attempt-Date: Sat, 7 May 2005 13:35:38 -0400
------------------------------------------------------------------------
Subject:
trusted forwarder
From:
Radu Hociung <radu(_at_)ohmi(_dot_)org>
Date:
Sat, 07 May 2005 13:35:34 -0400
To:
wayne <wayne(_at_)schlitt(_dot_)net>
To:
wayne <wayne(_at_)schlitt(_dot_)net>
(OFF-LIST)
Thanks for providing this service and allowing me to use it.
I will no longer be using it, because many of the senders you list
publish their own SPF records now. Certainly the ones I care about do.
Also I would like to point out that your list is outdated, as some of
the SPF policies published by those domains are in conflict with your list.
For instance, you list some "trusted" hosts for amazon that Amazon
themselves do not authorize. Perhaps they did once, but if they no
longer have those IP addresses, or at least no longer use them.
The trust problem is that those IP blocks may be reassigned to other
entities, and based on the wide use of trusted-forwarder.org, they will
be able to get mail through as they are 'trusted' by default.
I think the trusted-forwarder list may maintain its usefulness only if
it were actively maintained, and thus would reflect the non-fixed nature
of network topologies.
I sent this message privately as I don't wish to dilute the reputation
of trusted-forwarder in public, since you provided this service in good
faith. :)
Regards,
Radu.