Spam Solution for G.D.O

Yeah, this is a g.d.o thing, not a docs issue. Also, we really shouldn't be commenting on the g.d.o threads. :-/ I forgot to lock that one down.

Same thing here.

When editing a comment inside a discussion (story) the following message is output:

Your submission has triggered the installed spam filter and will not be accepted.

To reproduce:

1. Create a new discussion (story) at http://groups.drupal.org/node/add/story?gids[]=417
   
   Screenshot.
2. Add a comment.
3. Edit your comment. Click on PREVIEW COMMENT or POST COMMENT button. The following error message will display.

Attaching screenshot

I'd like to re-purpose this a bit about the general spam problem.

Mollom blocks people a little too often. But, because g.d.o sends e-mails right away, we need a solution that blocks spammers before they do their work.

Possible solutions:
1. Work to make mollom better.

2. Provide a role that has the "post with no checking" permission and grant that to people in some way (based on age of their account, being vouched for by someone else, etc.).

3. something else

The only possible solution, IMO, is the first.
To make a person the responsible for giving the permission to post without checking is not a good practice; once people will understand there is a person who can give them that permission, they will start to open reports, and ask why they are not granted that permission.

Actually, the first will not work at all since mollom is closed source.

I'd support a mechanism that allows them to post stuff without being checked vy mollom once they have successfully posted a couple of nodes or comments and these were not deleted again. Or something similar.

@Gerhard - you know how persistent spammers are and you propose that? That system is so easy to bypass!

I was actually referring to Mollom as module. What you proposed could be implemented in mollom.module as an option.

@greggles: Spammers are persistent, but they are also looking to get short-term successes. The suggested workflow would be:

1) user registers

2) user posts stuff (with mollom check)

3) time pases (several days)

4) if the stuff from 2) is still there, then it isn't spam, so the user gets the suggested role.

5) peridodic check if the condition in 4) is still true.

@Kiam: Ah, of course, we could do that, if Dries wants such a patch.

Another potential solution: manage expectations better. We could add some text to the welcome message or the node/add/* page:

We use a spam filter that sometimes blocks content. If your content is getting blocked, consider removing any unnecessary links and improving the overall quality of the message. It tends to learn your reputation over time, so you may notice the problem more when you first join the site.

we made recent mollom improvements here. please reopen if needed.

Thanks moshe that's good news. I didn't notice any spam/reject message during the last weeks.

It is somewhat normal for you to get a CAPTCHA when editing your own content.

We were getting complaints every day via a number of channels about the quality of the spam filter. Dries made some tweeks around September 20th and the complaints have virtually vanished (aside from this one, obviously). We also don't have a large amount of real spam making its way through. So, I'm inclined to think that the solution is working really well. I'm sorry it caused the slowness for you, Designer, but it's really the best thing we can do for the site.

I can not post event, have complete operation before without problems, Created this new account with new email (new domain) and still have the problem. The only field completed is 1 word in the title. I need to post for a meetup event.

"Your submission has triggered the installed spam filter and will not be accepted."

Thanks in advance for the help

@MkeDev - are you the same person as MkeHack? If so, I posted details about your situation at http://drupal.org/node/684424#comment-2475464

#684424: Am being totally blocked by Mollom on GDO.