From: "Raymond Wan" <[EMAIL PROTECTED]>
Hi Bowie,
On Tue, 22 Aug 2006, Bowie Bailey wrote:
Raymond Wan wrote:
1) /etc/spamassassin/*.pre
2a) /var/lib/spamassassin/3.001003/updates_spamassassin_org/*.cf
(if the directory exists)
2b) /usr/share/spamassassin/*.cf
(if the previous directory doesn't exist)
3) /etc/spamassassin/*.cf
4) ~/.spamassassin/user_prefs
Note that only one of 2a and 2b will be read, never both. If you have
run sa-update and created the updates directory, it will be used.
Otherwise, the original rules directory will be used.
Ah, thank you for that! I actually modified the CONTACTADDRESS in
/usr/share/spamassassin/10... and the change didn't take into effect. I
didn't know why and just presumed I got the syntax wrong. I didn't
realize there was another set of files elsewhere and that my change in
/usr/share/spamassasin were pointless.
Never change /etc/share/spamassassin or the /var/lib/spamassassin
directories. Always change /etc/spamassassin/ or /etc/mail/spamassassin
as appropriate for your install. You can override values set earlier
with new ones. That change should probably be made in local.cf or
maybe better a new "99_local.cf" of your own.
The user_prefs file is always read for configuration changes.
allow_user_rules simply allows the users to create custom rules as
well as making simple changes. The main reasons to leave user rules
off is that they slow down the system and give the possibility of
users writing bad rules.
I see. So it really is an efficiency issue and not so much a
security issue. I forgot to mention that I'm running a single-user Debian
system (one user account, one root). But good to know if I ever manage a
system with more user accounts.
Everything possible should be in local.cf (or another cf file in that
directory). The only thing that should be in user_prefs are settings
that only apply to that one user.
Ok...centralized at the local.cf file. Also, since it is loaded
last (but before the user_prefs file), it can undo some of the things that
the previous .cf files did...such as setting the contact address.
Well, there was a bit of a mis-statement there. All system wide
configuration rule type settings should be in files named with a
".cf" on the end such as the example I gave above, "99_local.cf",
and located in the same directory as "local.cf". The rules in that
directory, usually /etc/spamassassin or /etc/mail/spamassassin, are
read in alphabetical order. So a "50_local.cf" might contain a
value that is overridden in "65_local.cf" or "MyRules.cf". SA rule
sets and SARE rule sets use the two digit and underscore prefix
convention to assure the read order for rules and scores.
{^_^}
