From: Jake Colman <colman@ppllc.com>
Cc: ding@gnus.org
Subject: Re: spam/ham exit processors
Date: Tue, 04 Nov 2003 12:37:16 -0500 [thread overview]
Message-ID: <761xsorq5v.fsf@newjersey.ppllc.com> (raw)
In-Reply-To: <4nvfq0ds72.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Tue, 04 Nov 2003 11:17:05 -0500")
>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
TZ> On Tue, 04 Nov 2003, colman@ppllc.com wrote:
>>>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
>>
TZ> I think you want an intermediate "spam" group with its
TZ> process-destination set to "train", and then run
TZ> spam-processors on "train" only. So all spam will flow to
TZ> "spam" and then you can pop ham back out of "spam" before it
TZ> all gets moved into "train."
>>
TZ> I like the "train" approach also because Bogofilter can be
TZ> easily run on all those messages from the command line.
>>
>> But if the messages were already filtered into the "intermediate"
>> spam group it would seem to indicate that spam.el (through whatever
>> statistical tool is being used) already determine it to be spam. So
>> why do you need to ever move messages from one spam group into
>> another?
TZ> Because I like to verify (visually) that messages are spam before
TZ> training my filters on them. This has given me the result of 2 spam
TZ> messages in the last week that got through, out of a few thousand
TZ> spams. Some people don't want the inconvenience of spending time
TZ> looking at spams, so they train on whatever is in the spam folder.
TZ> That's fine too.
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?
--
Jake Colman
Principia Partners LLC Phone: (201) 209-2467
Harborside Financial Center Fax: (201) 946-0320
902 Plaza Two E-mail: colman@ppllc.com
Jersey City, NJ 07311 www.principiapartners.com
next prev parent reply other threads:[~2003-11-04 17:37 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 [this message]
2003-11-04 22:31 ` Kai Grossjohann
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=761xsorq5v.fsf@newjersey.ppllc.com \
--to=colman@ppllc.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).