This is a rework of the Pivot Blacklist by Marco. It’s a wrapper around this plugin providing you an administration panel and fully Nucleus integreated functionality.

There is a bug in all versions. This bug causes that rules in the form ‘domain.net’ will be interpreted as ‘domain?net’ whereby the ‘?’ stands for any character. I’m testing a solution for this problem.

Please note that the master blacklist list is gone. Please remove the blacklist URL from the plugin option once installed. Else, the failed blacklist update will slow down your blog’s loading as it keep trying to update the list.

rapid development of spam catching techniques. lot’s of bugfixes due to the conversion from pivot to nucleus.

In this version i’ve added the option to block visitors based on their referrer. This way you can take some load of the server by capturing the visitor really soon, just before you would serve him the webpage. This version also sports a plugin api. This way other plugins like np_chat and trackback can check submitted content for spam too. There is some discussion on this matter in the above metioned forum thread.

In 0.96 there is also the opportunity to block notorious spammers based on their ip-address. When a client hits your site with spam, the counter for that ip starts counting. As soon as he spams your site above the threshold (plugin option; default 10) the ip-address is added to the blocked-ip list. From now on, all requests coming from that address will be blocked immediatly. The current version can generate .htaccess snippets which you can incorporate in your exsisting .htaccess. This should stop the spammers at the gate, freeing some resources and memory of your server. The snippets are only generated for rules that are matched by blacklist.

For version 0.97 I’ve added another, new event which is available in Nucleus version 3.2 and onward. This new event makes the hacked action.php obsolete.

In this version the list retrieved from Jay Allen is converted differently; all . will be replaced by \. which is far better because it improves speed, and it solves a bug that the dot was interpreted as a wildcard instead of a real dot.

The following code can be incorporated in your plugin. If you do, the teststring will be checked for spam ...

global $manager;
if ($manager->pluginInstalled('NP_Blacklist')) {
  $spamcheck = array ('type'  => 'Referer', 'data'  => $body, 'return'  => false);
  $manager->notify('SpamCheck', array ('spamcheck' => & $spamcheck));
}