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.
On 28/05/2020 15:22, Matus UHLAR - fantomas wrote:
On 28.05.20 13:38, Bert Van de Poel wrote:
We're using a global bayes_path defined in local.cf:
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/ ?
