Re: (: spam-split) doesn't work

[Christopher Splinter <chris@splinter.inka.de>]

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Thu, 27 Feb 2003, chris@splinter.inka.de wrote:
>> 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")
>> 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.
>
[Problems might be related to narrowing issues]
> Try replacing spam-bogofilter-path (which is normally the path to
> bogofilter) with the path to something like this (save this script
> anywhere and make it executable):

[...]

> Then look at the /tmp/bogofilter.input file and see if it matches the
> message we're trying to classify.

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