No, hits=-2.6 required=5.0
	tests=AWL,EMAIL_ATTRIBUTION,KNOWN_MAILING_LIST,REFERENCES,
	      T_NONSENSE_FROM_70_80,USER_AGENT,USER_AGENT_MOZILLA_UA,
	      X_ACCEPT_LANG
	version=2.50-cvs

No, hits=-9.1 required=5.0
	tests=AWL,KNOWN_MAILING_LIST,NO_REAL_NAME,SIGNATURE_SHORT_DENSE,
	      T_NONSENSE_FROM_10_20
	version=2.50-cvs

from localhost (jalapeno [127.0.0.1])
	by jmason.org (Postfix) with ESMTP id 1152C16F03
	for <jm@localhost>; Fri, 20 Sep 2002 11:30:18 +0100 (IST)
from jalapeno [127.0.0.1]
	by localhost with IMAP (fetchmail-5.9.0)
	for jm@localhost (single-drop); Fri, 20 Sep 2002 11:30:18 +0100 (IST)
from egwn.net (ns2.egwn.net [193.172.5.4]) by
    dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id g8K5NIC23544 for
    <jm-rpm@jmason.org>; Fri, 20 Sep 2002 06:23:18 +0100
from mail.j2solutions.net (seattle.connectednw.com
    [216.163.77.13]) by egwn.net (8.11.6/8.11.6/EGWN) with ESMTP id
    g8K5Dcf06500 for <rpm-list@freshrpms.net>; Fri, 20 Sep 2002 07:13:38 +0200
from yoda (12-231-69-107.client.attbi.com
    [::ffff:12.231.69.107]) (AUTH: CRAM-MD5 hosting@j2solutions.net) by
    mail.j2solutions.net with esmtp; Thu, 19 Sep 2002 22:13:32 -0700
Sylpheed version 0.7.5claws (GTK+ 1.2.10; i386-redhat-linux)
From rpm-list-admin@freshrpms.net  Fri Sep 20 11:30:18 2002

Have you thought of bumping up sylpheed-claws?  I see sylpheed got a

>>>>> "NS" == Neil Schemenauer <nas@python.ca> writes:
NS> Writing an IMAP server is a non-trivial task.
That's what I've been told by everyone I've talked to who's actually
tried to write one.
NS> Alternatively, perhaps there could be a separate protocol and
NS> client that could be used to review additions to the training
NS> set.  Each day a few random spam and ham messages could be
NS> grabbed as candidates.  Someone would periodically startup the
NS> client, review the candidates, reclassify or remove any
NS> messages they don't like and add them to the training set.
I think people will be much more motivated to report spam than ham.  I
like the general approach that copies of random messages will be
sequestered for some period of time before they're assumed to be ham.
Matched with a simple spam reporting scheme, this could keep the
training up to date with little effort.  I've sketched out an approach
a listserver like Mailman could do along these lines and if I get some
free time I'll hack something together.
I like the idea of a POP proxy which is classifying messages as
they're pulled from the server.  The easiest way for such a beast to
be notified of spam might be to simply save the spam in a special
folder or file that the POP proxy would periodically consult.
-Barry