Oh, I had misunderstood you, Matus. My bad! I thought you meant we
should use a separate bayes db for every mailbox user, but now I
understand you were referring to the amavis user which indeed runs
everything.
I just moved the existing bayes db (after stopping amavis of course) to
the amavis user's .spamassassin folder and removed the path from
local.cf and it seems to work just fine and indeed solves our issue with
sa-compile. Thank you very much for the suggestion. This is a much
cleaner solution than what I had initially in mind!
On 28/05/2020 17:03, Matus UHLAR - fantomas wrote:
On 28.05.20 15:32, Bert Van de Poel wrote:
Almost all of the email we process are forwarders. It doesn't really
make sense for us to do a non-global bayes db. The large majority of
email we process is also for a uniform group: student organizations
at our local university.
you have apparently missed what I said before, so I repeat:
you said you use amavis. amavis daemon runs (usually) under amavis
user. Therefore, all mails processed by amavis use amavis' bayes
database stored
in amavis home directory.
move the database to amavis' home (and chown it to the amavis user):
# ls -la ~amavis/.spamassassin/
total 41368
drwx------ 2 amavis amavis 4096 May 28 16:59 .
drwxr-x--- 7 amavis amavis 4096 May 28 06:50 ..
-rw------- 1 amavis amavis 89136 May 28 17:01 bayes_journal
-rw------- 1 amavis amavis 21065728 May 28 16:59 bayes_seen
-rw------- 1 amavis amavis 40144896 May 28 16:59 bayes_toks
-rw-r--r-- 1 amavis amavis 2304 May 5 12:41 user_prefs
Then remove global setting of bayes database in
/etc/spamassassin/local.cf
and your problem will most probably to away.
On 28.05.20 13:38, Bert Van de Poel wrote:
We're using a global bayes_path defined in local.cf:
On 28/05/2020 15:22, Matus UHLAR - fantomas wrote:
This is your problem imho.
if you use amavis, you need no bayes database, but amavis users',
i guess in /var/lib/amavis/.spamassassin/
On 28/05/2020 10:18, Matus UHLAR - fantomas wrote:
On 25.05.20 23:34, Bert Van de Poel wrote:
Recently, we've been setting up Bayesian learning on our existing
Amavis with Spamassassin setup on Ubuntu 18.04 (Spamassassin
3.4.2-0ubuntu0.18.04.3 and Amavis 1:2.11.0-1ubuntu1). We've
decided to use a global db that was seeded with an aggregation of
spam and ham we've received, then enabling autolearn to further
train the set. As Spamassassin runs inside Amavis, the Bayes
database files are owned by the amavis user. This setup works
fine, and results for Bayes are great and growing in accuracy by
autolearning.
What was somewhat confusing is that we noticed our daily cronjob
running sa-update and sa-compile was giving us an error
concerning permissions:
May 25 00:31:25.488 [8381] warn: bayes: cannot write to
/var/lib/spamassassin/bayes_db/bayes_journal, bayes db update
ignored: Permission denied
bayes: cannot write to
/var/lib/spamassassin/bayes_db/bayes_journal, bayes db update
ignored: Permission denied
I wonder where did these files come from.
did you sety bayes_path in /etc/spamassassin/ ?
