> 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.
The Mail::SpamAssassin module doc in 3.1.4 doesn't list local_state_dir as an option for Mail::SpamAssassin->new. Should it? Is that how an app is supposed to pass this information? Bret
