bogofilter-0.93.0 - Significant Changes
relson at osagesoftware.com
Sat Nov 6 22:51:18 EST 2004
The 0.93.0 release of bogofilter brings with it some significant
changes. Be sure to read file RELEASE.NOTES-0.93!!!
Here's a summary of the two major changes:
1) Bogofilter now defaults to tri-state configuration using cutoff
values of 0.45 and 0.99 (for ham_cutoff and spam_cutoff, respectively).
The ham_cutoff value is new and spam_cutoff is unchanged. With these
cutoffs, messages with scores between 0.45 and 0.99 are unsures.
In tri-state mode messages are scored as "Spam", "Ham", or "Unsure"
rather than just "Yes" or "No". This affects the "X-Bogosity:" line and
you may need to change scripts in procmail, maildrop, etc and filters in
2) Bogofilter now uses BerkeleyDB's transactional capability to ensure
database integrity. Berkeley DB uses additional files in the wordlist
directory to keep state and logging information. See file doc/README.db
for important info.
Files are available at http://sourceforge.net/projects/bogofilter for
Here are the md5sums for the release:
Caution: If upgrading from an old version and skipping several
intervening versions of bogofilter, be smart and verify that the new
version is working for you before putting it into production.
Bogofilter's developers recommend that you run a few manual command
line tests. Use options, config files, and wordlists from your
production environment. This will help ensure that the new version of
bogofilter is working properly.
0.93.0 2004-11-06 "Broken compatibility" release
RELEASE.NOTES-0.93 has two important sections entitled:
MAJOR CHANGES IN BOGOFILTER 0.93
and INCOMPATIBLE CHANGES IN BOGOFILTER 0.93
** Bogofilter is now using Berkeley DB's Transaction capability to
ensure database integrity.
** Bogofilter is now generating tri-state results labeled Spam, Ham,
and Unsure, compared to the old two-state Yes/No results.
!!!!!!!! READ THE RELEASE.NOTES !!!!!!!!
* Added GETTING.STARTED document.
* Changed default mode from two-state to three-state
- with ham_cutoff=0.45 and spam_cutoff=0.99
The ham_cutoff value is new and spam_cutoff is unchanged.
- changed the "Yes/No" tags used in the "X-Bogosity:" line
* See RELEASE.NOTES-0.93 for more details. If you have
scripts that depend on "Yes" and "No", this change will
break them. You will need to change your config file to
enable the two-state options or else update your scripts.
* Merged Transactional branch (for BerkeleyDB) back into the trunk.
* Inserted new section 2.2 into doc/README.db to mention that it is
recommended to dump/load the data base when using BerkeleyDB 4.1 and
* Rearranged flag setting for Berkeley DB data store, so as only to set
DB_CHKSUM[_SHA1] when creating the data base.
Fixes "checksum error: catastrophic recovery required" and
consequential "wordlist.db: page 1: reference count overflow" errors
Reported by Torsten Veller.
* Use only reentrant functions in the signal handler that runs
periodically to check for crashed processes.
Reported by Pavel Kankovsky.
* Document that recovery only works for Berkeley DB, but not TDB or
QDBM. When attempting recovery with TDB or QDBM, generate an error,
so the user does not think it succeeded.
* Add a debugged and enhanced version of Stefan Bellon's QDBM
* Broke QDBM compatibility with 2004-10-30 change, check unsigned
characters to match Berkeley DB behavior of bogoutil -d.
* Revised RELEASE.NOTES-0.93 to move QDBM change into "Incompatible
Changes" section and to mention BerkeleyDB dump/load for 4.1 and 4.2
to add checksums.
* Converted QDBM from hash files (DEPOT API) to B+ trees
(Villa API) for better speed (Stefan Bellon).
* Fix bogotune's '-D' option.
0.92.8 2004-10-19 - previous stable release
More information about the Bogofilter-announce