:
:Get this guy outta here!
Firstly, Chris, I understand your frustration. But, please, do *NOT*
Cc a random ISP ( [EMAIL PROTECTED] ) in email that you also
send to a FreeBSD list, let alone several FreeBSD lists!
This particular spammer is operating from 213.96.224.148, which has
long been blacklisted not only by spamcop, but by many other
DNSbl providers. See:
http://relays.osirusoft.com/cgi-bin/rbcheck.cgi
Personally speaking I think that hub should be running DNSbl. I recently
gave up trying to fight every spam coming into my system (50+ pieces
of email to my main mailbox alone per day, several hundred flowing through
my system and bothering my friends). Instead I went through and upgraded
sendmail to the most recent release and turned on about five DNSbl
sites as well as added a well known HACK() to disallow relays whos
reverse DNS does not resolve. My mail system now rejects around 350
emails a day.
This cut my personal spam down from 50/day to 5/day. Well, that is
until some asshole spammer started using my email address as the
envelope sender for their spams, but that's another story. Sigh.
Yet another up-and-coming trend by spammers... using valid envelope
addresses that are not their own. At least it's easy to filter,
and if I ever spend the time to track them down it'll be about $50K in
damages under california law. A dangerous game, spammers play. A
dangerous game indeed.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
