en Documentation
The range of functions of the Antispam plugin for WordPress is manageable and is mainly focused on the defense of spam entries via comments and pings. Most functions of the application can be controlled via the panel with settings to determine the desired result of the protection. Each individual option of the tool is presented below. Since version 2.4.5, the option page consists of three main columns with choices. The columns are flexible and lined up side by side depending on the width of the window. In the following, the individual columns are presented as separate areas with plugin settings.
Moved to https://antispambee.pluginkollektiv.org/documentation/#antispam-filter
Moved to https://antispambee.pluginkollektiv.org/documentation/#trust-approved-commenters
Moved to https://antispambee.pluginkollektiv.org/documentation/#trust-commenters-with-a-gravatar
Moved to https://antispambee.pluginkollektiv.org/documentation/#consider-the-comment-time
Moved to https://antispambee.pluginkollektiv.org/documentation/#bbcode-links-are-spam
Moved to https://antispambee.pluginkollektiv.org/documentation/#validate-the-ip-address-of-commenters
Moved to https://antispambee.pluginkollektiv.org/documentation/#use-regular-expressions
Moved to https://antispambee.pluginkollektiv.org/documentation/#look-in-the-local-spam-database
Moved to https://antispambee.pluginkollektiv.org/documentation/#block-comments-from-specific-countries
Moved to https://antispambee.pluginkollektiv.org/documentation/#allow-comments-only-in-certain-language
Moved to https://antispambee.pluginkollektiv.org/documentation/#advanced
Moved to https://antispambee.pluginkollektiv.org/documentation/#mark-as-spam-do-not-delete
Moved to https://antispambee.pluginkollektiv.org/documentation/#notification-by-email
Moved to https://antispambee.pluginkollektiv.org/documentation/#not-save-the-spam-reason
Moved to https://antispambee.pluginkollektiv.org/documentation/#delete-existing-spam-after-x-days
Moved to https://antispambee.pluginkollektiv.org/documentation/#limit-approval-to
The plugin created artificially comment form and which is filled by most spam bots recognizes nearly 99 percent of the total spam volume in WordPress blogs. The False Positive rate, on the other hand, equals zero. Why then keep such spam and be notified via e-mail? Does not have to be mandatory.
Antispam Bee 2.4 brings an internal filter, which immediately deletes the detected spam depending on the reason (see below). In this way, the administrator can only keep spam entries with more error-prone causes (language, country limit etc.) in the comment area of the blog. For control or learning.
For this purpose, the Antispam plugin provides a list of possible suspicious reasons to choose from. If a comment or trackback comes up with one of the reasons from this - user selected - list, the plugin removes the newcomer without hesitation. "Parasites", which are classified for reasons other than spam, are marked by Antispam Bee and Antispam Bee will sent a suitable notification depending on the setting.
Implementation: Antispam Bee 2.4
Moved to https://antispambee.pluginkollektiv.org/documentation/#statistics-on-the-dashboard
Moved to https://antispambee.pluginkollektiv.org/documentation/#spam-counter-on-the-dashboard
Moved to https://antispambee.pluginkollektiv.org/documentation/#do-not-check-trackbacks-pingbacks
Moved to https://antispambee.pluginkollektiv.org/documentation/#comment-form-used-outside-of-posts
Moved to https://antispambee.pluginkollektiv.org/documentation/#suspicion-of-spam-detection
Moved to https://antispambee.pluginkollektiv.org/documentation/#log-file-for-fail2ban
We recommend not to delete spam detected by Antispam Bee immediately, but to keep it in the WordPress database - the plugin option "Mark as spam, do not delete" is responsible for this. The reason: If the function "Look in the local spam database" is activated, Antispam Bee considers already detected spam comments.
But depending on the size of the WordPress project, the database runs full - exaggerated ;) Although the plugin can automatically clean up the database after X days and delete older entries, there is a way to get by with a much smaller amount of suspicious comment entries. Namely:
Activate the plugin option "Delete comments by spam reasons" and select "Honeypot" there. Save settings.
From now on Antispam Bee deletes every spam comment that has filled in the invisible input field - this is 100 % spam bot. Such comments do not need to be saved in WordPress, because bots of this kind always use the same technique to send the comment and are reliably recognized by Antispam Bee without having to access the local file.
After the conversion, Antispam Bee really only stores spam comments that have been "noticed" by other filter techniques. The number of local spam comments is thus reduced many times over, without any restrictions on anti-spam protection.