Andy said:
I don't know if it's just me, but I have noticed the amount of spam coming
into the email address I use for usenet posting has gotten out of hand in
the last few days
Recently I have been getting around 10 copies per hour of the trojan
"microsoft security update patch" - at 150kb each. I had to keep my email
client running all the time just to stop the mailbox on my server filling up
Decided enough is enough so I have killed the email address. :-(
Andy
I try not to use my real e-mail address in usenet postings. Recently, my ISP
changed the e-mail domain, and the reduction in spam has been *wonderful*.
Unfortunately, I did make one unprotected posting with the new address, and I
still get a trickle, but it's just one or two every couple of days instead of
over 100 a day--which I could trace to indiscreet posting in 1996!
Take a look at
http://www.spamgourmet.com for a nice way to have an invalid
address that does the least amount of harm to bandwidth and such. They also
provide for disposable e-mail addresses, so if you *do* have a reason to post an
address, it will only work for a little while.
Roedy Green posted something (last year, I think) on this subject. IIRC, here
are the points he made:
1. Obfuscation techniques are not very nice. If someone, in all innocence,
tries to e-mail you, and just click rather than actually looking at the address,
they don't find out for awhile. And their ISP, the backbone servers, and
possibly your ISP have to deal with dead mail. There is an old standard, not
very well known, that says you should add ".invalid" to the end of an invalid
e-mail address. Not all e-mail clients know about that standard, but for those
that do, the sender finds out immediately as soon as they click, so you do not
cause any addition to the glut on the Internet.
2. Obfuscation techniques do not work 100%. The simpler techniques are easy to
crack automatically, and (Roedy claimed in the posting), the spammers pay little
old ladies to scan manually and collect e-mail addresses, so they will figure
out the more elaborate schemes.
3. Invalid e-mail sent to spamgourmet.com is quietly sent to the bit bucket. Of
course, the innocent who tried to send you e-mail will never know, but you did
try to help them by adding ".invalid" to your bogus address. It's not your
fault if their e-mail client was thrown together in a hurry by someone who did
not take the time to understand e-mail in all its glory.
4. If you set up a disposable address through spamgourmet.com, folks have a
chance to send you e-mail that you will actually recieve. You might get a
couple of spam messages, but then they stop and never bother you again.
There are lots of other uses for disposable addresses, including your first
exchanges with an organization that you don't know and do not yet trust. Yes, I
have had the bad experience of giving my e-mail address to a company who
promised that they respected my privacy--and was immediately buried with spam
using that address. (You can probably demonstrate this for yourself if you want
to. Many ISPs will deliver mail with bogus subdomains. For example, if your
address is (e-mail address removed), you can give out (e-mail address removed) and
it will still be delivered. So you make such a change when dealing with someone
new and watch the junk roll in using that address.)
Scott