From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Training for ham and training for spam
Date: Wed, 29 Oct 2003 14:50:42 -0500 [thread overview]
Message-ID: <4n65i7vn59.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <76u15ru93j.fsf@newjersey.ppllc.com> (Jake Colman's message of "Wed, 29 Oct 2003 14:39:28 -0500")
On Wed, 29 Oct 2003, colman@ppllc.com wrote:
> Is it truly necessary to train for ham or can I just train for spam.
> I have a number of mailing lists that filter into their own folders
> and are mostly spam-free. Is there any benefit to classifying them
> as ham folders and specifying an exit processor? Or will it just
> add processing time?
Training for ham is useful, and pretty much every statistical filter
recommends it. The decision of whether it's worth the CPU time and
memory is up to you and depends on the particular filter.
> On the other hand, I have a group that mostly gets spam so I have
> classified it as a spam group and I do pass it through the exit
> processor.
>
> Does this make sense?
Sure.
Ted
next prev parent reply other threads:[~2003-10-29 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 19:39 Jake Colman
2003-10-29 19:50 ` Ted Zlatanov [this message]
2003-10-29 19:54 ` Michael Shields
2003-10-29 14:26 ` Ian Dobbie
2003-10-30 14:39 ` Michael Shields
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=4n65i7vn59.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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).