From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: spam/ham exit processors
Date: Tue, 04 Nov 2003 22:31:27 +0000 [thread overview]
Message-ID: <87n0bbzry8.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: <761xsorq5v.fsf@newjersey.ppllc.com>
Jake Colman <colman@ppllc.com> writes:
> I MUST be missing something here. Don't the filters _already know_ that
> the messages were spam? How else did they end up in the intermediate folder?
> Why do you need to train if it's been trained?
No, the filters don't _know_. They just _predict_ that with a
sufficiently high probability, the message is spam.
Sometimes, they predict wrong so it's good to double-check.
Double-checking is not a big problem because finding the one ham in
100 messages is quite easy, whereas finding 50 hams in 100 messages is
difficult and tedious.
Kai
next prev parent reply other threads:[~2003-11-04 22:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 13:47 Jake Colman
2003-11-03 18:41 ` Ted Zlatanov
2003-11-03 20:29 ` Kai Grossjohann
2003-11-03 20:31 ` Russ Allbery
2003-11-03 21:26 ` Ted Zlatanov
2003-11-03 21:43 ` Russ Allbery
2003-11-04 2:28 ` Ted Zlatanov
2003-11-04 3:03 ` Russ Allbery
2003-11-04 15:11 ` Jake Colman
2003-11-04 16:17 ` Ted Zlatanov
2003-11-04 17:37 ` Jake Colman
2003-11-04 22:31 ` Kai Grossjohann [this message]
2003-11-03 21:25 ` Ted Zlatanov
2003-11-03 22:10 ` Kai Grossjohann
2003-11-04 2:20 ` Ted Zlatanov
2003-11-04 15:08 ` Jake Colman
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=87n0bbzry8.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.de \
/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).