One of the most frustrating events a blogger or commenter could face on the net is being blocked or their comments being eaten by some anti-spam system employed by the blogs that they visit.
I for one had many of this incidents before. The latest was just a few minutes ago when I posted a comment on Aja Lapus’ blog post about Schools still teaching deprecated HTML. Aja’s blog is protected by Bad Behavior, an anti-spam plugin that is indeed powerful and effective. Yet it has received its fair share of complaints from bloggers because in some instances, it has blocked or eaten the comments by non-spammers or “false positives” even comments by the blog owners themselves.
Of course, I vouch that my laptop is spam and malware free so it’s a bit frustrating to know that I’m being blocked as a spammer. It’s a good thing that Bad Behavior displays a web page pointing to the Spamhaus Project explaining why my comment as blocked, because some anti-spam plugins simply swallow your comment and dumps it in the spam comments list.
Going back, I followed the links to the Spamhaus project and it turns out that it was my IP or Internet Protocol address that was blocked. Here below is the entirety of the explanation:
184.108.40.206/24 is listed on the Spamhaus Block List (SBL)
23-Mar-2008 10:14 GMT | SR01
Spammer operating from 220.127.116.11, hijacking PCs in other networks for spamming.
To have record SBL63950 (18.104.22.168/24) removed from the SBL, the Abuse/Security representative of globenet.com.ph (or the Internet Service Provider responsible for connectivity to 22.214.171.124/24) needs to contact the SBL Team to explain how the spam problem has been terminated. If the spam problem that caused this listing has been terminated we will normally remove the listing from the SBL.
So, a spammer using the same ISP as I do has been using the network or the set of IP addresses which the one I’m currently using right now to spread spam over the internet. Damn it!
There’s little I could for now because the problem, or rather the solution itself rests on my ISP, Globe Broadband to contact the SBL Team and work out a solution so that the IP range in question be cleaned and removed from the block list. Question now is, will Globe Broadband do something about it? Are they even aware of this issue?
Last month, I recall receiving a phone call from a Globe Broadband representative asking my if I was aware of anti-spamming techniques to protect my computer from attacks. This was part of their effort in ‘cleaning up’ their network to provide a ‘better broadband internet service to their customers’.
It seems that they either missed a spot or they need to clean up their networks again. This may be an issue isolated to blogs being protected by Bad Behavior because Akismet-protected blogs are not flagging my comments, as far as I can tell. I wonder if other Globe Broadband users are having the same or similar problems. I suppose it’s time to give them a wake up call once more.