From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: bogofilter behavior
Date: Tue, 10 Aug 2004 10:59:18 -0400 [thread overview]
Message-ID: <4nzn53nint.fsf@lifelogs.com> (raw)
In-Reply-To: <m3fz6v7u7l.fsf@merlin.emma.line.org>
On Tue, 10 Aug 2004, matthias.andree@gmx.de wrote:
> Looking at the NEWS file however I can only again discourage using
> bogofilter versions that old. Missing features, missing tuning, missing
> accuracy, and so on.
Can any other Bogofilter users comment please? If this is the
general sentiment I'll gladly go with Matthias.
> Whether you use 0.11.2 or 0.92.4, -n -N -s -S are the same. Versions
> before 0.11 used -S instead of -Ns and -N instead of -Sn.
My point is that the switches may change again. I'll assume they are
stable for now.
> I do believe your fear for bogus bug reports is unsubstantiated if
> the refusal is worded properly, something along the lines "Sorry,
> spam.el is not compatible with your older version of bogofilter but
> has been developed with a more recent bogofilter version in mind. If
> you plan to upgrade your bogofilter version; spam.el requires at
> least bogofilter version 0.11.2, it is advisable to get at least
> 0.15.13 though."
OK, I can put that in spam.el, I would just like one more vote for it
so I know people are using the bogofilter support :)
I'll make it conditional on whether spam-use-bogofilter is set when
spam.el is loaded.
Ted
next prev parent reply other threads:[~2004-08-10 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 10:06 Harry Putnam
[not found] ` <v9zn5cv3hd.fsf@marauder.physik.uni-ulm.de>
2004-08-03 16:19 ` Harry Putnam
[not found] ` <v9d628p0ei.fsf@marauder.physik.uni-ulm.de>
2004-08-03 21:39 ` Harry Putnam
[not found] ` <4nekmmaokh.fsf@lifelogs.com>
[not found] ` <m3oelqt4or.fsf@merlin.emma.line.org>
[not found] ` <4nd625cjag.fsf@lifelogs.com>
2004-08-09 2:00 ` Matthias Andree
[not found] ` <4nvffs6vfs.fsf@lifelogs.com>
[not found] ` <m3fz6v7u7l.fsf@merlin.emma.line.org>
2004-08-10 14:59 ` Ted Zlatanov [this message]
[not found] ` <656wo2y8.fsf@blue.sea.net>
[not found] ` <4nvfdzmync.fsf@lifelogs.com>
[not found] ` <v98yavbncv.fsf@marauder.physik.uni-ulm.de>
[not found] ` <4nfz5231ea.fsf@lifelogs.com>
[not found] ` <v9hdpijfgx.fsf@marauder.physik.uni-ulm.de>
[not found] ` <4nd605axsa.fsf@lifelogs.com>
[not found] ` <v9hdpgrb4l.fsf@marauder.physik.uni-ulm.de>
2004-09-30 15:15 ` Ted Zlatanov
2004-10-02 17:11 ` Harry Putnam
2004-10-03 15:45 ` Reiner Steib
[not found] ` <m31ximuk0r.fsf@merlin.emma.line.org>
[not found] ` <m34qnhlwhb.fsf@newsguy.com>
2004-08-05 16:45 ` Matthias Andree
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=4nzn53nint.fsf@lifelogs.com \
--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).