The spam filtering works in 3.x, but relative to 1.x I miss the following:

- There were custum filters, where I could enter own expressions, without "waiting on the bayesian" ...
This was a list in which I could ad my own entries. Will this come back?

- The new "filter options" mostly contain "notify visitor".
I prefer "not to notify", because there are mostly spam engines, and I do not want to give them feedback,.
(Alternatively as feature: notification only 'below a certain level', but that sounds to be luxury ;-)
If a human is mistakenly being filtered, I hope they come over to the contact page or email.

- There was an option to delete the spam filtered entries from the db automatically after some time. I hope to get this feature back too.

Comments

jeremy’s picture

Title: Custom Filters, notify... » Re-introduce custom filters

Please file one feature request per issue. Filing multiple requests in one issue is confusing and things get dropped.

Updating title to reflect your first feature request -- you can open new issues for your other requests if you're still interested in them.

Yes, custom filters can easily be added back through a plug-in module. And yes, I do intend to support them in this release. Patches are also welcome.

jeremy’s picture

Assigned: Unassigned » jeremy

Assigning to myself, as I want this implemented before we have a beta release.

jeremy’s picture

When implementing custom filters, be sure to test filters before adding them.

jeremy’s picture

I just committed code for managing custom filters. They aren't actually used yet, but that should be the easy part. There's also not yet code for importing filters from the 5.x-1.x version of the spam module.

jeremy’s picture

With this code check in, custom filters are now functional. All that's left to implement are upgrades from the 5.x-1.x modules.

jeremy’s picture

Status: Active » Fixed

Committed code to upgrade custom filters from the 5.x-1.x spam module.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.