On Thu, Aug 03, 2006 at 03:28:05PM +0200, Mark Martinec wrote: > Well, this is not entirely true. It is not the SpamAssassin modules > that sets a default value for LOCAL_STATE_DIR => '/var/lib' in the > SA object, but it is the application program that does it: the > spamassassin, sa-update and spamd.
True. > Which means that other application programs like amavisd-new > or other callers of SA modules won't see the rules updates > in /var/lib/spamassasin unless explicitly configured to do so ... You would want to make sure that the third party application you're running supports the version of SA you're using, yes. local_state_dir was an API change from 3.1.0, unfortunately, but it's been known about for several months now. > ... which is unfortunate, as it would probably not be difficult > to change Mail::SpamAssassin to provide a suitable default > for LOCAL_STATE_DIR. Please consider this a feature request. http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4952 :) > - tell sa-update to place updates in the usual rules directory > (which is probably the easiest way): > > # sa-update --updatedir /usr/local/share/spamassassin Warning: This will break your installation -- there are files in def_rules_dir that aren't in the updates, and sa-update will be happy to delete all of the files in the directory for you. local_state_dir and def_rules_dir are not interchangeable. -- Randomly Generated Tagline: "Security is mostly a superstition. It does not exist in nature, nor do the children of men as a whole experience it. Avoiding danger is no safer in the long run than outright exposure. Life is either a daring adventure, or nothing." - Helen Keller
pgpUPhz5mCEKE.pgp
Description: PGP signature
