From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: spam-stat.el and mime
Date: Tue, 20 Jan 2004 19:17:48 -0500 [thread overview]
Message-ID: <4nhdyqi28j.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <m3llo3mada.fsf@defun.localdomain> (Jesper Harder's message of "Tue, 20 Jan 2004 06:56:17 +0100")
On Tue, 20 Jan 2004, harder@ifa.au.dk wrote:
> Please try the attached code (it increased my spam recognition rate
> by 4 percentage points).
Jesper,
other than renaming to spam-wash.el (to be consistent with spam-stat
and spam-report), your code looks good. Has anyone else tried it?
I'd like to use it, since you say it's much faster than Andrew's
original code.
Thanks
Ted
next prev parent reply other threads:[~2004-01-21 0:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 16:43 Andrew Cohen
2004-01-11 20:37 ` Adam Sjøgren
2004-01-12 4:47 ` Jesper Harder
2004-01-12 21:37 ` Ted Zlatanov
2004-01-13 19:42 ` Adam Sjøgren
2004-01-20 5:56 ` Jesper Harder
2004-01-21 0:17 ` Ted Zlatanov [this message]
2004-01-21 20:41 ` Adam Sjøgren
2004-01-22 7:30 ` Jesper Harder
2004-01-22 13:49 ` Reiner Steib
2004-01-23 1:15 ` Jesper Harder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4nhdyqi28j.fsf@collins.bwh.harvard.edu \
--to=tzz@lifelogs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).