From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Spam.el: Train in ham?
Date: Fri, 16 Apr 2004 11:00:10 -0400 [thread overview]
Message-ID: <4nfzb49ddx.fsf@b2-25-3.bwh.harvard.edu> (raw)
In-Reply-To: <m2smf4tal5.fsf@c-ec5372d5.036-4-67626721.cust.bredbandsbolaget.se> (Jonas Steverud's message of "Fri, 16 Apr 2004 13:40:22 +0200")
On Fri, 16 Apr 2004, tvrud@bredband.net wrote:
> I probably have missed something; but I've just started to use
> spam.el according to previous emails and found a problem. How do I
> tell spam.el to register all my non-spam messages in my non-spam
> groups as ham?
Batch training is something I will add to spam.el eventually, but
right now is not available.
It should be pretty easy to do, though.
> I added (spam-contents gnus-group-spam-classification-ham) to the
> top email topic and I have (: spam-split) in the beginning of the
> fancy-split-rules (is this a Bad Idea?).
Not necessarily, but it will override all other rules. I specify
specific spam checks, the more permissive ones early and the more
restrictive ones later.
Note that it's OK to have all your groups be unclassified.
> Currently, all mail I receive is considered spam, which is not very
> nice. ;-)
I'm not sure why that is, is your mail group a spam group?
> BTW, is it already possible or WIBNI one could set
> ham-process-destination to 'respool or something like that and have
> the email respooled instead of moving it to the main mail box?
It's already possible, with that exact syntax. It should work.
If you're curious for more, you can do `G c' on a group or topic and
explore all the spam-related options.
Ted
next prev parent reply other threads:[~2004-04-16 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 11:40 Jonas Steverud
2004-04-16 13:06 ` Jonas Steverud
2004-04-16 15:00 ` Ted Zlatanov [this message]
2004-04-16 15:13 ` Jonas Steverud
2004-04-16 18:58 ` 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=4nfzb49ddx.fsf@b2-25-3.bwh.harvard.edu \
--to=tzz@lifelogs.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).