Releases for Spambot

#3194278: Check if account matches a known spammer does not work even if API returns a match
#3211503: Regression: Fixing caching breaks all test to returned $data

#3161424: “Check if this account matches a known spammer” throws an exception error

#2795493: Coding standard issue
#2795009: Spambot never advances after cron run if all examined accounts are blocked

A minor update.

#1884754: Provide links to the search results on SFS
Fix path typo (7.x)

This is a significant update to spambot.module.

Reporting of accounts as spammers has been rewritten in light of changes to www.stopforumspam.com policy. Reporting must provide evidence.

Automatic reporting, or reporting without evidence, has been removed.

List of changes:

Tidy logging messages.

See SA-CONTRIB-2012-142 - Spambot - Cross Site Scripting (XSS) for details.

Bump release to 7.x-1.0.

Fixes #1353178: Spurious 'Error reporting account ...' messages.

Development snapshot.

First 7.x release. This is a port of the 6.x-3.x branch. There are no new features.

Some new features and a bugfix or two:

Change criteria booleans to configurable threshold values.
Don't check IP 127.0.0.1.
Add auto-reporting of blocked user registrations as spammers.
Fix typo bug: cron scan of users didn't take action.

* New settings section in admin/settings/spambot
* Report users to Spambot in the user administration
* Configurable Go Away message