Matt Kettler wrote:
Note: for this to work 10_default_prefs.cf MUST NOT be in your
/etc/mail/spamassassin. It belongs in /usr/share/spamassassin, as do ALL
the rulefiles that come with SA.
Or in /var/lib/spamassassin/... after running sa-update
I have been trying to do a good deal of reading on the newer 3.2.x branch
etc.
10_default_prefs.cf
I came across this file in the docs and I am wondering how important it is
to the big picture on some of our ISP type installs
U I guess I spaced and just didn't see it if it was in the 3.1.x
Robert - eLists wrote:
10_default_prefs.cf
I came across this file in the docs and I am wondering how important it is
to the big picture on some of our ISP type installs
U I guess I spaced and just didn't see it if it was in the 3.1.x
branch...
I am investigating yet, it *appears* to
Robert - eLists wrote:
I have been trying to do a good deal of reading on the newer 3.2.x branch
etc.
10_default_prefs.cf
I came across this file in the docs and I am wondering how important it is
to the big picture on some of our ISP type installs
U I guess I spaced and just didn't
Other way around. These are the defaults, and anything you put in
local.cf will override the corresponding setting in this file.
SA processes all the files in the general SA directory --
/usr/(local)/share/spamassassin, or
/var/lib/spamassassin/path/to/updated/rules -- then processes
No, it doesn't... Your local.cf gets parsed *AFTER* this file, so your
local.cf overides 10_default_prefs.cf.
Note: for this to work 10_default_prefs.cf MUST NOT be in your
/etc/mail/spamassassin. It belongs in /usr/share/spamassassin, as do ALL
the rulefiles that come with SA. Only your
