Note For First Time Users -------------------------- Per default spamprobe uses the directory ~/.spamprobe to store its database when no directory is specified with the -d option. IT DOES NOT AUTOMATICALLY CREATE DIRECTORIES when they don't exist. Either you create the directory where you want the database to reside with mkdir before invoking spamprobe or use spamprobe's -c command line flag. Upgrading Notes --------------- Since version 1.4d-12.1, this package uses Berkeley DB 5.3. Previous versions of this package used Berkeley DB version 5.1 or prior databases for storing state. This change results in spamprobe choking when trying to modify old databases (cf. Bug #440939). Section DATABASE MAINTENANCE in the spamprobe(1) manual page outlines a manual upgrade path. Spamprobe allows each user to use own spamprobe databases, making a fully automatic upgrade path infeasibly, again I apologize. To avoid this issue at next Berkeley DB migration, converting to another data file format, like 'hash', is recommended. See documentation of the -d option in spamprobe(1) man page. Configure Options Used ---------------------- When building the package, spamprobe was configured with these specific options: default-8bit - Use 8bit characters by default cdb - Concurrent Berkeley DB access gif - Processing of gif images png - Processing of png images jpeg - Processing of jpeg images Should you experience problems with the latter option, please file a bug report using a tool like reportbug. Manual Page ----------- Upstream's manual page spamprobe(1) is sort of reformating the README coming with the tarball, including marketing blurb, build and installation instructions, effectively making it annoying to use for reference. Debian provides a docbook-xml based version compiled from the original by Siggy Brentrup (previous maintainer of this Debian package). -- Ondřej Surý , Tue, 11 Feb 2014 15:38:55 +0100