Just updated the new rules :)

Cool - if anyone wants to post up rules they're using onto this thread then please do.

You know the best thing for me? I stop all users from posting a URL in their first 5 posts. Kills 99% of spam.

regexp:a_url:10:any:"/http/i"
regexp:a_www_url:10:any:"/www/i"

obviously a threshold of 10 - so anyone who posts any kind of URL will need to be moderated - if they have less then 5 posts.

Jimbo - I am not very good at figuring out the templates. How can I add the name of the poster to the spam report? I have spam reports posted to a special forum. I would like to have their name available (in the title?) so I can scan the title and see the real problem posters.

Is that possible?

I'd err on the side of caution and use something like

regexp:a_url:10:any:"/http:\/\//i"
regexp:a_www_url:10:any:"/www\./i"


${spam_user} is the name of the posting user. The user's name is already in the report as part of the quote tag.

Hmm. Okay. When I do indeedget more spamvertiser, I'll preserve the links to help with the rules.

Great plug-in, and we've just recently installed and began using it on our system. Still tweaking the rule-set, but so far it's been great.

I have run into the admincp/modcp issue as well, since as far as I can tell the postdata_presave hook is also called when moderating posts. I haven't been getting any errors, but the admincp/modcp page doesn't refresh at all after validating posts (I get a blank page), and the whole process basically just fails.

In my case, I had to add the following snippet, modified from an earlier post in this thread:

The $GLOBALS['sbhits'] = array() portion in the else construct didn't actually work, so I trimmed it down to what you see above, and that appears to have restored modcp/admincp functionality for me.

I've also made a small addition in my system that I thought I'd share... Generally, spammers on our forum get banned pretty quickly, but obvioiusly I don't want that to be an automated process until an Admin or Senior Moderator has had a chance to review the situation. So what I did was a template modification to add a link to the banning portion of the modcp. Basically, a "Click Here to Ban or Suspend This User" link.

The following specific modifications were made in SpamBuster Libraries under the global_start plug-in hook:

In variable definitions:
In body of message section:
The only other issue that I've run into is the way that posts are dropped into the moderation queue after an edit of an existing post when it's the first post in the thread.

Normally, if a user posts a new thread which is tagged as spam, the entire thread is set to require moderation. However, if the user posts a valid thread, and then goes back and edits their first post, then only the post is sent to the moderation queue.

This creates a situation where normal users see a dangling thread header with no posts. Further, the in-line moderation tools don't work for approving the post, because they're looking to approve the thread. I think the post can still be approved from the ModCP, but ultimately it creates an odd situation.

Granted, this shouldn't occur too often, but it would be nice to add a check to the code following an edit to determine if the post being edited is the first in it's thread, in which case the thread should probably be set to "moderated."

I'm going to poke a bit at the code myself to see if I can't make this work, although it's not a huge priority. If I do solve it, however, I'll post my results here.

Thanks again for a great mod otherwise, though.

Thanks for the detailed feedback and suggestions. I'll factor these in for the next release.

Any update of this for 3.6.0?

I don't have a 3.6 install to test it on at the moment. If anyone would like to verify if it works or otherwise that would be great.

Thanks :)

It appears to be working in 3.6.0...though I haven't had any real-world tests (actual spammers) hit it yet.

It did catch my test posts (both new posts and replies).

If it does anything odd, I'll be sure to let you know.