Hi!

I have considered methods to let SPAMs which went under the spamassassin radar
(i.e. passed spamassassins check) but failed the member of list check (which
has so far been a 100% filter for this category) to be somehow sent into the
spamassassin learning process, so that list-admins/moderators can teach the
spamassassin filter. When doing this on a larger site like the one which my
mailman installation sits on also means that I don't have direct access to the
spamassassin processing, so some form of passing may be necessary.

I've toyed with these alternatives:

1) The moderator gets the option of click a "Is SPAM" check-box for a caught
   message. A site-configuration decides weither this means forwarding the spam
   to an email address, tossing it on an MBOX file or saving it as a separate
   file.

2) The moderator gets a different default forward email address to a hidden
   list ([EMAIL PROTECTED]), this hidden list archives the emails as normal but
   has normally no members.

3) Have the front-end of the first proposal but actually use the normal email
   listing mechanism of the second proposal.

The later of these are really just a quick-and-dirty implementation of the
first, but it does have its merits.

Any thoughts?

Cheers,
Magnus
_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Reply via email to