{"id":826,"date":"2004-12-29T14:57:23","date_gmt":"2004-12-29T14:57:23","guid":{"rendered":"\/?p=826"},"modified":"2004-12-30T07:51:43","modified_gmt":"2004-12-30T07:51:43","slug":"wordpress-spammers","status":"publish","type":"post","link":"https:\/\/harry.sufehmi.com\/archives\/2004-12-29-wordpress-spammers\/","title":{"rendered":"WordPress’ spammers"},"content":{"rendered":"

Blogs have been under massive attack from spammers lately; I totally didn’t expect to have so many posts about this single topic in this blog.
\nBut with Trencaspammer users as the last casualties<\/a>, I think investing in a heavy spam defense – such as Spaminator<\/a> or WP-AuthImage<\/a> is actually now worth the trouble of installing them.<\/p>\n

I’ve installed WP-AuthImage here and it seems to be working, and for a long time I hope.
\nBut with the spammers continuing to attack our defenses, I think it’s time to fight back.
\n
\nIdeally, there should be some sort of SpamAssassin, but available as Apache module, which once installed will block incoming requests from spammers.
\nI just hope it won’t be as bloated as SpamAssassin (SA) though \ud83d\ude41 this server is of quite decent spec, yet it’s almost running out of memory with amavis & SA running.<\/p>\n

But to be fair, my current anti-spam setup for my mailserver is quite complex. Incoming email will go through Postfix (which will query various RBLs), then it goes through amavis (virus scanned by clamd), then it got passed to SA (checked against Bayes and Razor database).
\nIt will take some time for Internet community to make similarly robust defenses available for our webservers.<\/p>\n

In the meantime, we can launch offenses at the spammers instead. There are a few which you can try :<\/p>\n