Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Matthias Andree <matthias.andree@gmx.de>
Subject: Re: bogofilter behavior
Date: Mon, 09 Aug 2004 04:00:04 +0200	[thread overview]
Message-ID: <m3y8kpdqaj.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <4nd625cjag.fsf@lifelogs.com>

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Thu, 05 Aug 2004, matthias.andree@gmx.de wrote:
>
>> Ted, you would have to use bogofilter -V instead (capital letter 'V'
>> vee).
>
> OK.  I don't use Bogofilter so I'd appreciate your help.
>
> VERSION: spam ham spam-strong ham-strong
> 0.11.0: -s -n -S -N
>
> Can you continue the table?

Not at this time, the meaning of spam-strong and ham-strong is unclear
to me and doesn't stand out in the documentation.

-s/-n - REGISTER message as spam/ham (ham = non-spam)
-S/-N - UNREGISTER message as spam/ham (undo a registration, must use
        the same message)

These options can be combined, to fix up a false training, -Sn moves a
message from spam to ham and -Ns moves it from ham to spam.

>> I'd suggest refusing to work with bogofilter versions older than
>> 0.10.2 and it's recommended to warn about versions older than 0.17.5
>> which is now three months old. Remember that bogofilter 0.X versions
>> are still under development.
>
> It's hard to give the boot to the users like that.

The users chose to use a development version, with all the implications
such as a minor release becoming incompatible with the previous,
anything but the current version unsupported, frequent updates and the
like.

0.11.0, when the meaning of the registration options was changed for the
last time, was released in March 2003 - over 17 months ago, which is an
entire era for a software under development.

It's sensible to request frequent updates of users using a development
version. Don't waste your time on the 0.1 % of machines that run
outdated bogofilter versions - use the registration as mentioned above
and refuse work with versions before and excluding 0.11.0.

> Gnus is in Emacs, and that means we have to handle old software too
> occasionally.

It's not going to help anybody if someone uses some two-year-old version
of bogofilter today.

-- 
Matthias Andree

NOTE YOU WILL NOT RECEIVE MY MAIL IF YOU'RE USING SPF!
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 (PGP/MIME preferred)


  parent reply	other threads:[~2004-08-09  2:00 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 [this message]
     [not found]                 ` <4nvffs6vfs.fsf@lifelogs.com>
     [not found]                   ` <m3fz6v7u7l.fsf@merlin.emma.line.org>
2004-08-10 14:59                     ` Ted Zlatanov
     [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=m3y8kpdqaj.fsf@merlin.emma.line.org \
    --to=matthias.andree@gmx.de \
    /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).