I'd run "sh -x /etc/cron.daily/spamassassin"
to see what command in that file failed. I assume it is the sa-compile
command.
I got some more results.
Here are the steps I made:
1. Remove everything from /var/lib/spamassassin
2. Reinstall spamassassin package
3. Recreate /var/lib/spamassassin/co
Thanks for your help Ian,
I'd run "sh -x /etc/cron.daily/spamassassin"
to see what command in that file failed. I assume it is the sa-compile command.
Running /etc/cron.daily/spamassassin manually, either with "-x" provided
to the shell or simply by running it, letting the shebang do the job,
Bernard writes:
> I got SpamAssassin on my server for a long time, and from time to time
> it was reporting errors now and then from the daily scheduled task.
>
> However, for the past week, the error is now constant.
>
> I get the following error by email:
> /etc/cron.daily/spamassassin:
> chm
What version are you running, what os version, etc.
Debian (Bullseye) 11 like platform:
SpamAssassin version 3.4.6
running on Perl version 5.32.1
Package: spamassassin
Version: 3.4.6-1
[...]
Maintainer: Noah Meyerhans
[...]
Homepage: https://spamassassin.apache.org/
Bernard
Bernard writes:
> I never really understood what I was doing with SpamAssassin...
What version are you running, what os version, etc.
I got SpamAssassin on my server for a long time, and from time to time
it was reporting errors now and then from the daily scheduled task.
However, for the past week, the error is now constant.
I get the following error by email:
/etc/cron.daily/spamassassin:
chmod: cannot access 'body_0.bs': N
