Description of problem: /usr/lib/mailman/mail/mailman cannot be executed by mail daemons (e.g. exim), as selinux blocks execution of it, as it does not have a proper type (actually just plain bin_t): $ ls -lZ /usr/lib/mailman/mail/mailman -rwxr-sr-x. 1 root mailman system_u:object_r:bin_t:s0 15640 Mar 2 2016 /usr/lib/mailman/mail/mailman This results in mail daemons not being able to execute the binary and pass a mail to it: May 14 17:23:56 xxxx exim[18240]: 2017-05-14 17:23:56 aaaaa-vvvvv-bc ** foo.com R=mailman_router T=mailman_transport_local: Child process of mailman_transport_local transport returned 127 (could mean unable to exec or command does not exist) from command: /usr/lib/mailman/mail/mailman If we change the type to mailman_mail_exec_t, the daemon can execute the script and pass a mail to mailman. If we look at the current fcontexts, we see two overlapping contexts: /usr/lib/mailman.*/mail/mailman regular file system_u:object_r:mailman_mail_exec_t:s0 /usr/lib/mailman/mail(/.*)? all files system_u:object_r:bin_t:s0 And the second one seems to win, while the first one would be right. Version-Release number of selected component (if applicable): $ rpm -qi mailman Name : mailman Epoch : 3 Version : 2.1.21 Release : 1.fc25 Architecture: x86_64 Install Date: Sun 14 May 2017 09:18:12 PM CEST Group : Applications/Internet Size : 37938256 License : GPLv2+ Signature : RSA/SHA256, Fri 01 Apr 2016 06:13:52 PM CEST, Key ID 4089d8f2fdb19c98 Source RPM : mailman-2.1.21-1.fc25.src.rpm Build Date : Wed 02 Mar 2016 09:21:10 AM CET Build Host : buildvm-12-nfs.phx2.fedoraproject.org Relocations : (not relocatable) Packager : Fedora Project Vendor : Fedora Project URL : http://www.list.org/ Summary : Mailing list manager with built in Web access Additional info: This affects also RHEL / CentOS 7.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.