At 08:03 AM 9/21/2005, Ronald I. Nutter wrote:
I have spam coming through that I havent been able to block with the
blacklist command. Tried putting it in a 90_blacklist.cf file. thought
it was working but things are still coming through. I am using a setup
with postfix/amavisd that calls the daemonized version of SA. Should
the blacklist command be put in a local.cf file instead of where I have
been trying it ? Next question is where should the local.cf file reside
- in /usr/share/spamassassin ?
In general, unless you REALLY know what you are doing, don't edit any of
the files that are in /usr/share/spamassassin.
Add your settings to /etc/mail/spamassassin/local.cf (or any other .cf
file you want in /etc/mail/spamassassin).
The reason for using /etc/mail instead of /usr/share is twofold:
1) when you upgrade, the installer does a rm -f /usr/share/spamassassin/*
and all your changes will be wiped out
2) if you screw up your configuration, you can easily move your local.cf
somewhere and get SA working again with it's default config while you
figure out the problem.
3) this is how the SA devs envisioned you doing it, which is why SA parses
/usr/share/ first, then parses /etc/mail/ and any duplicate settings are
clobbered by the latter.
Also remember, when you're done editing config files, run spamassassin
--lint to check for errors, and restart spamd (spamd only reads these
config files at startup to avoid wasting time)
