Today I experienced a client who used my site-wide contact form, who's message I did not receive at all. Because it was blocked by mollom. The client had not continued to enter the mollom captcha, due to not understanding this. Client believed the message had been submitted.

FEATURE REQUEST: can we store these failed messages somewhere? For later human review? Sometimes apparently valid messages get lost due to visitors not understanding the captcha...

P.S. Is mollom working well for multi-lingual sites? In this case the message was sent in Dutch language.

Comments

Dries’s picture

It is (temporary) stored in the watchdog but that could be improved ...

spidersilk’s picture

I think this is really important. I recently installed Mollom on a client site that had been having some problems with spam, and when I went to check on it to see how it was performing, I was very disturbed to see that there was a chart showing that it had blocked some "spam activity" -- but apparently no way of finding out what it had blocked!

Given that every other spam filter of any type (e-mail, web, anything) is responsible for at least a few false positives from time to time, I think it's really crucial to have some way of seeing what has been blocked and correcting it if necessary. The bit in the FAQ about getting rid of the moderation queue seems to suggest that you don't think users of this module need to be able to see how it's doing because you're convinced it will always be 100% accurate, so we don't need to know! This is troubling to say the least. No software is 100% accurate.

I had planned on adding Mollom to most of the other Drupal sites I manage if I was happy with its performance, but based on this, and the fact that the issues queue shows several people having experienced false positives, I'm starting to think this module is not yet ready to use on any site where losing valid submissions would be a major problem (for example, any business site that relies on the contact form for customers to contact the business).

I may leave it on the one site I have it on for now, as the only thing it's applying to there are blog comments and forum postings, which are less crucial, and I'll keep an eye on how the module develops in the future since the idea behind it sounds good, but I honestly don't think it's ready to use on most production sites yet.

Dave Reid’s picture