Gnus development mailing list
 help / color / mirror / Atom feed
From: Christopher Splinter <chris@splinter.inka.de>
Subject: Re: `S t' always returns nil
Date: Tue, 28 Jan 2003 16:13:36 +0100	[thread overview]
Message-ID: <871y2xnw7z.fsf@splinter.inka.de> (raw)
In-Reply-To: <4n7kcqtkia.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Mon, 27 Jan 2003 15:17:49 -0500")

Ted Zlatanov <tzz@lifelogs.com> writes:

> I want spam.el to remain binary (spam vs. ham).  Introducing a third
> category would complicate things enormously.  ifile is the only
> multi-way classifier in a limited way, and I'm not sure that's too
> useful.  We should have three ways of dealing with 'Unsure' messages:
>
> - treat them as ham (the case now)
>
> - let the user decide if they are to be ham or spam (why would the
>   user ever want unsure messages as spam, though?)
>
> - use the spamicity score for 'Unsure' messages, cutoff decided by the
>   user
>
> I think the third option is best, what do you think?

As bogofilter allows the user to use RF (Robinson-Fisher) as a
binary filter too, that's somewhat redundant. Another reason why
this wouldn't be too useful is the RF algorithm itself, which
yields extreme results for messages which are easy to classify,
but rather undifferentiated ones for 'unsure' messages.

If it's arduous to support non-binary algorithms properly, I
wouldn't support them at all and go for the first option.



  reply	other threads:[~2003-01-28 15:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-26 15:35 Christopher Splinter
2003-01-27 17:50 ` Ted Zlatanov
2003-01-27 19:01   ` Christopher Splinter
2003-01-27 20:17     ` Ted Zlatanov
2003-01-28 15:13       ` Christopher Splinter [this message]
2003-01-28 16:46         ` Ted Zlatanov

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=871y2xnw7z.fsf@splinter.inka.de \
    --to=chris@splinter.inka.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).