Administrative and Maintenance Tools - vbStopForumSpam - known spammer lookup for new registrations

vbStopForumSpam

This provides access to a RBL type system for forum admins, listing known spam IP / email / usernames. The RBL database is provided by www.stopforumspam.com. You do NOT need an API key from the website in order to access the database. only to submit data if you should wish to do so.

At the point of user registration, the mod checks if the IP number / provided username / email addresses appear on a block list and can block the registration.

Whilst this isnt the most perfect way to stop all forum spam, its another step that spammers have to overcome.

VB4 here https://vborg.vbsupport.ru/showthrea...hreadid=230921
Its the same code, it works in 3.54 to 4.0


What it does

It checks with a remote database of known forum spammers. Their IP number, email address and forum username are tested and based on your configuration, you can reject / log / accept user registrations based on what you get back.

This version doesnt have
- whitelisting or the ability to submit users to the database but it will within the next week.
- automatic user deletion / post / PM purging. There are good tools out there already, this does something else.

Instructions are included in the installation.txt file - PLEASE read it first and dont forget to actually upload the files in the upload folder, otherwise it WILL kill your registration progress and you wont see the log file options in admincp. You do not need to download the product-vbstopforumspam-3.54.xml file unless you are using a vBulletin version older than 3.6.0

Changes to vB
- 3 new database tables
- 2 database table alternations
- No new templates.
- 2 Hook (register_addmember_process & register_addmember_complete)

Ive tested it but had feedback that it works with versions as old as 3.6.2... Support should go back to older versions, as long as they have hook support for register_addmember_process / register_addmember_complete

Known to work - tested by me
- vBulletin 3.6.8 on Apache 2.2 / PHP 5.1.2 on Linux using cUrl
- vBulletin 3.7 Gold on Apache 2.0 / PHP 4.4.3 on Windows without cUrl (template changes wont work on 3.7 - thats in the next version with auto template changes)

For code to submit spammers to the database, check this post for code changes
https://vborg.vbsupport.ru/showpost....&postcount=288

Reported in the thread to work
- 3.6.1, 3.6.2, 3.6.9, 3.6.10, 3.7.0, 3.7.1, 3.7.2, 3.7.3, 3.74, 3.80, 3.81, 3.82, 3.83, 3.8.4, 4.0beta3

If you have 3.54, then you can use the product-vbstopforumspam-3.54.xml file attached instead of the one in the ZIP file, which will allow older vBulletin versions to access this mods' features. I personally havent tested this version, its a user contribution, thanks to Darrell Mobley, that changes the way the XML works when imported into older versions.

Installers should remember to refresh their ACP navigation window when they first install it so they can see the new log file menu item.

REQUIRES MySQL 4.1.1+

Future versions
- Automatic integration into vBulletin to add users to the stopForumSpam.com database from a form
- Whitelisting of username / IP / email addresses
- AJAX integration to allow for lookups from within the users profile
- Decreased remote query count from three per user to one per user.

Versions / Changes

0.1 Initial Release

0.2 pedigrees special brew birthday release.
- Small security update. If you have 0.1 installed, download 0.2 and replace your existing functions_vbsfs.php with the one in the archive. It just tests to see if its running inside the VB framework before anything else. This is what happens when you code at 2am after drinking wine

0.3
- stopped it processing valid registrations twice
- moved all non-function code into the plugin. Not a big one as 0.2 basically did that
- fixed a typo in the log pruner that stopped it working (404)
- removed unused fields from the database for people with mysql that doesnt support varchar > 255 (ie mySQL4). If you have 0.2 installed and dont need to prune your logs just yet, you dont really need to install this version but can instead wait for 1.0 unless of a massive security update.

0.4
- logs registrations that arent/wouldnt be blocked
- fixed XML errors when username has a space it in
- tightened up the cache so that it doesnt test a username against an email name to give a bypass result (for when a username is an email address that isnt banned where the email address is)
- fixed some basic logic errors in the PHP

0.6
- Should work on PHP 4.4 now - rewrote the XML with PHP4 in mind (tested on Apache2.0/PHP 4.4.3)
- Fixed a caching system where data wasnt being updated correctly which could cause a remote query when one wasnt needed
- Possible false negative situation when a spammer was blocked due to SFS.com being down who then visited again when it was up but within the cache expiry time
- Remote query failure when the result page isnt XML should work a bit better now. It does a very basic test for valid XML results.
- Fixed log purging (again) and it should actually work properly now.
- No longer requires PHP5
- The log viewer now links to a user profile when registration is allowed.

v0.61 - Removed a template change that was invalid vBulletin code. The package you download will still say its 0.60 however

NB : When upgrading from any version to 0.6, you must remove and then add the plugin due to changes in one of the database tables

You need to have an API key from www.stopforumspam.com in order to submit data, its free and easy to get... You DONT need an API key in order to use this mod however, only to submit spammer data.

Issues are
- The usergroup permissions / view details etc DONT work. I jumped the gun and put the permissions controls in there before I put the code in. Please delete the includes/xml/bitfield_vbstopforumspam.xml file and rebuild your postbit

Installation
- Follow the instructions in the zip file, that includes upload the correct folders
- ONLY download the 3.54 xml file if youre using a vbulletin version prior to 3.6.0. use this file to install the mod instead of the xml file in the zip file.

Please click Installed

[inaka]

I seriously want to give a big thanks for this.

INSTALLED. Awesome.

[bernie g]

Installed and linked up to the database perfect. Although I've uploaded Wired1's plug in, I still can't see the box anywhere where I submit spam

Edit: Just found it

[imported_silkroad]

Congrats on a great mod! We installed and there were 7 entires in the logfile within 15 minutes !!!

