Defensio and server configurationApril 23, 2010
It has been a while since my last post and like always I managed to find a good excuse for not posting anything. The last month (!) I have been busy trying to solve a riddle which involved the Defensio addon. As you have probably read on this blog or somewhere else on the web, Defensio is used to protect a blog against comment spam. A few months back I was very excited about the version 2 release of the api and I modified the plugin for the photoblogging software Pixelpost for this new version.
About a month ago I noticed that huge amounts of spam were actually published in my websites. Pretty strange, considering Defensio was active to prevent this behavior. It took some long nights to discover that my hostingcompany had disabled the fsockopen functionality, something that is extensively used by Defensio. So we had to switch to Curl, although that wasn’t completely operational just yet. The guys at Defensio put in some extra hours and provided me with a working test version. After some modifications Defensio was yet again stopping spam in my photoblog.
However, I also have a WordPress blog (you’re reading it) and that also attracts tons of spam. So much in fact I updated some core files of the WP addon with the newly programmed files and a fresh copy from GitHub to enable Defensio again. To bad it didn’t work. Over 100 spam comments a day where published on my blog and had to be removed manually. It took me and Camilo from Defensio about three nights debugging to catch the offending line of code and finally the plugin (which stopped working at March 21, 2010( is fully operational again since last night.
Finally all spam is getting caught again which frees me up to do some more bug hunting in some code I wrote instead.