[Listwork] Patches for SpamAssassin/Mailman

[Pabs]

On Sat, 2004-09-25 at 14:55 +0200, Alster wrote:

> yummie, sounds great. Just in case we decide to use it, is there any
> patch for per list bayes filtering (list specific bayesian word lists
> would be very cool IMO)?

That can be done with the "discard" address - the way i see it, we would
add an extra action in the admin interface - mark as spam. This would
discard the message and forward it to the "discard" address, which would
check which it came from, run it thru sa-learn (adding keywords to the
bayes db for that list), and perhaps put it up for review by spam
admins, who might then decide if it is really commercial spam that needs
to be reported to one of those spam hash databases - like razor or
pyzor. Well, in the ideal world, mebbe, but people in indy look at other
kinds of spam each day on their newswires, I doubt they wanna see UCE as
well. I seem to remember jb has already done a patch for this, I may be
going crazy tho.

Anyways jb, the per-list spamass variables look fine.

Also, as far as spamassassin 3.0 goes, the SpamAssassin.py should be
just fine, as spamass3 speaks the same spamc protocol version (even
speaks some older versions!!) as 2.64, so there will be no troubles
there.

-- 
Bye,
Pabs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.indymedia.org/pipermail/listwork/attachments/20040925/02c3ed3c/attachment.pgp