From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Jake Colman <colman@ppllc.com>, ding@gnus.org
Subject: Re: ham training and gnus-expirable-mark
Date: Fri, 31 Oct 2003 11:52:19 -0500 [thread overview]
Message-ID: <4nism58i4c.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <u65i6c4i1.fsf@coas.oregonstate.edu> (Jody Klymak's message of "Thu, 30 Oct 2003 22:20:38 -0800")
> Jake Colman <colman@ppllc.com> writes:
> > 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?
> I had exactly the same difficulty:
> C-h v spam-process-ham-in-spam-groups
Also spam-process-ham-in-nonham-groups could be useful to some.
> Ted, maybe this should default to t?
I think that's a good idea. spam-process-ham-in-nonham-groups should
still be nil though. Anyone against?
Ted
prev parent reply other threads:[~2003-10-31 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 23:36 Jake Colman
2003-10-31 6:20 ` Jody Klymak
2003-10-31 16:52 ` Ted Zlatanov [this message]
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=4nism58i4c.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=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).