We're using a global bayes_path defined in local.cf:
use_bayes 1
use_bayes_rules 1
bayes_auto_learn 1
bayes_expiry_max_db_size 1500000
bayes_path /var/lib/spamassassin/bayes_db/bayes
bayes_file_mode 0775
bayes_ignore_to spam-analy...@ulyssis.org
bayes_ignore_from spam-analy...@ulyssis.org
bayes_auto_learn_threshold_nonspam 0.1
bayes_auto_learn_threshold_spam 10.0
score BAYES_00 -0.001 -0.001 -0.001 -0.001
score BAYES_05 -0.001 -0.001 -0.001 -0.001
score BAYES_20 -0.001 -0.001 -0.001 -0.001
score BAYES_40 -0.001 -0.001 -0.001 -0.001
score BAYES_50 0.001 0.001 0.001 0.001
score BAYES_60 0.001 0.001 0.001 0.001
score BAYES_80 0.001 0.001 0.001 0.001
score BAYES_95 0.001 0.001 0.001 0.001
score BAYES_99 0.001 0.001 0.001 0.001
score BAYES_999 0.001 0.001 0.001 0.001
Currently we're still evaluating the amount of false positives (and
contacting users who seem to have broken cronjobs that confuse bayes)
before taking away the artificial scores. We wanted to clear up our
sa-compile cronjob error.
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/ ?
