From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Spam.el: Train in ham?
Date: Fri, 16 Apr 2004 14:58:06 -0400 [thread overview]
Message-ID: <4npta77nsx.fsf@b2-25-3.bwh.harvard.edu> (raw)
In-Reply-To: <m2vfk0ot15.fsf@c-ec5372d5.036-4-67626721.cust.bredbandsbolaget.se> (Jonas Steverud's message of "Fri, 16 Apr 2004 17:13:10 +0200")
On Fri, 16 Apr 2004, tvrud@bredband.net wrote:
> Expiable and ancient articles is not sent through training and since
> there isn't any "take this article (which is in a unclassified or
> ham group) and train it as ham" AFAICT I was a bit confused.
Right now, spam.el aims to be proactive, doing the right thing at the
right time. What you describe is reactive behavior (reacting to a
command), which is not a bad thing, just inconsistent with how spam.el
operates otherwise.
I'll think about how to reconcile these two operating modes.
> Ooh. Nice. I asked since I couldn't find anything about it in the
> docs.
Yeah, 'respool and a bunch of other things need to be updated in the
docs, plus there are other problems as you observed.
Ted
prev parent reply other threads:[~2004-04-16 18:58 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
2004-04-16 15:13 ` Jonas Steverud
2004-04-16 18:58 ` 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=4npta77nsx.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).