On Mon, 19 Sep 2005, David Woodhouse wrote:
On Sun, 2005-09-18 at 23:27 -0400, Stuart D. Gathman wrote:
The point is that I want to recognize messages that *ought* to
be DSNs (MFROM <>), but the sender was too clueless/rude to
actually send a DSN.
But those messages are still a mail loop waiting to happen. Surely it's
better to deal with them by hand, by reporting them as network abuse to
the upstream network provider?
Actually, by converting them to a real DSN, I am helping to prevent
a mail-loop.
Imagine that I was running brain-dead spam software like theirs.
I get a (non-DSN) message from mailer-daemon(_at_)clueless(_dot_)com telling me
I sent
them some spam. I recognize it as spam, and send *them* a (non-DSN)
message telling them they sent me some spam, which their program
recognizes as spam, and send me a (non-DSN) message telling me
I sent them some spam (which is actually true this time 'round),
which my program recognizes as spam...
Another motivation for converting postmaster(_at_)HELO to <> is that
I have encountered some MTAs out there that actually *convert*
<> to postmaster(_at_)HELO or mailer-daemon(_at_)HELO when they relay the mail.
This tries to undo that braindamage.
--
Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flamis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
-------
Sender Policy Framework: http://spf.pobox.com/
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/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com