[mradlin]

Installed!! Thanks!!

[imported_silkroad]

Isn't is better to send the details of the spammer to the StopForumSpam database automatically by adding code to inlinemod.php?

That way, when moderators select "Delete Posts as Spam" there is no need to waste the moderators time to use the form in the user template (as provided in the instructions). This is too much work and unnecessary extra steps when it can be done automatically in inlinemod.php when deleting spam.

There are plenty of hooks in inlinemod.php, for example, $hook = vBulletinHook::fetch_hook('inlinemod_deletespam'))

Isn't is better to simply add an option to admincp and a small amount of code to automatically add the spammer to the database?

grep -i hook inlinemod.php
                ($hook = vBulletinHook::fetch_hook('inlinemod_authenticate_switch')) ? eval($hook) : false;
                ($hook = vBulletinHook::fetch_hook('inlinemod_action_switch')) ? eval($hook) : false;
($hook = vBulletinHook::fetch_hook('inlinemod_start')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_clearthread')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_clearpost')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_closeopen')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_stickunstick')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_deletethread')) ? eval($hook) : false;
                        ($hook = vBulletinHook::fetch_hook('inlinemod_spamthread')) ? eval($hook) : false;
                                ($hook = vBulletinHook::fetch_hook('inlinemod_dodeletethread')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_spam_permission')) ? eval($hook) : false;
                        ($hook = vBulletinHook::fetch_hook('inlinemod_spamconfirm_defaultaction')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_spamconfirm')) ? eval($hook) : false;
                                ($hook = vBulletinHook::fetch_hook('inlinemod_deletespam_defaultaction')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_deletespam')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_dodeletethread')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_undeletethread')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_approvethread')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_unapprovethread')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_movethread')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_domovethread')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_mergethread')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_domergethread')) ? eval($hook) : false;
                ($hook = vBulletinHook::fetch_hook('inlinemod_spampost')) ? eval($hook) : false;
                ($hook = vBulletinHook::fetch_hook('inlinemod_deleteposts')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_dodeleteposts')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_undeleteposts')) ? eval($hook) : false;
                ($hook = vBulletinHook::fetch_hook('inlinemod_approveattachments')) ? eval($hook) : false;
                ($hook = vBulletinHook::fetch_hook('inlinemod_unapproveattachments')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_approveposts')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_unapproveposts')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_domergeposts_process')) ? eval($hook) : false;
                ($hook = vBulletinHook::fetch_hook('inlinemod_domergeposts_complete')) ? eval($hook) : false;
                ($hook = vBulletinHook::fetch_hook('inlinemod_mergeposts_post')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_mergeposts_complete')) ? eval($hook) : false;
                ($hook = vBulletinHook::fetch_hook('inlinemod_moveposts')) ? eval($hook) : false;
                ($hook = vBulletinHook::fetch_hook('inlinemod_copyposts')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_domoveposts')) ? eval($hook) : false;
        ($hook = vBulletinHook::fetch_hook('inlinemod_docopyposts')) ? eval($hook) : false;
($hook = vBulletinHook::fetch_hook('inlinemod_complete')) ? eval($hook) : false;

[Floris]

I don't even know how to manually submit spammers from the site at the moment, integrated solution for 0.7 would be awesome

[imported_silkroad]

Originally Posted by Floris

I don't even know how to manually submit spammers from the site at the moment, integrated solution for 0.7 would be awesome

Agreed.... that is why I provided Mr. Pedigree the hooks in inlinemod.php where to add the code, so maybe he will be kind enough to add this to the next release!

I think the best place is in "Delete Posts as Spam" ... combined with a single option in the AdminCP for this product to automatically add the spammer's info to the StopForumSpam database when they "Delete Posts as Spam"....

Cheers!

[pedigree]

The code is already in 0.7 to submit spammers to the database as part of a ban/delete/cleanup function or in bulk via a user selection form but I will look at the inline hook. We have tried to shy away from the automatic submission as people always submit more innocent details this way, causing more people to come onto the forums and start +++++ing (seriously) and more work for us to then remove them (until you see the admin interface we have, youll understand why ) Rather than maybe an auotmatic submission, the mod would have to tick a box to confirm the submission...

[imported_silkroad]

Originally Posted by pedigree

The code is already in 0.7 to submit spammers to the database as part of a ban/delete/cleanup function or in bulk via a user selection form but I will look at the inline hook. We have tried to shy away from the automatic submission as people always submit more innocent details this way, causing more people to come onto the forums and start +++++ing (seriously) and more work for us to then remove them (until you see the admin interface we have, youll understand why ) Rather than maybe an auotmatic submission, the mod would have to tick a box to confirm the submission...

I understand, but that depends on your forums and the experience of the forum mods.

That is why that automatic banning in "Delete Posts as Spam" function should be an AdminCP option. When our mods ban spammers, they ban "real spammers" and we trust our very experienced mods (we have over 22), very much. We need to provide tools for them that require less clicks, not more.

On the other hand, a simple tickbox might be OK, if it is in the process flow of the "Delete Posts as Spam" inlinemod.php function and elsewhere, and is simply an additional tick-box on a form that is being submitted in the mod process.

I can understand how you might not want this on "some boards" with "some mods", but our board gets over 4M PVs a month, we have 22+ mods around the world, so we try to make the mods (who are really experienced professionals) job very easy in appreciation for the work they do.

Thanks for the update, BTW. I look forward to the next release, including the whitelist function, since it is a bit easy to send malicious info to a community database and blacklist innocent people (an unintended side-effect of community based access controls).

[jahshaka]

loving this it really helps, installed and voted for MOTM!!!