BUG? corrupted goodlist.db again, spamlist.db fine
David Relson
relson at osagesoftware.com
Mon Dec 30 05:56:33 CET 2002
At 11:38 PM 12/29/02, Matthias Andree wrote:
>Matthias Andree <matthias.andree at gmx.de> writes:
>
> > b0rken
>
>Guess what, I got another deferral in the last few hours, and it
>magically fixed itself, db_verify reports no issues.
>
>bogofilter: (db) db_getvalue( 'b32c97188d' ), err: -30988,
>DB_PAGE_NOTFOUND: Requested page not found
>
>Running sendmail -q delivered the mail.
>
>Strange, no? I have no other explanation than attempted read access
>while write access is taking place. bogofilter -u is in use
>here. (non-MIME version for system use still).
I'm running current sota (state of the art) bogofilter.
The "ignore TOKEN if not MIME_TEXT" is working great. Without it, the
tarballs inflated my goodlist from 36,277 words to 80,974 words. Reverting
to this morning's training set and processing the same message, I have
35,823 words in my goodlist. (The difference between 36,277 and 35,823
being some '-u' stuff).
By the way, my "Failed to acquire locks" problem appears to have been fixed
by changing the "delay after failure" code in datastore_db.c. It now
actually delays for "1 millisecond to 1 second" as the comment
states. Looking at my logs, every once in a while I see a "failed" message
and then, several seconds later, there's a "X-Bogosity ... register ..."
message. As best I know, since that fix, all my incoming email has
received an X-Bogosity status line.
More information about the bogofilter-dev
mailing list