Version: 1.0.3, by nhawk
Developer Last Online: May 2021
Category: Anti-Spam Options -
Version: 4.1.5
Rating:
Released: 02-23-2012
Last Update: 12-11-2013
Installs: 72
No support by the author.
THIS ADD-ON IS NO LONGER AVAILABLE AND IS NOT SUPPORTED
This is an add-on that is designed with vBulletin 4.1.5. It may not work on earlier versions of vBulletin. It is known to be working on vB versions 3.8.7, 4.0.7 and 4.1.5 through 4.2.0. I don't know if it is compatable with all versions of vB or not.
On my site, I receive quite a few PMs asking me how I prevent spam from being posted there. While I can't release everything I use because some of it is server based (external from vBulletin), I can release one of the lines of defense that I use.
This mod allows you to ban Hostnames and Useragents from registering on your site.
If a hostname or useragent contains any of the words you specify and they are trying to register, they are presented with an error telling them they are forbidden from registering on your site. And no registration screen ever appears.
In the event the hostname is blank, a WHOIS can be performed to establish the identity of the system being used to register.
The 'External Content' pulled by this mod is only the WHOIS information when that is enabled.
WARNING: This mod has the potential of banning humans from registering. Choose what words you use carefully.
Personally, I am not very concerned about banning an occasional human from registering. So, from time to time my system may ban a human that uses an anonymous proxy.
NOTE: This mod has a 'Don't Ask, Don't Tell' clause. Please don't post telling people what words to ban. We don't need spammers getting around this mod by reading posts telling them what is being filtered.
REQUIREMENTS: In order for the WHOIS function used in this mod to work properly, your server must have OPENSSL installed.
* INSTALLATION *
---------------------
1) Upload the contents of the 'upload' folder to your forum's root.
(If your forum's location is http://www.example.com/forums/, the root is /forums/)
2) Import the product XML file (product-hostusercheck.xml) into the Product Manager in AdminCP.
3) Take some time to set the options in ACP->Settings->Options->Prevent Hostname or Useragent from Registering.
4) Be sure to turn on the mod when setting options in ACP->Settings->Options->Prevent Hostname or Useragent from Registering.
* History (Changelog) *
-----------------------------
1.0.3 (December 12, 2013)
- Fix hostname not being checked under certain circumstances.
1.0.2 (March 1, 2012)
- Fix error on registration page when Useragent or Hostname to ban is blank.
1.0.1 (February 24, 2012)
- Wrong hook being used for one of the plugins.
1.0.0 (January 22, 2012)
- Public Release
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
which version. and is it for vbulletin version or this mod version. for a clear info let me tell you, i don't want to upgrade vb to higher than 4.1.3 thinking many of the mod will stop working. Please clear your solution. Thanks.
The add-on version. You have version 1.0.0. I uploaded version 1.0.1
Download the file again, and re-install the XML file. Be sure to set the 'Allow Overwrite' to yes when you update.
If you tell them they are blocked from registering, they will know there some detection method involved and find a way to work around it. Why not just have the standard vBulletin message, "The Administrator has Disabled Registration" come up, instead of the gotcha?
This is the same thing, but also allows redirect off-site with no 'gotcha' either:
If you tell them they are blocked from registering, they will know there some detection method involved and find a way to work around it. Why not just have the standard vBulletin message, "The Administrator has Disabled Registration" come up, instead of the gotcha?
This is the same thing, but also allows redirect off-site with no 'gotcha' either:
I've been running this for a very long time (as in years) on a few different sites. Nobody has gotten around it yet.
And it's not quite the same as the mod you posted. This one also bans hostnames, which is a HUGE difference that works wonders.
EDIT: The only reason for the 2 updates to this were...
Update 1) I exported from my development server which I forgot was set to a different hook.
Update 2) I never expected anyone to leave a field blank.
I've been running this for a very long time (as in years) on a few different sites. Nobody has gotten around it yet.
And it's not quite the same as the mod you posted. This one also bans hostnames, which is a HUGE difference that works wonders.
EDIT: The only reason for the 2 updates to this were...
Update 1) I exported from my development server which I forgot was set to a different hook.
Update 2) I never expected anyone to leave a field blank.