GNOME Bugzilla – Bug 269098
Make the junk filter pluggable
Last modified: 2013-09-13 00:47:26 UTC
Integration with SpamAssassin is a reasonable choice. However, there are other solutions available, with their own advantages and drawbacks. There should be choice which spam filter to use. Pesonally, I'd kill for a bogofilter plugin, because bogofilter is fast, it doesn't require N copies of the Perl runtime unfolding themselves in memory, and it does wonders to my spam :)
"pluggable" also means "eplugin". achieving this one here would immediately solve bug 259506 (is it a dup?), bug 272926 about the docs would also be affected. bug 272411 could also be a duplicate of this one here. :-/ bug 257091 says that junk ui shouldn't be displayed when *spamassassin* is not installed (hmm... does it get blocked by this one here? can the eplugin check if spamassassin is installed? either not i guess...). bug 258538 is a request to involve other programs than spamassassin to filter spam.
...and bug 273649 (support for a GUI for spamassassin list entries and remote tests).
*** Bug 231748 has been marked as a duplicate of this bug. ***
this would require a framework for pluggable junk modules first. something similar to the em-format-hook system.
I have created a New hook which allows anybody to plug there spam filter in. The code is checked in CVS Head. The default spam assasin mechanism is pulled out from being the default and is an e-plugin now with the name "sa-junk-plugin". This can be taken as an example to write other plugins (using different spam filters).