Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: (: spam-split) doesn't work
Date: Thu, 27 Feb 2003 17:29:45 -0500	[thread overview]
Message-ID: <4nlm01pdba.fsf@chubby.bwh.harvard.edu> (raw)
In-Reply-To: <87isv5crc0.fsf@splinter.inka.de> (Christopher Splinter's message of "Thu, 27 Feb 2003 23:05:19 +0100")

On Thu, 27 Feb 2003, chris@splinter.inka.de wrote:
> As I had assumed, /tmp/bogofilter.input only contains the header,
> whereas the message which is to be classified contains a
> non-empty body.
> 
>> You can see what bogofilter would have said about it, too, if
>> you do
>>
>> bogofilter -v /tmp/bogofilter.input
> 
> Well, almost :-) bogofilter only takes input from stdin.
> 
> X-Bogosity: Unsure, tests=bogofilter, spamicity=0.8524075477,
> version=0.10.3.1.cvs.20030227

I see.  Try setting nnimap-split-download-body to t.  Does that fix
it?  If yes, I'll make it the default setting if you enable
spam-use-bogofilter or any other statistical filter.  But it will slow
down IMAP mail retrieval, since the full message body will be
downloaded for analysis.  Does anyone object?

I remember us checking this, and we got the full message body, that's
why I didn't check this sooner.  Sorry!

Thanks
Ted



  reply	other threads:[~2003-02-27 22:29 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
2003-02-27 20:56                             ` Ted Zlatanov
2003-02-27 22:05                               ` Christopher Splinter
2003-02-27 22:29                                 ` Ted Zlatanov [this message]
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=4nlm01pdba.fsf@chubby.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).