Bug 1761455
Summary: | Unable update sympa_aliases file | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | debugitu <RedHat-Bug> |
Component: | sympa | Assignee: | Xavier Bachelot <xavier> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel7 | CC: | ikeda, xavier |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | sympa-6.2.48-2.el7 sympa-6.2.48-2.fc30 sympa-6.2.48-2.fc29 sympa-6.2.48-2.fc31 sympa-6.2.48-2.el6 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-18 20:56:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
debugitu
2019-10-14 12:42:12 UTC
Hi debugitu, Thanks for the bug report. At first, the sympa_aliases and sympa_aliases.db files didn't look properly set to me. sympa_aliases should be owned by user sympa and group sympa with perms 644. sympa_aliases.db should be owned by user sympa and group root with perms 664. Just curious, is that a fresh installation of sympa ? Anyway, this is not the root cause of the issue. File locking has been modified by upstream. The easiest workaround is probably to 'chown sympa:sympa /var/lib/sympa' as you already discovered. I'll discuss this with upstream. Regards, Xavier Soji, this looks related to commit 391591c05 (and possibly bfa876ecb). This is a fresh installation with following the instructions in the documentation: https://sympa-community.github.io/manual/install/configure-mail-server-sendmail.html Concerning the permission on the file /var/lib/sympa/sympa_aliases, I just followed the instruction found at step number 4: touch $SENDMAIL_ALIASES chmod 640 $SENDMAIL_ALIASES chown sympa:sympa $SENDMAIL_ALIASES Concerning the ownership of /var/lib/sympa/sympa_aliases.db, I set it by my own, according the most restrictive permission still functioning to avoid newaliases errors, based on: ls -lL /usr/bin/newaliases -rwxr-sr-x. 1 root smmsp 836936 Aug 3 2017 /usr/bin/newaliases Excellent support, many thanks! Sorry, the .db file permission is matching the permission of the system's standard alias file: ls -l /etc/aliases.db /var/lib/sympa/sympa_aliases.db -rw-r-----. 1 root smmsp 12288 Oct 14 16:28 /etc/aliases.db -rw-r-----. 1 root smmsp 12288 Oct 14 16:28 /var/lib/sympa/sympa_aliases.db I was referring to the owner/group/perms on the sympa_aliases{,.db} files as set by the rpm on initial install. It shouldn't be necessary to tweak them to get a working sympa install (except for the /var/lib/sympa perms issue related to the relocation of the lock file). However, changing from root to smmsp for the .db group might be something to look at. FEDORA-2019-c2bcb23920 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c2bcb23920 FEDORA-EPEL-2019-6181673f24 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-6181673f24 FEDORA-2019-1c0ea48133 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-1c0ea48133 sympa-6.2.48-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-6ea5b1d015 sympa-6.2.48-2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-1c0ea48133 sympa-6.2.48-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-c2bcb23920 (In reply to Xavier Bachelot from comment #2) > Soji, this looks related to commit 391591c05 (and possibly bfa876ecb). That's right. `/var/lib/sympa/` should have write permission by `sympa` user. sympa-6.2.48-2.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-8886284be5 sympa-6.2.48-2.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-6181673f24 sympa-6.2.48-2.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report. sympa-6.2.48-2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. sympa-6.2.48-2.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. sympa-6.2.48-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. sympa-6.2.48-2.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. |