Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I've been coming across some spam on the community site lately. I don't think Mollom is configured properly, nor does there appear to be a captcha fallback.
Assuming there are no objections, I'll go ahead and set this up.
Comments
Comment #1
anarcat CreditAttribution: anarcat commentedGo ahead. I thought I set it up right, but it was my first time setting up mollom....
Comment #2
ergonlogicIt turns out you have to specify which forms to protect with Mollom. I've activated it for the following forms:
* blog entry form (I don't think this is actually used, but whatever)
* book page form
* comment form
* discussion entry form
* user registration form
I'll try to test it by submitting some spam, I guess.
Comment #3
ergonlogicI was able to trigger the spam filter by copy/pasting existing spam into a comment form. I had set it to prompt for a CAPTCHA, but I didn't see one. I'll double-check whether I have to install captcha directly, as I was under the impression from the Mollom docs, that this was provided by the Mollom service.
Comment #4
ergonlogicAlright... so captchas are part of the Mollom service, but only triggered by borderline content... which I can't seem to find. So, I'll assume this works, until proven otherwise.
If anyone is blocked with false positives, let me know by reopening this issue.
Comment #6
omega8cc CreditAttribution: omega8cc commentedWe are flooded by spammers since December 2013 and I'm already tired after deleting manually a two or more dozen of them, while Mollom doesn't stop them at all, so they keep posting the spam and then links to their spam on the community site on Twitter.
Comment #7
helmo CreditAttribution: helmo commentedI suggested botcha in #1923440-6: Spam
Time to give that some more thought...
Comment #8
helmo CreditAttribution: helmo commentedI just created two views ... hoping to make this easier. Installing VBO could help some more ...
http://community.aegirproject.org/admin/build/views/edit/usercomments
http://community.aegirproject.org/admin/build/views/edit/usercontent
Comment #9
ergonlogicAlright, I enabled honeypot.module, which was installed but not enabled. Not sure why not... Hopefully that'll help a bit.
I also enabled vbo and tweaked the views that helmo had built. The comments one can not be found at admin/content/comment/spam, and there's a corresponding menu item. I added a link to suspend the account of the comment author, and we can now mass-delete comments. I added a filter on this view to remove any comments from users with a role assigned. This allows for a sort of white-list, and to that end, I created a 'human' role with no permissions attached. I went through all the comments on the site and added that role to all the users with valid comments (save one that I'm not sure about). So this view should now only contain new comments from new users, making it much easier to keep spam under control.
Comment #11
helmo CreditAttribution: helmo commentedFor reference we do have VBO nowm and direct url's for nodes and comments:
http://community.aegirproject.org/admin/content/node/spam
http://community.aegirproject.org/admin/content/comment/spam
Anarcat and me are still having issues with vbo....