What's nice about comment spam is that, unlike e-mail spam where the text can be mangled (V1agraa), comment spam is meant to be effective at coming up in searches and in conferring extra search mojo to sites for certain words (in my most recent case, "fioricet"). So, spammers are forced to spell their key words correctly ("ringtone" is another heavily-spammed term), and it's easy to force moderation for such spammy comments.
Sam Ruby: Bounces:
If my experience is anywhere near representative, it seems like the future of SPAM on the Internet is to be sent purportedly from somebody that doesn’t exist, and to somebody that doesn’t exist.
I've had the same experience. Since TextDrive (with some help from my own procmail rules) seems to do an excellent job of blocking all real spam before I even see it, just about all of my spam now consists of bounces from joe-jobs, plus the occasional link exchange request. 
Sam posts his procmail rule to block such bounces:
:0:
* ^FROM_MAILER
* ! ^TO_rubys@
| /home/rubys/bin/logspam
I had no idea that procmail had a ^FROM_MAILER rule. I kind of want to know what's in that rule before I use it, but that's not going to stop me. Any way for me to see what's in that rule without having to dig through the source?
Update: If you say:
VERBOSE=yes
in your .procmailrc, that'll show you the exact regular expression procmail tries matching against in your procmail log.
Update: Sam points out that that information is in the man page.
Friday, February 29, 2008
Permalink
I hate ASP.NET
I hate ASP... I was doing wonderswith PHP, then suddenly one of myclients...
Johnies: Mar 17, 6:14am