Antispam Bee

Descripción

Dile adiós a los comentarios de spam en tu blog o web de WordPress. Antispam Bee bloquea los comentarios y trackbacks de spam de forma efectiva, sin captchas y sin enviar información personal a servicios de terceros. Es gratuito, sin anuncios y cumple al 100% con el RGPD.

Resumen de características/ajustes

  • Confía en los comentaristas aprobados.
  • Confía en los comentaristas con un Gravatar.
  • Analiza la hora de los comentarios.
  • Permite comentarios sólo en un idioma determinado.
  • Bloquea o permite a comentaristas de ciertos países.
  • Trata el BBCode como spam.
  • Valida la dirección IP de los comentaristas.
  • Usa expresiones regulares.
  • Busca en la base de datos local de spam a los comentaristas previamente marcados como spammers.
  • Notifica a los administradores por correo electrónico sobre el spam entrante.
  • Elimina el spam existente después de n días.
  • Limita la aprobación a comentarios/pings (eliminará otros tipos de comentarios).
  • Selecciona los indicadores de spam para eliminar comentarios directamente.
  • Opcionalmente, excluye trackbacks y pingbacks de la detección de spam.
  • Opcionalmente, revisa los formularios de comentarios de spam en las páginas de archivo.
  • Muestra estadísticas de spam en el escritorio, incluyendo actualizaciones diarias de la tasa de detección de spam y el total de comentarios de spam bloqueados.

Soporte

Colabora

  • El desarrollo de este plugin se realiza en GitHub.
  • Los pull request de fallos documentados son muy apreciados.
  • Si crees que has encontrado un fallo (p. ej., estás experimentando un comportamiento inesperado), publícalo primero en los foros de soporte.
  • Si quieres ayudarnos a traducir este plugin puedes hacerlo en WordPress Translate.

Agradecimientos

Capturas

  • Ajustes de Antispam Bee

Instalación

  • If you don’t know how to install a plugin for WordPress, here’s how.

Requisitos

  • PHP 5.2.4 or greater
  • WordPress 3.8 o superior

Configuración

After you have activated Antispam Bee the plugin will block spam comments out of the box. However, you may want to visit Settings → Antispam Bee to configure your custom set of anti-spam options that works best for your site.

Preguntas frecuentes

Instrucciones de instalación
  • If you don’t know how to install a plugin for WordPress, here’s how.

Requisitos

  • PHP 5.2.4 or greater
  • WordPress 3.8 o superior

Configuración

After you have activated Antispam Bee the plugin will block spam comments out of the box. However, you may want to visit Settings → Antispam Bee to configure your custom set of anti-spam options that works best for your site.

Does Antispam Bee work with Jetpack, Disqus Comments and other comment plugins?

Antispam Bee works best with default WordPress comments. It is not compatible with Jetpack or Disqus Comments as those plugins load the comment form within an iframe. Thus Antispam Bee can not access the comment form directly.
It also won’t work with any AJAX-powered comment forms.

Does Antispam Bee store any private user data, and is it compliant with GDPR?

Antispam Bee is developed in Europe. You might have heard we can be a bit nitpicky over here when it comes to privacy. The plugin does not save private user data and is 100% compliant with GDPR.

Will I have to edit any theme templates to get Antispam Bee to work?

No, the plugin works as is. You may want to configure your favorite settings, though.

Does Antispam Bee work with shortened IPs?

Generally yes. However, commissioning the Antispam Bee plugin for canceled or shortened IP addresses in comment metadata is not recommended. Because the name and the e-mail address of the comments are not unique, an IP address is the only reliable measure. The more complete the stored IP addresses, the more reliable the assignment or detection of spam.

How can I submit undetected spam?

If the antispam plugin has passed some spam comments, these comments can be reported for analysis. A Google table was created for this purpose.

¿Antispam Bee con Varnish?

If WordPress is operated with Apache + Varnish, the actual IP address of the visitors does not appear in WordPress. Accordingly the Antispam-Plugin lacks the base for the correct functionality. An adaptation in the Varnish configuration file /etc/varnish/default.vcl provides a remedy and forwards the original (not from Apache) IP address in the HTTP header X-Forwarded-For:
if (req.restarts == 0) {
set req.http.X-Forwarded-For = client.ip;
}

