From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: planned spam.el features
Date: Mon, 24 Feb 2003 10:42:50 -0500 [thread overview]
Message-ID: <4n8yw5wupx.fsf@chubby.bwh.harvard.edu> (raw)
In-Reply-To: <8765rc94vb.fsf@fire-swamp.org> (Stephen Zander's message of "Fri, 21 Feb 2003 23:00:40 -0800")
On Fri, 21 Feb 2003, gibreel@pobox.com wrote:
> Since writing my original mail, I've upgraded to Oort 0.15, and I
> have to say that spam.el officially rocks!!!
That's good, I hope you keep enjoying it. I would welcome any
suggestions for improvements of the documentation or functionality.
> The only thing I need now is the ability to use '-S' & '-N' instead
> of '-s' & '-n' so that any spam/ham messages are reclassified rather
> than added to the pool. Any likelihood of you adding that, rather
> than my doing so?
Well, I can make it a customizable option, but with the next major
iteration of spam.el there will be real reclassification. What this
means is, after a message has been processed with a spam processor,
you could "undo" that processing through reclassification.
Is there a way to specify "-s if message is not registered, -S
otherwise"? Or are the -S and -N flags OK always? I'm worried that
-S on an unregistered message might cause a skew in the statistics,
and I don't know if bogofilter allows for that. If that can't be
done, I'll make the -s/-n flags customizable until the
reclassification abilities are in place.
Ted
prev parent reply other threads:[~2003-02-24 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 19:22 Ted Zlatanov
2003-01-24 20:01 ` Kai Großjohann
2003-01-24 20:25 ` Ted Zlatanov
2003-01-25 20:54 ` Stephen Zander
2003-01-27 18:20 ` Ted Zlatanov
2003-02-22 7:00 ` Stephen Zander
2003-02-24 15:42 ` 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=4n8yw5wupx.fsf@chubby.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).