Description of problem: amavis and spampd both are designed to work with spamassassin. Both fail to work. This has to do with permissions on /var/lib/spamassassin and possibly /etc/mail/spamassassin and subdirs. Both amavis and spampd run as their own user. They need ability to write if bayes learning is enabled, I believe. /var/lib/spamassassin's subdirs seem to be the biggest problem. sa-update creates dirs with NO other and NO group permissions. Is it possible to create a spamassassin group with amavis and spampd as members? Is it possible to fix /var/lib/spamassassin's group as rwx and get sa-update to not make group --- permissions? Version-Release number of selected component (if applicable): amavis-2.12.1-6.fc34.noarch spampd-2.61-1.fc34.noarch spamassassin-3.4.6-1.fc34.x86_64 https://bugzilla.redhat.com/show_bug.cgi?id=1992749 (comment #6 and later) https://bugzilla.redhat.com/show_bug.cgi?id=1994831
This mostly (/var/lib/spamassassin/*) appears to be a problem if you run sa-update instead of sa-update.service.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.