I installed Mollom on my test website, but all my attempts to fill captcha was refused.

Later I found that it is not problem only of my website, but I cannot fill Mollom captcha on any website using Mollom (including mollom.com).

When I tried to send this message over contact form on mollom.com I got this message: "Your submission has triggered the spam filter and will not be accepted."

I am currently connected over ISP in Czech Republic and have IP address 188.75.128.2. It seems under same IP address are all clients of that ISP.

Seems like critical bug as there is no way to post anything for me on websites using Mollom.

CommentFileSizeAuthor
mollom-problem.jpg62.47 KBanantagati
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

sun’s picture

Category: bug » support
Status: Active » Postponed (maintainer needs more info)

Sorry for the delayed response. This should not happen, but it's nothing that can be fixed in the client-side module.

Do you still have this issue? If so, can you try again on mollom.com, so we can analyze your session data?

anantagati’s picture

I am not there anymore, but when I will call with father he can check it. I will let you know then.

sun’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Thanks for reporting back.

If it is OK for you, I'm going to close this issue for now. Feel free to re-open when you want to provide further information.

anantagati’s picture

Status: Closed (cannot reproduce) » Active

So I called with father who tried it from that location and got this message:
Your submission has triggered the spam filter and will not be accepted.

He tried contact form:
Subject:
Drupal issue #882072
Message:

Trying to to pass Mollom filter.
See more information here: http://drupal.org/node/882072#comment-3438224

His IP address was: 188.75.128.2

anantagati’s picture

One more thing. It doesn't ask for captcha it only shows the message.

sun’s picture

Sorry again for the delayed response. That submission was blocked because of a negative reputation of the IP address. If your internet provider assigns you a dynamic IP, then this should no longer be an issue in the meantime. Otherwise, if you always have that IP, and if you are still being blocked, then your client/computer might be abused by spammers and I'd recommend to run a virus/trojan check.

anantagati’s picture

Problem is that that IP address have all people connected through that service provider. Let say all people in radius about 30km connected through that ISP have all same address. In city of my parents it's most used ISP.

Mollom didn't offer any captcha, so that means that none of those people can post to any Mollom protected website. I am OK with that as I am not living there and on our website we started to use reCaptcha instead of Mollom, but it is definitely disadvantage of Mollom as some users may have legitimate fear to use it and lose users.

escoles’s picture

I'm getting reports of a similar issue from a client. She's trying to test comment forms, and keeps getting bounced.

Given high spam levels, going without protection altogether is a very unattractive option. But if our clients are going to get blacklisted, that's not good either.

Would an option to forego blacklist filtering be workable? (i.e., could the Mollom service support such an option.)

Dries’s picture

Can you share some session IDs of sessions that were incorrectly blocked?

anantagati’s picture

Can you share some session IDs of sessions that were incorrectly blocked?

How can I do that?

sun’s picture

Priority: Critical » Normal
Status: Active » Fixed

Mollom's management of IP address reputations has been significantly improved in the meantime, so I believe that this issue is resolved by now.

Also, regarding the other detail that was mentioned earlier here: The form to contact Mollom Support on http://mollom.com itself is no longer protected by Mollom, so support requests will never be blocked.

Thanks for your feedback,
sun

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.