Open kristineds opened 8 years ago
Do we know why it blocks the comment? Just curious if it's because of an IP address mismatch or for what reason it might be identifying the comment as spam when it comes from a reply via email.
Quoting from the plugin's FAQ section
How does Anti-spam plugin work? The blocking algorithm is based on 2 methods:
invisible js-captcha
andinvisible input trap
(aka honeypot technique).How does
invisible js-captcha
method (aka honeypot) work? The 'invisible js-captcha' method is based on fact that bots does not have javascript on their user-agents. Extra hidden field is added to comments form. It is the question about the current year. If the user visits site, than this field is answered automatically with javascript, is hidden by javascript and css and invisible for the user. If the spammer will fill year-field incorrectly - the comment will be blocked because it is spam.How does
invisible input trap
(aka honeypot technique) method work? The 'invisible input trap' method is based on fact that almost all the bots will fill inputs with name 'email' or 'url'. Extra hidden field is added to comments form. This field is hidden for the user and user will not fill it. But this field is visible for the spammer. If the spammer will fill this trap-field with anything - the comment will be blocked because it is spam.
I see. Thanks. We could try to add special exceptions that will (hopefully) be capable of disabling those whenever a reply is received via email. Seems like it should be configurable also.
It would be nice if Comment Mail is tested against and made compatible with the Anti-Spam plugin by WebVitality.
We have at least one report (via internal ticket) of things not working as expected: