bogoupgrade.sh [was: problems upon upgrade]

[David Relson]

On Wed, 28 Jul 2004 18:37:28 -0800
jerry wrote:

> On Wednesday 28 July 2004 06:21 pm, you wrote:
> 
> >
> > Sorry.  I should have specified the name of the database rather than
> > the directory.  Use:
> >
> > bogoutil -d ~/.bogofilter/wordlist.db | tee wordlist.txt | wc -l
> 
> bogoutil -d ~/.bogofilter/wordlist.db | tee wordlist.txt | wc -l
> 1056850

Indicates your wordlist has 1,056,850 tokens in it.  Since bogoutil
doesn't have any trouble reading it, the file is fine (not corrupt or
broken).

> > How were you checking for spam/ham?
> 
> Prior to the failed upgrade 0.14.5 was working excellent.

Are you using procmail or maildrop or something else?  Were you using
"bogofilter -p -e" and checking for "X-Bogosity: Yes" or were you
checking bogofilter's return codes?

> > To make the error messages go away, remove (or comment out) the
> > lines in bogofilter.cf.  Alternatively, use bogofilter's "-C" option
> > to run without config file.
> 
> would that be /etc/bogofilter.cf or my ~/.bogofilter.cf
> I tried commenting out the relevent error lines in both .cf files,
> with the result that all emails were/are being deleted

Bogofilter will use ~/.bogofilter.cf if it's available then will try
/etc/bogofilter.cf.  The "-C" option stops bogofilter from using either.

> > Take some messages, run them through bogofilter, and look at the
> > scores, see if they're reasonable, i.e.
> >
> > bogofilter -v -d ~/.bogofilter < ham.1
> > bogofilter -v -d ~/.bogofilter < ham.2
> > ....
> > bogofilter -v -d ~/.bogofilter < spam.1
> > bogofilter -v -d ~/.bogofilter < spam.2
> > ....
> Ok, I'll have to wait for more spam to give this a try
> thanks

You could try something like:

echo This is viagra grow bigger | bogofilter -C -H -vvv

which may well be spammish.

Also, you can tell bogofilter to print some debug messages by using
flags "-x d -v"


bogofilter -