Bill Cole <[email protected]> writes:
> On 2023-11-01 at 07:50:38 UTC-0400 (Wed, 01 Nov 2023 12:50:38 +0100)
> Cecil Westerhof <[email protected]>
> is rumored to have said:
>
>> Since some time I see that when I want to update the spamassassin
>> filters I get error 74 for every email that I use to train the
>> filters. What could be happening here?
>
> We really would need a lot more context to answer that.
Using scripts that hide things has his problems. :-(
The script was using:
sa-update
And when I run that from the command line I get:
gpg: WARNING: unsafe ownership on homedir '/etc/spamassassin/sa-update-keys'
Using --nogpg does not give this warning.
But I prefer not having an unsafe ownership.
Sadly after running with --nogpg I do not get the when I run it
without.
The directory itself has drwx------, what seems OK to me.
Or is it about /etc/spamassassin? This has drwxr-xr-x.
> In SOME contexts, '74' is defined as EX_IOERR. That would indicate a
> problem with the underlying storage (OR network connection, in some
> cases) used for your Bayes database.
>
> What database are you using for Bayes?
I do not know. How can I find this out?
Installed about ten years ago on the then current Debian with the
defaults.
> What tool are you using to learn messages?
I was confused. It was sa-update that went wrong.
> What platform are you running on? (OS, distro, perl version, etc.)
Debian 12.
sa-update version 4.0.0 / svn1900642
running on Perl version 5.36.0
> What version of SpamAssassin are you using?
4.0.0
> I see that you asked about this same issue(?) on this mailing list in
> October 2018 but I do not see any resolution from that time...
I did not remember that.
This time it was probably because of the update to Debian 12. But
there was not a new version in 2018.
--
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof
