Extension:Antispam
This extension is currently not actively maintained! Although it may still work, any bug reports or feature requests will more than likely be ignored. |
![]() Release status: unmaintained |
|
---|---|
Implementation | User activity , Page action |
Description | Client extension for cloud anti-spam service CleanTalk.org. |
Author(s) | Denis Shagimuratov |
Latest version | 2.3 (2019-12-17) |
MediaWiki | 1.19+ |
PHP | PHP 5.3+ |
Database changes | Yes |
License | GNU General Public License 2.0 or later |
Download | GitHub: Note: |
|
|
|
|
The Anti-spam extension is a client-side application for a commercial cloud anti-spam service, cleantalk.org.
Anti-Spam service
The CleanTalk Cloud Service provides automatic and invisible protection from spam for websites. CleanTalk analyzes user behavior and evaluates the parameters of a completed form.
When installed on your website the Anti-Spam Module captures the behavior parameters of a visitor or a spambot. These parameters are being assessed and the service makes a decision — to post the visitor's message or to define it as spam and reject it. Based on such checks, the service forms its own list of email addresses used by spambots. Likewise, visitor registrations are being checked too. The service adds not only email addresses to the global blacklist but also IP addresses and domains of the websites that are promoted through spam mailout.
Spam Firewall feature
This option allows blocking spam-bots before they access MediaWiki content. CleanTalk collects spam bots activity data on websites, IP addresses of the most active spam bots are added to the Spam Firewall database. The service intercepts any HTTP(POST/GET) requests to a site and IP address it contains. If an IP address is included in CleanTalk blacklist of most spam active IPs, it will get a special page, if it is a real visitor then it proceeds to the site. That is completely transparent to the visitors. The results of Spam FireWall are logged and available in your control panel.
Real-Time Email Address Existence Validation
To validate that users sign up with their real email address, the CleanTalk server will perform email account existence checks using SMTP response.
Private blacklist/whitelist
Automatically blocks comments and registrations from your private black IP/email address list. This option helps to strengthen the protection from manual spam or block unwanted comments from users. You can add not only the certain IP addresses but also a separate subnet to your personal blacklist. The extension allows blocking or whitelisting emails for registration using wildcards, for example, "*@mail.com" will block/allow every address ending on @mail.com.
Blocking users by country
The external service can be used to automatically block comments and registrations from specific countries.
Stoplist by words
Comments that contain specific words can be forbidden.
ScreenshotsEdit
InstallationEdit
- Download and place the file(s) in a directory called
Antispam
in yourextensions/
folder. - Add the following code at the bottom of your
LocalSettings.php
:require_once "$IP/extensions/Antispam/Antispam.php";
- Done – Navigate to Special:Version on your wiki to verify that the extension is successfully installed.
Configuration parametersEdit
To run extension
- Get Access key
Place the Access key in the LocalSettings.php with the variable $wgCTAccessKey
. Note : you need to put it after loading the extension using require_once
or wfLoadExtension()
.
- Set as you wish true or false the parameter
$wgCTNewEditsOnly
Frequently Asked QuestionsEdit
- Should I change anything in the extension's settings or in my CleanTalk Control Panel when I switch my website from HTTP to HTTPS or vice versa?
No, the extension will work regardless of the protocol.
- After installation, on creation of a test user, I get error: Fatal exception of type "Wikimedia\Rdbms\DBQueryError". How to fix?
- temporarily add
require_once "$IP/extensions/Antispam/Antispam.php";
into LocalSettings.php, verify that the extension was loaded on the version page, then replace with
wfLoadExtension( 'Antispam' ); - Don't set the key in the extensions/Antispam/Antispam.php file, but in LocalSettings.php file as variable $wgCTAccessKey below the load instruction.
- temporarily add