Hi Alex,
No worries…it happens. Thanks for letting me know.
Keep in mind when you’re using the WordPress comment blacklist that it is inclusive, not exact match. So if you put the word “press” on the blacklist, it will not only block comments with “press” but “WordPress”, “express” and anything else that includes “press”. You almost have to think of every single possibility that something could match before you add a word to the list, which is a difficult task.
One thing not a lot of people realize, is that it doesn’t just run these terms you blacklisted against the comment content, but it tests against all of the following as well:
- the user’s name
- email address
- website
- IP address
- User-Agent of their browser
So if your terms are in any of those, it will get flagged as spam. Most people don’t realize it checks the User-Agent…that one doesn’t seem like a good idea to me, especially since it isn’t mentioned on the settings page or anywhere in the admin. It can be quite frustrating for users if they don’t realize WordPress does that.
Also, some people don’t realize this…if they specific a full IP address, it may match other complete IP addresses. For example…you put in 12.34.56.24, thinking it will only block that one IP. No…it will also block 212.34.56.24, as well as 12.34.56.245. So you have to be really careful.
You might be interested to know that in the Enhanced Comment Blacklist in WP-SpamShield, I changed that blacklist behavior a bit to make it a little more user-friendly and IMO a bit more accurate. It does not check the User-Agent, only does exact matches on email addresses, for IP addresses if you specific a full IP address (123.45.67.89) it will only do an exact match, and if you specify a C-block (123.45.67.), it will match IP addresses within that C-block, not the standard inclusive match. (The plugin checks user agent quite thoroughly so there’s no need for users to have to mess with that.) In addition, instead of sending the comments to spam it will block them altogether. This option has to be enabled though, otherwise it just follows the default WordPress blacklist behavior.
I hope that helps shed some light on it a little bit. Have a good one.
– Scott