[Mailman-Developers] Google Summer of Code - Spam Defense
lists at mschuette.name
Thu Mar 27 19:37:29 CET 2008
Terri Oda schrieb:
> Even if it's not Mailman's responsibility to do the scanning, it can
> be incredibly helpful to make the mailman interface aware of and able
> to interact with scanning technologies.
I would suggest to be more specific: which functions do we wish to have,
what is necessary to implement them, and is the effort worth it?
- run Spamassassin (or another classification) on all messages:
IMHO this is the MTA's job, so let's assume it already happens
- hold or discard Messages marked as spam:
Set up Spam-Filter rules with "X-Spam-Flag: YES", "X-Spam-Level:
\*\*\*\*\*\*\*", or whatever. It is not the most user friendly
interface, but certainly the most configurable and flexible one.
- give feedback to train a classifier:
The admindb interface already has a checkbox to save spam.
IMHO it should be given a better label (cf.
but it exists and the site administrator only has to train the saved
messages regularly. (On my site I deliver them into a shared IMAP
spam-folder for review and training.)
- reclassify mails in the hold-queue:
This sounds quite promising (I know some people do this successfully
with IMAP inboxes).
But as already mentioned this requires additional effort from the site
admins, which probably will not change a working Amavis setup for this.
P.S.: I hope this mail did not become too negative. I am always in
favour of better and more user friendly spam filters. But there are
quite a lot of spam-related patches already and any new approach should
be clearly better than the already existing hooks and functions.
Otherwise it is just a waste of time which should be used for other
problems (MM3 comes to mind).
More information about the Mailman-Developers