Allow scanning through existing users

Hi,

Please upgrade to the 3.x branch.

The 3.x branch has this feature, although it is implemented as a cron task instead of a bulk check.

Before I upgrade, I'd like to know how this work. Does the scan automatically delete the accounts or quarantine then for me to review?

The scan is not enabled by default, so it won't actually run until you ask it to.

When it scans (invoked via cron), you can ask spambot.module to just report (to the site log) spam accounts that it finds, or block accounts, or delete accounts. This is all configurable so you can choose as you like.

I think I may have found a conflict with this running at the same time as MailQ. I only turn on MailQ when I want to queue up a bunch of mails to send on cron. Spambot found spammers before turning on MailQ and after I turned it off. I have spambot checking 10 users every hour and about 300 users to go through. It's doubtful that there were no spam accounts during the period that I had MailQ active.

Hi,

I'm sorry, but what is MailQ? Do you mean http://drupal.org/project/mailq ?

Spambot should be operating independently from MailQ. Spambot only checks existing user accounts if they match spammers reported on www.stopforumspam.com. Spambot isn't meant for fighting email spam, and doesn't do anything related to emails outgoing from your site.

Also, you can turn spambot's account scanning by having it check a maximum of 0 user accounts per hour.

The only thing I can possibly think of, is that the increased processing during cron is hitting your server's PHP limits, and hence MailQ doesn't get a chance to run ... or something like that.

When an account is examined there are options to unpublish nodes/comment or delete them as well as block/delete accounts. When I do the bulk deletion using cron, what happens to the nodes/comments. Are they deleted or just unpublished? Can I force behaviour in this context? i.e. when I delete an account using cron I want to delete the comments as well.

Cheers,
Graham

PS: Just been using this for a day and I really like it!

@6: Presently, when an account is blocked or deleted via cron, nothing is done to the nodes/comments by that user (although I think if an account is deleted, then all its posts become attributed to the anonymous user - this is Drupal core behaviour, not spambot.module's).

I thought it was a bit dangerous having bulk automatic delete/unpublishing of nodes/comments via cron.

In the case of examining an individual account, deleting/unpublishing is allowed because, presumably, its a decision by an administrator and less likely to accidentally delete important content.

I'm also going to mark this as fixed since there hasn't been a reply to comment 5 for a long time, and this feature request is met in the 6.x-3.x branch.