Blue Frog, providers of the Blue Security anti-spam service that I questioned some months back, may soon have some pissed off users. It seems the Blue Security user list may have gotten out into the open, and some anti-anti-spammer is readying a spam barrage against that user list.
Your email address has never been safe in your favorite mailing list, but getting spammed for using an anti-spam service is definitely a new one for the internet. For users of Blue Security, it might be time to change that address. For Blue Security, which essentially emails spammers warning them to stop, it might be time for a few more SMTP servers.
Blue Security says it is a spammer with previous access to the addresses that is causing the problems.
From the sounds of the commentary, it seems the anti-anti-spammer in question is targeting email addresses that users already know are “out in the open.” That is the consensus so far, and it does make a lot of sense. Whether the perpetrator’s retaliatory tactics persist remains to be seen, as the list is too small for the big spammers to see much value in it, if other than to drive away a handful of Blue Security users. However, as the commenters noted, the attention alone is likely to add to the Blue Security user base, potentially foiling the attacker’s efforts.
On a side note:
After pondering my failure to do a brute force (or dictionary) attack of MD5 using my Powerbook G4, on quick request from a reader, I need to rethink my place here at Spamroll. This is not a shot against OS X either – source exists (for Linux) that I could have recompiled for this singular effort – I chose not to do so because I was 1) just plain lazy, and/or 2) knew it would take the rest of the day and I needed to finish debugging some Perl scripts for a real engineer (I am working for him, even though I am paying him as well – how did that happen?). Anyway, my apologies – I will try to be more diligent in the future.