John, > I'm confused on how Amavisd-new and Spamassassin sa-update interact. > There are several previous posts that didn't clear things by me. > Versions: SA 3.1.7, Amavisd-new 2.3.3
These versions are fine, sa-update should work out of the box, no special options or actions are needed, just let it create its stuff under /var/lib or wherever it chooses. After amavisd reload new directories with rules would be seed by SA running aunder amavisd. > Should I include the updated rules in /etc/spamassasin/local.cf as > mentioned in the SA website? > include /var/lib/spamassassin/3.001007/updates.spamassassin.org.pre > include /var/lib/spamassassin/3.001007/updates.spamassassin.org.cf No, SA should notice /var/lib/spamassassin by itself. > I also read on previous posts that there should be a "LOCAL_STATE_DIR" = > /var/lib specified in amavisd.conf but that's only necessary in SA <3.1.4. > I also read on previous posts that amavisd could be patched. Right, but your versions need no patches. Either SA 3.1.5 or later suffices regardless of version of amavisd, or amavisd-new-2.4.3 suffices, regardless of version of SA. Mark ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ 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/
