On Wed, Nov 22, 2006 at 10:07:08AM -0500, Stuart D. Gathman wrote:
I see the problem. This does complicate rejecting bogus DSN's. To
the extent that you need to accept these malformed DSN's and you
still want to protect yourself from forged bounces, there is not
much choice. This still doesn't interfere with postmaster sending
you ordinary mail, and you still reject bogus DSN's that don't meet
one of the three criteria you listed. The last two are particularly
annoying. What MTA's do this?
A quick look turns up the mostly the following:
From: Symantec_Mail_Security_for_SMTP(_at_)garveyintl(_dot_)com
Content-Type: multipart/report; report-type=delivery-status;
This isn't a DSN.
A DSN is sent using the null sender.
Alex
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to http://v2.listbox.com/member/?list_id=735