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.Pretty satisfied with Mollom. Here's a feature request - thanks.
Ability to 'Report to Mollom' registered spam user accounts and optionally delete or block the spam user account.
Use case: if a spammer successfully creates an account (it happens) and this registered spammer account successfully posts a comment or submit a story (via Modr8), I can report to Mollom the comment or node, which gets deleted, but the spam user account if left active and untouched. Mollom could offer an option to either toggle the spam user account to "blocked" or more radically simply delete the spam user account.
| Comment | File | Size | Author |
|---|---|---|---|
| #18 | Screenshot_2_4_14_10_16_AM.png | 32.8 KB | greggles |
Comments
Comment #1
sunThis feature is actually part of the D7 module already. However, backporting it to D6 might not be very easy. I totally understand the need for it, but I'm not sure whether it's worth to try to make this work.
Comment #2
Dries CreditAttribution: Dries commentedMmm, is this really part of D7 already? I don't remember that.
Comment #3
sunBy deleting (+ optionally reporting) a user account in D7, all of its content is deleted, too. We integrate with the new user account cancellation process.
Comment #4
jeffschulerA D6 site that I use Mollom for is getting lots of spam user registrations now, making it through Mollom's text analysis filters.
Assuming that feeding back that info to Mollom is useful, this functionality would be very useful.
Comment #5
jeffschulerIf deleting a user and its content complicates this issue, why not just block the user, (and not worry about the content?)
Comment #6
Code Rader CreditAttribution: Code Rader commented+1 please. The main reason I went with Mollom was for user registration spam. It did great at first, but now they seem to have figured it out. Just had 2 in the past hour.
Comment #7
GuillaumeDuveau+1, having a lot of registration spams these days. I'm using the CAPTCHA protection provided by Mollom, and the account activation by email. A spammer keeps passing both.
Comment #8
mcurry CreditAttribution: mcurry commentedSubscribing. Getting hit with registration spam as well.
Comment #9
mshaver CreditAttribution: mshaver commentedWould also like to see better registration spam prevention and reporting for D6. Most links added to a bio field are pretty obviously spam, so the text analysis is letting a lot through.
Comment #10
venusrising CreditAttribution: venusrising commentedWe are using Mollom for our production site (stable version though) we have same issues with content spam and some Spam users creating accounts and posting BS. it sure would be good to be able to block by IP or something.
Comment #11
antiorario CreditAttribution: antiorario commentedsubscribe
Comment #12
AimAdvantage CreditAttribution: AimAdvantage commentedsubscribe
Comment #13
rubyji+1
Comment #14
chrism2671 CreditAttribution: chrism2671 commented+1
Comment #15
rubyjiI'd also like to request the ability to report a USER not just NODEs to Mollom. We get about 10 spam registrations daily, and some don't comment or post right away, so we have to monitor the profiles themselves. I block the users and then delete them after about a month (to ensure that I haven't unintentionally blocked a legimiate user).
Comment #16
EmpireNM CreditAttribution: EmpireNM commentedI agree with #6. Sorry to say that Mollom was working great, but is now pretty much ineffective. Spammers are bypassing Mollom on registration, and captcha on any input forms. So the only way to stop them is to block them from the site. I'm blocking numerous email addresses with access rules. But I would rather benefit Mollom in adding those addresses to a registry where it could potentially help other sites.
Comment #17
chrism2671 CreditAttribution: chrism2671 commentedYes, I'd like to chime in that we have removed Mollom altogether now and ceased paying for it, finding it completely ineffective, and in fact slightly annoying.
Comment #18
gregglesThis doesn't make sense to me to say that the issue is satisfied by this behavior. One of the standard ways to deal with spam content (including the policy on drupal.org and g.d.o) is to block the account and delete the content (not delete the account). When I look at the options in D7 core with mollom none of them matches that use case.
Anyway, given that there are a variety of moderation policies, I believe a more flexible/sustainable solution is #655846: Mollom Actions which lets people chain together actions as they might need.