> Mark wrote: > > > Gary, > > >> I though the rules provided with sa-update were additions > to existing > >> rules, but I guess I have not paid much attention. Is it true then > >> that the rules downloaded through sa-update are a complete > rule set > >> in themselves? If so, ... > >> does direct SpamAssassin to use the sa-update rules there. It no > >> longer will use rules in the DEF_RULES_DIR. If sa-update (with no > >> --updatedir > >> override) has never been run, the rules in the DEF_RULES_DIR are > >> loaded. If 'sa-update --updatedir /usr/share/spamassassin' > (this is > >> where Debian puts the default rules) has been run, it appears the > >> default rules are loaded, then the newer rules in the > >> updates_spamassassin_org subdirectory located there are > loaded also (on top of them?). > > > I'm not sure, better join the topic on the SA list, or experiment. > > Seems to be that adding LOCAL_STATE_DIR => '/var/lib' is a > way to go. > > > Mark > > There is this: > > NOTE: Once the /var/lib/spamassassin/<spamassassin version> > directory exists, spamassassin expects to find all rules > underneath that directory, so make sure that the first time > you run sa-update it completes successfully <...> > > >From the SA thread: > > >> OK Now I am really confused. Do I assume that > SpamAssassin looks in > >> /var/lib/spamassassin/<version>/ for rules definitions and not > >> /usr/share/spamassassin? > > and Theo says: > > > Right -- if the update directory exists, SA will use that > instead of > > the default rules directory. > > I'm using 3.1.3 from Debian. After setting LOCAL_STATE_DIR in > amavisd the rules in /var/lib/spamassassin are used as noted > before. I downgraded to 3.0.3 and it used the standard rules > in /usr/share/spamassassin so at least on the surface it > appears the code change of LOCAL_STATE_DIR => '/var/lib' will > not affect older versions of SpamAssassin. I'm going to try > it on my production box. > > Gary V
There might be different behaviors depending upon whether --updatedir was used with sa-update, and where you perl installation is. In my case, perl is in /usr/local, SpamAssassin default rules are in /usr/local/spamassassin, there is no /var/lib/spamassassin, and the command: sa-update --updatedir /usr/local/share/spamassassin creates a non-versioned directory /usr/local/share/spamassassin/updates_spamassassin_org, which contains all the updated files. These are incorporated by inclusion via /usr/local/share/spamassassin/updates_spamassassin_org.cf. The rules in the updatedir override existing default rules. Debug shows first default rule files loading, and then updated rules. I've tested and have verified this by creating a duplicate rule with a changed score in the default rules and verifying that the scores match the algorithm indicated above. MrC ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
