Thanks for the quick response... see below:
On 11/22/2019 12:25 PM, Matus UHLAR - fantomas wrote:
On 22.11.19 12:14, Jerry Malcolm wrote:
I am trying to add bayes to SA. I see in the docs that there is a
use_bayes parm and the path parm. I made the changes to
/usr/share/spamassassin/local.cf.
the config files and rules are usually in /etc/spamassassin/
But I see no change. I am not sure it's even loading that config
file. I've got debug on, and the log doesn't tell me that it's
reading the local.cf file I'm changing.
try running spamassassin -D --lint and look for results:
Nov 22 19:20:24.735 [16921] dbg: logger: adding facilities: all
Nov 22 19:20:24.735 [16921] dbg: logger: logging level is DBG
Nov 22 19:20:24.735 [16921] dbg: generic: SpamAssassin version 3.4.2
Nov 22 19:20:24.735 [16921] dbg: generic: Perl 5.028001, PREFIX=/usr,
DEF_RULES_DIR=/usr/share/spamassassin,
LOCAL_RULES_DIR=/etc/spamassassin, LOCAL_STATE_DIR=/var/lib/spamassassin
My LOCAL_RULES_DIR is /etc/mail/spamassassin, and the log did say:
dbg: config: read file /etc/mail/spamassassin/local.cf
I added: bayes_path /etc/sysconfig/sa_bayes line to
/etc/mail/spamassassin/local.cf, but the log said:
dbg: bayes: tie-ing to DB file R/O
/root/.spamassassin/bayes_toks
It ignored the path I set. Shouldn't it be using the bayes_path from my
local.cf?
The initial install of SA on AWS Linux EC2 has a SPAMDOPTIONS="-d -c
-m5 -H". I was told a few months back in this forum that -H without
a parameter following is not even valid and it applies to per-user
stuff.
it _is_ valid and applies per-user config files.
But even if I'm not using per-user, should I still add -H and -c back in?
So I removed the -H. I read that -c creates a user pref file which
sounds like per-user. So I removed that. But the log is telling me
it's loading files from /etc/mail which I thought the docs said was
per-user stuff. Basically, I can't figure out how to make any config
changes that are actually seen by SA.
you thought wrong, I don't know where did you get that info.
/etc/ stores system-wide settings on UN*X systems.
-- Finally, where should I put custom rule files such as KAM.cf
so they are used, but not erased with sa_update?
see LOCAL_RULES_DIR in your debug output
