TRUSTED_RULESETS="TRIPWIRE SARE_ADULT SARE_OBFU0 SARE_OBFU1 SARE_URI0 SARE_URI1 SARE_STOCKS" SA_DIR="/etc/mail/spamassassin" MAIL_ADDRESS="<your e-mail address>" SA_RESTART="/scripts/restartsrv_spamd"
#!/bin/sh /usr/bin/sa-update /usr/bin/sa-update --nogpg --channel saupdates.openprotect.com
chirpy,It doesn't show output if it works. You can find the rule sets it downloads and spamassassin uses in /var/lib/spamassassin/ - what I gave you above provides you with the very latest rules from spamassassin themselves (the first sa-update) and the second one provides the latest recommended rules from SARE.
Ok, I see this now. I just ran the update on one of our less used servers and it does read from that folder ... interestingv3 of SpamAssassin automatically looks in /var/lib/spamassassin/ for rules. It's v3 that provides the sa-update procedure itself. It's nothing to do with cPanel
You can see this if you run sa-update and then do a:
spamassassin --lint -D
At the start of the output you should see it importing the downloaded rules from /var/lib/spamassassin/
thx's Chirpy for the info, very helpful.There's no need for RulesDuJour if you're using sa-update, especially as I've suggested above.
/usr/share/spamassassin/ is the local for the default installation of SA
/etc/mail/spamassassin/ is where you should put yur own local SA configuration settings for server-wide rules - if you currently have SARE rulesets in here you should remove them
/var/lib/spamassassin/ is used for dynamically updated rules from sa-update which contains both updates to the default SA rules plus the recommended selection of SARE rules
I'd leave the /usr/share/spamassassin/ directory alone. The newer rules will override them anyway.I did notice now, when you run the sa-update, you end up with alot of duplicate files in the /var/lib/spamassassin and /usr/share/spamassassin folders. Is this OK or should they be removed from one of the folders?