From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: spam.el's bogofilter support and bogofilter 0.11.1
Date: Thu, 06 Mar 2003 10:47:59 -0500 [thread overview]
Message-ID: <4nfzq05weo.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <86y93tqo61.fsf@ieee.org> (Jorge Godoy's message of "Wed, 05 Mar 2003 22:28:06 -0300")
On Wed, 05 Mar 2003, godoy@metalab.unc.edu wrote:
> Is spam.el aware of the modification done to '-S' and '-N' options
> on bogofilter 0.11.1?
> IIRC, this is the inverse of what used to be.
As of now, -S/-N are not used, since spam.el does not yet do
reclassification. Only -s/-n are used. Those haven't changed, right?
I added spam-bogofilter-spam-switch and spam-bogofilter-ham-switch as
custom variables ("-s"/"-n" by default), so you can set those if you
pre-process all your mail with bogofilter.
> Also, the algorithm used per default has changed to
> Robinson-Fisher...
I don't think this matters to spam.el, but it's good to know...
Thanks
Ted
next prev parent reply other threads:[~2003-03-06 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 1:28 Jorge Godoy
2003-03-06 15:47 ` Ted Zlatanov [this message]
2003-03-06 18:23 ` Jorge Godoy
2003-03-07 2:42 ` Stephen Zander
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=4nfzq05weo.fsf@lockgroove.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).