Are there some paid services or limitations?

No, Antispam Bee is free forever, for both private and commercial projects. You can use it on as many sites as you want. There is no limitation to the number of sites you use the plugin on.

A complete documentation is available in the GitHub repository Wiki.

Reseñas

Works great and is privacy-friendly

Great plugin which is super easy to configure and catches comment spam absolutely reliable. I always recommend it.

Big thanks to pluginkollektiv for taking data protection seriously and making the plugin 100% compliant with GDPR with the latest version 2.8.

Leer todas las 141 reseñas

Colaboradores y desarrolladores

“Antispam Bee” es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

“Antispam Bee” ha sido traducido a 14 idiomas. Gracias a los traductores por sus contribuciones.

Traduce “Antispam Bee” a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN , o suscríbete al log de desarrollo por RSS .

Registro de cambios

2.8.1

  • Compatibilidad con PHP 5.3
  • Corrección de un error fatal producido por un trackback de spam
  • Para más detalles mira https://github.com/pluginkollektiv/antispam-bee/milestone/8?closed=1

2.8.0

  • Removed stopforumspam.com to avoid potential GDPR violation
  • Improves IP handling to comply with GDPR
  • Mejora la compatibilidad con PHP 7.2
  • Corrige un pequeño fallo en la vista móvil
  • Allow more than one language in language check
  • Mejoras menores en la interfaz
  • Elimina los archivos de traducción antiguos de ruso y holandés
  • Para más detalles mira https://github.com/pluginkollektiv/antispam-bee/milestone/4?closed=1

2.7.1

  • Fixes an incompatibility with Chrome autofill
  • Fixes some incompatibilities with other plugins/themes where the comment field was left empty
  • Compatibilidad con RTL
  • Solucionados algunos fallos de traducción/idioma
  • A new filter to add languages to the language check
  • For more details see https://github.com/pluginkollektiv/antispam-bee/milestone/6?closed=1

2.7.0

  • Country check is back again (thanks to Sergej Müller for his amazing work and the service page)
  • Improved Honeypot
  • Language check through Google Translate API is back again (thanks to Simon Kraft of https://moenus.net/ for offering to cover the costs)
  • More default Regexes
  • Unit Test Framework
  • Accessibility and GUI improvements
  • An english documentation is now available, too. Some corrections in the german documentation.
  • Some bugfixes – Among other things for WPML compatibility
  • For more details see https://github.com/pluginkollektiv/antispam-bee/milestone/3?closed=1

2.6.9

  • Updates donation links throughout the plugin
  • Fixes an error were JavaScript on the dashboard was erroneously being enqueued
  • Ensures compatibility with the latest WordPress version

2.6.8

  • added a POT file
  • actualizada la traducción al Alemán, añadida versión formal
  • updated plugin text domain to include a dash instead of an underscore
  • actualizado, traducido + formateado el README.md
  • updated expired link URLs in plugin and languages files
  • updated plugin authors

2.6.7

  • Removal of functions Block comments from specific countries and Allow comments only in certain language for financial reasons – more information (only german)

2.6.6

  • Switch to the official Google Translation API – more information (only german)
  • Release time investment (Development & QA): 2.5 h

2.6.5

  • Fix: Return parameters on dashboard_glance_items callback / thx @toscho
  • New function: Trust commenters with a Gravatar / thx @glueckpress
  • Additional plausibility checks and filters
  • Release time investment (Development & QA): 12 h

2.6.4

  • Consideration of the comment time (Spam if a comment was written in less than 5 seconds) – more information on Google+ (only german)
  • Release time investment (Development & QA): 6.25 h

2.6.3

  • Sorting for the Antispam Bee column in the spam comments overview
  • Code refactoring around the use of REQUEST_URI
  • Release time investment (Development & QA): 2.75 h

2.6.2

  • Improving detection of fake IPs
  • Release time investment (Development & QA): 11 h

2.6.1

  • Code refactoring of options management
  • Support for HTTP_FORWARDED_FOR header
  • Release time investment (Development & QA): 8.5 h

2.6.0

  • Optimizaciones para WordPress 3.8
  • Clear invalid UTF-8 characters in comment fields
  • Spam reason as a column in the table with spam comments

For the complete changelog, check out our GitHub repository.