environmental issues

David Relson relson at osagesoftware.com
Sun Aug 3 19:48:20 CEST 2003


Greetings,

This weekend I've had an interesting time diagnosing bogofilter problems in 
new and different (to me) environments.  I've had to look at Solaris 2.5, 
RedHat 9 with BerkeleyDB 4.0.14, and Debian GNU with flex 2.5.31.  For 
those of you interested in the issues I encountered, my notes are below.

At this point, I'm looking for guidance in where to document the findings 
so that people don't have to spend time defining and correcting the 
problem.  One idea is to add to the FAQ.  Another idea is to create 
additional doc/programmer/README.xxx files, for example README.solaris-2.5, 
README.BerkeleyDB-4.0.14, and README.flex-2.5.31.

Question:  where should I document the issues?

Question:  Are there other issues that need to be documented?

Thanks.

David

*** Here's what I've learned this weekend ***

Flex 2.5.31

	The generated parsing code compiles with multiple "no previous
	prototype for ..." warnings, which is not a problem.
	However, it seems that pattern "<INITIAL>^[ \b\t]*\n" is
	evaluated at a different point in time, which results in
	bogofilter treating the first line of the message body as part of
	the message's header.

RH9 and BerkeleyDB 4.0.14

	When building from source, bogofilter uses the 4.1.x call to
	db->open().  When db->open() is called, it returns error 22
	(Invalid argument).  Installing the db4-4.1.25-0.rh73.3.1 rpm
	cures the problem.

Solaris 2.5

	lines longer than 4096 chars get split (under uncertain
	circumstances) and only the end part gets processed





More information about the Bogofilter mailing list