bogofilter (-o) & bogoutil (-c) bugs?

[W M Brelsford]

David,

Thanks for the prompt reply.

> >1. bogofilter -o <value>  seems to have no effect.
> 
> '-o' sets the spam_cutoff value.  Messages with scores above spam_cutoff 
> are classified as spam.  In the test below, I've classified a message that 
> has a score of 0.509410, which is less than the default spam_cutoff of 
> 0.54.  The message was classified as "No" (not spam).  I then reran 
> bogofilter with "-o 0.500" to lower the spam_cutoff value and the messagee 
> is classifed as "Yes" (spam).  Here's the test:
> 
> [relson at osage 0103]$ bogofilter -C -v < msg.test
> X-Bogosity: No, tests=bogofilter, spamicity=0.509410, version=0.10.3
> 
> [relson at osage 0103]$ bogofilter -C -v -o 0.500 < msg.test
> X-Bogosity: Yes, tests=bogofilter, spamicity=0.509410, version=0.10.3

I was running the same test without the -C option, and -o had no
effect.  Do command-line arguments not override configuration file
settings?

> >3. bogoutil -c1  should remove tokens with 0 counts, but also
> >        removes counts of 1.  -c0 removes nothing.
> 
> The code is keeping tokens with counts above the specified value.  I'll 
> correct the documentation.

Then -c0 should remove the 0-count tokens.  But I get

	$ bogoutil -d spamlist.db | grep ' 0 '
	a-1 0 20030128
	a-2 0 20030121
	a-3 0 20030121

-- 
Bill Brelsford
k2di2 at att.net