On Tue, 10 Dec 2002 dman(_at_)nomotek(_dot_)com wrote:
Specifically, RFC 2822 says:
Though other algorithms will work, it is
RECOMMENDED that the right hand side contain some domain identifier
(either of the host itself or otherwise) such that the generator of
the message identifier can guarantee the uniqueness of the left hand
side within the scope of that domain.
Unfortunately this practice is now causing spam problems of its own:
Harvesters mistake message-id strings for email addresses and send spam to
them. Of course it all bounces, but for a large domain that emits lots of
usenet postings (like, say, the University of Washington), I'll bet it
generates a huge amount of wasted network traffic. Heck, I'm the only
person in the brasslantern.com domain who ever posts to usenet or to
mailing lists, and I've been seeing spam aimed at message-id strings from
postings made five years or more ago.
If this is, as I suspect, the reason the scramble-message-id feature was
introduced, I don't think UW is going to back off easily.
On Tue, 10 Dec 2002, Nancy McGough wrote:
If anyone has any insight into how prevalent this (no valid
domain name in a Message-ID) is in spam-detection tools, please
let me know.
I know SpamAssassin does message-id analysis. I forwarded your original
message (including its message-id) to the spamassassin-talk mailing list
so that they'll be prepared to adapt the filter rules.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail