AntiSpam
Explanation
The AntiSpam Tools application gives an administrator two independent defences against spam. Spam Checking refuses a page at save time when the page looks like spam and disables the account that submitted it, while Spam Cleaning finds spam that is already on the wiki and removes it together with its author. Both read everything they need from wiki pages in the AntiSpam space, and every screen they provide requires programming rights.
The keyword list and every cleaning screen are reached from the application home page.
Spam Checking needs no attention once its keyword list is populated: Configure Spam Keywords builds that list, and Spam Detection When Saving a Page describes what is inspected and what a match costs the account.
Spam Cleaning is the day-to-day work: Delete Spam Pages and Users removes the spam revisions and the accounts behind them, Review the Latest Changes for Spam spots an attack in the event list, and Delete Inactive Users removes accounts that registered and never contributed.
What makes running any of this on a live wiki safe is that neither mechanism can touch a protected user. The lists they read, and the two settings they take from the wiki administration, are listed in AntiSpam Configuration.
FAQ
Can the application be installed on a subwiki?
No. It declares the main wiki as its only namespace, so a farm has one installation covering every wiki.
Do I have to use both mechanisms?
No, they are independent. An empty keyword list leaves Spam Checking inert, and Spam Cleaning works whether or not any keyword is defined.
Where do I see what has been caught?
On the AntiSpam.Logs page. AntiSpam Configuration describes it and the other pages Spam Checking writes to.
More
To find more about the current topic, you can search or use the table below and filter the columns to narrow your choices.
