From: Jake Colman <colman@ppllc.com>
Subject: ham training and gnus-expirable-mark
Date: Thu, 30 Oct 2003 18:36:48 -0500 [thread overview]
Message-ID: <76fzha1enj.fsf@newjersey.ppllc.com> (raw)
I've figured out why my ham was not being trained. Many of mailing lists are
sety up as auto-expire. Messages with the gnus-expirable-mark are not passed
on to the ham processor. If I give the messages the gnus-del-mark the
message gets trained.
Some related questions:
1) Should this be considered a problem? Why not allow me to use the contents
of an auto-expiry group for ham training?
2) In a spam group, how do I mark ham so that it can be sent for training? I
have specified both spam and ham processors, I removed the gnus-spam-mark
and replace it with a gnus-del-mark but that does not seem to do the
trick. Did I miss something or (as I think the manual implies) is this
not possible? If not, I guess the only thing to do is to specify a ham
group for the non-spam contents so that it can get moved over and then
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 reply other threads:[~2003-10-30 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 23:36 Jake Colman [this message]
2003-10-31 6:20 ` Jody Klymak
2003-10-31 16:52 ` Ted Zlatanov
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=76fzha1enj.fsf@newjersey.ppllc.com \
--to=colman@ppllc.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).