From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] wierd spam
Date: Mon, 26 Nov 2007 15:24:19 -0800 [thread overview]
Message-ID: <4ACD6E20-064E-4500-BC97-1B98948A6F6F@orthanc.ca> (raw)
In-Reply-To: <20071126221404.GA21340@mero.morphisms.net>
On 2007-Nov-26, at 14:14 , William Josephson wrote:
> Probably some spammer mistaking message IDs like
> <5a07215f3e7e896f4b528a1838e78757@quanstro.net>
> for addresses.
Makes sense. The address harvesters are pretty stupid. E.g., I use
plus-detail addresses on my internet draft submissions, and regularly
see spam sent to rfc-crammd5@orthanc.ca as a result of harvesters not
parsing lyndon+rfc-crammd5@orthanc.ca correctly.
I'm slowly moving my mailing list subscriptions over to lyndon+@orthanc.ca
, to take advantage of the spammers lack of RE-fu :-) Sadly, there is
still quite a bit of list management software that also doesn't grok
full RFC[2]822 address syntax.
While the '+' hack helps circumvent the harvesting, bayesian filters
are your only practical defense.
--lyndon
next prev parent reply other threads:[~2007-11-26 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 22:08 erik quanstrom
2007-11-26 22:14 ` William Josephson
2007-11-26 22:24 ` erik quanstrom
2007-11-26 23:24 ` Lyndon Nerenberg [this message]
2007-11-28 3:18 ` sqweek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ACD6E20-064E-4500-BC97-1B98948A6F6F@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).