'Database handles remain at environment close' with new bogofilter

[Matthias Andree]

Kris Kennaway <kris at obsecurity.org> writes:

> I'm frequently get the following response when dispatching mail to
> bogofilter from my procmail script:
>
> --
> # filter mail through bogofilter, tagging it as spam and
> # updating the word lists
>
> :0fw
> | /usr/local/bin/bogofilter -u -e -p
>
> # if bogofilter failed, return the mail to the queue, the MTA will
> # retry to deliver it later
> # 75 is the value for EX_TEMPFAIL in /usr/include/sysexits.h
>
> :0e
> { EXITCODE=75 HOST }
> ---

The .procmailrc fragment is fine -- although personally, I'm not a
friend of -u as this hasn't been researched into. Others are.

> The error is:
>
> --
> Database handles remain at environment close
> Open database handle: wordlist.db
> DB_ENV->close(0x8077800): Invalid argument
> --

Are there further messages before the "Database handles..." line?
I think you'd had shown them but I'm asking nonetheless.

Does bogoutil --db-remove-environment=$HOME/.bogofilter/ fix the problem?

Are you using FreeBSD 6-CURRENT or a production version such as 5.4 or 4.11?

Can you show the output of "bogofilter -QQ"?

I cannot reproduce this on 4.11-RELEASE-p9 i386 with Exim 4.51, db
4.3.28 and procmail 3.22. Information that allows me to reproduce this
is needed.

> I'm using the latest version of the freebsd port (i.e. 0.94.12 with
> db43 backend) and the problems started after I converted the database
> to the new format per the instructions.

Do your recall the steps you took to "convert to the new format"?

Were there intermediate error messages?

At any rate, please see if you can get additional output for instance by
adding "-vvxd 2>/some/path/bogofilter.log".

Putting a breakpoint on exit or _exit and getting a backtrace when
bogofilter exits may also be useful to find out which path bogofilter
has taken out and how the error came to pass.

-- 
Matthias Andree