Release status: stable
|Description||Uses stopforumspam.com to prevent spam|
|Latest version||0.2.0 (2014-04-02)|
|License||GNU General Public License 2.0 or later|
Translate the StopForumSpam extension if it is available at translatewiki.net
|Check usage and version matrix.|
|Open tasks · Report a bug|
The StopForumSpam extension allows wikis to utilize and contribute data to stopforumspam.com. It features automatic IP blocking, confidence variables, and an easy interface for administrators to submit data. Use of the IP blacklist requires that you use some kind of object caching; it won't work if you have $wgMainCacheType set to CACHE_NONE. If neither APC or Memcached is an option, the simplest approach is to fallback to storing the object cache in your MySQL database. The following preset (in LocalSettings.php) will do that: $wgMainCacheType = CACHE_DB;
- Download and place the file(s) in a directory called
- Add the following code at the bottom of your LocalSettings.php:
wfLoadExtension( 'StopForumSpam' );
- Done – Navigate to Special:Version on your wiki to verify that the extension is successfully installed.
$wgSFSAPIKey- API key, can be obtained at http://stopforumspam.com/signup
$wgSFSIPListLocation- location of an unzipped IP address blacklist
stopforumspam- allows users to optionally submit data. Useless without "block" right.
sfsblock-bypass- allows users to bypass blacklisted IP blocks
When blocking a user, a checkbox will appear to submit the user's data. Data will only be submitted if the user is logged in, has an email address set, and has an IP address stored. This feature requires either $wgPutIPinRC to be enabled, or the CheckUser extension installed.
When using the AbuseFilter, a variable named "sfs_confidence" is added. The value is a float between 0 and 1, where 0 is that they are not a spammer, and 1 means 100% they are a spammer.
You can download IP blacklists, and import them using the
updateBlacklist.php script. StopForumSpam has several lists, recommend http://www.stopforumspam.com/downloads/listed_ip_30_all.zip. Unzip it and then point $wgSFSIPListLocation in the LocalSettings.php file at it. Recommend updating it with a nightly cronjob.
If that IP tries to edit, or a user tries to edit through that IP address, they will be prevented from editing. To exempt a user from being blocked, give them the
sfsblock-bypass userright. This feature requires object caching to be setup.