Gnus development mailing list
 help / color / mirror / Atom feed
From: Christopher Splinter <chris@splinter.inka.de>
Subject: Re: (: spam-split) doesn't work
Date: Thu, 27 Feb 2003 21:06:33 +0100	[thread overview]
Message-ID: <87n0khcwty.fsf@splinter.inka.de> (raw)
In-Reply-To: <4nwujlim0o.fsf@chubby.bwh.harvard.edu> (Ted Zlatanov's message of "Thu, 27 Feb 2003 14:03:35 -0500")

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Thu, 27 Feb 2003, chris@splinter.inka.de wrote:
>> Note that the spamicity value differs from what `S t' returns --
>> which is a value of 1.0. Moreover, the *Article* buffer of the
>> respective article is deprived of its body after hitting `B r'
>> (which is what I did to get the backtrace) and the score of the
>> header alone (= 0.8477387640) is quite similar to the one below.
>> 
>> Debugger entered: ("Unsure, tests=bogofilter,
>>   spamicity=0.8469313635, version=0.10.3.1.cvs.20030227")
>
> (background for ding readers: Chris was having issues with bogofilter
> classification in spam.el)
>
> There's the problem, I think.   "Unsure" is not a recognized spam flag.

I'm not sure about that. After all, the above value is not what
bogofilter returns when the message, for which bogofilter returns
that value when called via `B t' or `B r', is piped to bogofilter
manually -- in that case, this is returned:

X-Bogosity: Spam, tests=bogofilter, spamicity=1.0000000000, version=0.10.3.1.cvs.20030227

Therefore I suspect that bogofilter isn't fed the complete message.




  reply	other threads:[~2003-02-27 20:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87vfzyjx2v.fsf@splinter.inka.de>
     [not found] ` <4nisvxs1j6.fsf@lockgroove.bwh.harvard.edu>
     [not found]   ` <874r7g2f4w.fsf@splinter.inka.de>
     [not found]     ` <4nheb8qazq.fsf@lockgroove.bwh.harvard.edu>
     [not found]       ` <87vfznc21y.fsf@splinter.inka.de>
     [not found]         ` <4nk7g3gdbk.fsf@lockgroove.bwh.harvard.edu>
     [not found]           ` <87vfzm7p2f.fsf@splinter.inka.de>
     [not found]             ` <4nlm0iad77.fsf@lockgroove.bwh.harvard.edu>
     [not found]               ` <877kc26j07.fsf@splinter.inka.de>
     [not found]                 ` <m3of5dc4tt.fsf@heechee.beld.net>
     [not found]                   ` <87el5talpw.fsf@splinter.inka.de>
     [not found]                     ` <4nfzq9k84r.fsf@chubby.bwh.harvard.edu>
     [not found]                       ` <87wujl8tj8.fsf@splinter.inka.de>
2003-02-27 19:03                         ` Ted Zlatanov
2003-02-27 20:06                           ` Christopher Splinter [this message]
2003-02-27 20:56                             ` Ted Zlatanov
2003-02-27 22:05                               ` Christopher Splinter
2003-02-27 22:29                                 ` Ted Zlatanov
2003-02-27 23:45                                   ` Christopher Splinter
2003-02-28 16:43                                     ` Ted Zlatanov
2003-02-28 16:55                                       ` Simon Josefsson
2003-02-28 17:07                                         ` Ted Zlatanov
2003-02-28 17:34                                           ` Simon Josefsson
2003-02-28 21:22                                             ` Ted Zlatanov
2003-02-28 22:17                                               ` Christopher Splinter
2003-03-01 15:01                                                 ` 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=87n0khcwty.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).