bogofilter-0.93.1 - New Current Release

David Relson relson at osagesoftware.com
Thu Nov 11 05:28:57 CET 2004 

Greetings,

The 0.93.1 release of bogofilter brings with it a variety of bug fixes,
usability enhancements, and documentation updates mostly pertaining to
bogofilter's use of Berkeley DB's Transaction capability.  

Be sure to read file RELEASE.NOTES, available on SourceForge:
http://sourceforge.net/project/showfiles.php?group_id=62265

Here's the summary of the two major changes that comprised the heart of
the previous release - bogofilter-0.93.0:

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
your MUA. 

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
download.

Here are the md5sums for the release:

873a89748a4b8256e2305a41c629cdef  bogofilter-0.93.1-1.i586.rpm
1223c084eda94fc3f1221bd2cb980bd9  bogofilter-0.93.1-1.src.rpm
111fec77de9a616a786cb17e3f6a6b56  bogofilter-0.93.1-3.i586.rpm
8f958258aa33c29f7b3968157be7e398  bogofilter-0.93.1-3.src.rpm
b193e76758c294922d960ead057b0904  bogofilter-0.93.1.tar.bz2
3dcb7ede9de2801604e41103f08113c9  bogofilter-0.93.1.tar.gz
095820c0b5bf03bf3fee46c3e087b92a  bogofilter-static-0.93.1-1.i586.rpm
786beae6aa0428eefe0dce41319643b6  bogofilter-static-0.93.1-3.i586.rpm

			       =================
				BOGOFILTER NEWS
			       =================

NOTE: More information on important changes for bogofilter updaters
is in the RELEASE.NOTES files.  Read them!!

RELEASE.NOTES has two important sections entitled:

        INCOMPATIBLE CHANGES IN BOGOFILTER 0.93
and     MAJOR CHANGES IN BOGOFILTER 0.93

Briefly:

	** 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 !!!!!!!!

0.93.1	2004-11-11

	* The README.db file now has information on the DB_CONFIG file that
	  can be created and used to configure the Berkeley DB module.

	* Bogofilter's config file now supports setting max lock and
	  object counts for Berkeley DB using options
	      db_lk_max_locks=N
	      db_lk_max_objects=N

	* Bogofilter and bogoutil now allow these options on the
          command line, as:
	      --db_lk_max_locks=N
	      --db_lk_max_objects=N

	* When running database recovery automatically, don't let go of the
	  lockfile, so we can do our actual work subsequently.

	2004-11-10

	* Support for BerkeleyDB 4.3 was added. We'll avoid DB_NOSYNC on
	  DB->close() when DB_LOG_INMEMORY is configured for now.

	* Update manual pages/example outputs and filter recipe examples from
	  "X-Bogosity: yes" to "X-Bogosity: Spam". Fixes Debian bug #280557.
	
	* Bugfix for BerkeleyDB 4.2 support: check the data base flags, not the
	  environment flags, for DB_TXN_NOT_DURABLE, when determining whether
	  DB_NOSYNC is safe on DB->close(). May fix some kinds of database
	  corruption encountered with DB_TXN_NOT_DURABLE.

	* Return DB_VERSION_STRING contents in -V (version) output when
	  compiled against Berkeley DB. Minor change to the output format.

	* Bogofilter's config file  now supports setting max lock and
	  object counts for Berkeley DB using options
	
	      db_lk_max_locks=N
	      db_lk_max_objects=N

	* Bogofilter and bogoutil now allow these options on the
          command line, as:

	      --db_lk_max_locks=N
	      --db_lk_max_objects=N

	2004-11-09

	* Unify and clean up the horrible RELEASE.NOTES-*, CHANGES* and NEWS-*
	  mess with lots of duplicated info.
	  There shall only be one RELEASE.NOTES file and one NEWS file.
	  RELEASE.NOTES shall contain important information for updates.
	  NEWS shall contain noteworthy code changes in technical detail.

	  This also removes the confusion that RELEASE.NOTES didn't contain
	  information relevant for 0.93.X.

	2004-11-08

	* Berkeley DB mode: do not create data base in read mode (properly map
	  open_mode to DB_RDONLY flag, store open_mode).

	* Berkeley DB mode: exit with error code if lock file cannot be
	  created. Attempt recovery even if creation of lock file succeeded.

	2004-11-07

	* Fixed negative buffer index in mime.c

0.93.0	2004-11-06 "Broken compatibility" release

	* Fix bogotune's '-D' option.

	2004-11-02

	* Use only reentrant functions in the signal handler that runs
	  periodically to check for crashed processes.
	  Reported by Pavel Kankovsky.

	2004-11-01

	* Add a debugged and enhanced version of Stefan Bellon's QDBM
	  Hash->B+tree converter.

	* Broke QDBM compatibility with 2004-10-30 change, check unsigned
	  characters to match Berkeley DB behavior of bogoutil -d.

	2004-10-31

	* 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.

	* 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.

	* 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
	  4.2.

	2004-10-30

	* Converted QDBM from hash files (DEPOT API) to B+ trees
          (Villa API) for better speed (Stefan Bellon).

	2004-10-29

	* Attempting recovery with TDB or QDBM data bases results in an error,
	  so the user does not think it succeeded.

	* Document that recovery only works for Berkeley DB, but not TDB or
	  QDBM.

	2004-10-28

	* Merged Transactional branch (for BerkeleyDB) back into the trunk.

	2004-10-25

	* 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
	    to "Spam/Ham/Unsure"

0.92.8	2004-10-25 - previous stable release
_______________________________________________
Bogofilter-announce mailing list
Bogofilter-announce at bogofilter.org
http://www.bogofilter.org/mailman/listinfo/bogofilter-announce

More information about the bogofilter-dev mailing list