• First of all, thank you for this excellent plugin. Really appreciate it!

    This is a request for compatibility with Antispam Bee. I am currently using Antispam Bee as a GDPR compliant anti-spam solution, however, I noticed that spam comments which are blocked by the AntispamBee plugin are still saved in the GDPR Framework’s consent database (as spammers automatically check the consent checkbox).

    The downside I’m having currently is that my sql database is getting full of consent logs – but these aren’t from legitimate commenters – most of them are spammers. While the spam was blocked, the consent’s are still recorded (but I don’t need/want to store them).

    So my request is, could you provide crosschecking/integration with Antispam Bee to somehow check if comments have been tagged as spam, before they are saved in the consent database? Or alternatively delete entries from the consent database if they are confirmed as spam via Antispam Bee.

    As most people will be needing a GDPR-compliant antispam solution, this type of compatibility should benefit most people and prevent our consent databases filling up with spam entries.

    Thanks!

    The page I need help with: [log in to see the link]

  • The topic ‘Compatibility Request: Antispam Bee Plugin’ is closed to new replies.