from localhost (jalapeno [127.0.0.1])
	by example.com (Postfix) with ESMTP id AD07516F1F
	for <zzzz@localhost>; Tue,  8 Oct 2002 10:57:11 +0100 (IST)
from n31.grp.scd.yahoo.com (n31.grp.scd.yahoo.com
    [66.218.66.99]) by dogma.slashnull.org (8.11.6/8.11.6) with SMTP id
    g983kpK31814 for <zzzz@example.com>; Tue, 8 Oct 2002 04:46:51 +0100
From sentto-2242572-56000-1034048852-zzzz=example.com@returns.groups.yahoo.com  Tue Oct  8 10:58:11 2002

> I guess MUA-level filtering is just a fallback for people who don't have
> 1) a burning, all-consuming hatred of junk mail, 2) root access to all
> mail servers they rely on, and 3) the ability and inclination to install
> an MTA with every bell and whistle tweaked to keep out junk mail.
Sure.  But for most people, changing their company's or ISP's server
requires years of lobbying, while they have total and immediate
control over their own MUA.
That said, I agree that we should offer a good solution to
postmasters, and I trust that your ideas are right on the mark!
--Guido van Rossum (home page: http://www.python.org/~guido/)

I think one step towards deployment is creating a re-usable tokenizer
for mail messages.  The current codebase doesn't expose an easy-to-use
or easy-to-customize tokenizer.
The timtest module seems to contain an enormous body of practical
knowledge about how to parse mail messages, but the module wasn't
designed for re-use.  I'd like to see a module that can take a single
message or a collection of messages and tokenize each one.
I'd like to see the tokenize by customizable, too.  Tim had to exclude
some headers from his test data, because there were particular biases
in the test data.  If other people have test data without those
biases, they ought to be able to customize the tokenizer to include
them or exclude others.
Jeremy

TP> A false positive *really* has to work hard then, eh?  The long
TP> quote of a Nigerian scam letter is one of the two that made
TP> it, and spamprob() looked at all this stuff before deciding it
TP> was spam:
Here's an interesting thing to test: discriminate words differently if
they are on a line that starts with `>' or, to catch styles like
above, that the first occurance on a line of < or > is > (to eliminate
html).
Then again, it may not be worth trying to un-false-positive that
Nigerian scam quote.
-Barry