When it comes to fighting comment spam, akismet is the default, goto option… the problem is that, as I learned the hard way a few days ago when my host took my site off line for using up too many resources, it is an option that has a pretty major downside. Still, let’s focus on what akismet gets right first: it is extremely effective when it comes to identifying spam, quarantining it, and keeping it from showing up in your blog, that is most definitely a good thing. The problem is that this approach allows those comments to be added to your database before blocking them and keeping them from showing, and that means that it does nothing to keep spambots from using most of your bandwidth. In other words, what you need is something that can keep those comments from being posted in the first place, and that is where adding some sort of CAPTCHA can help you and/or an automated system that can tell bots from real users is bound to come in handy.
Now, I’m not saying that akismet is a bad idea, in fact I find it downright invaluable and it is definitely not going anywhere, but chances are that you’ll be better off making it your last resort for the odd spam comment that manages to get through, rather than your first line of defense.
And a word of caution, if you have a major spam problem already it may take a while to get the spam-bots off your case, as chances are that your site is already in their databases, and that means that they are going to keep on trying (if this remains a problem you may want to give blocking them via the .htaccess file a shot.. you can find the information on how to do that here, but the process is not for the faint of heart).
Okay, that’s it for now. Hopefully I will soon be able to go back to focusing on the things I actually care for, and I’ll finally be able to put spam and spam-bots off my mind.