Bug 740150 - More mail (mailman, procmail) woes with unconfined disabled
Summary: More mail (mailman, procmail) woes with unconfined disabled
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 15
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-09-21 06:11 UTC by Robin Powell
Modified: 2011-12-04 02:35 UTC (History)
3 users (show)

Fixed In Version: selinux-policy-3.9.16-48.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-12-04 02:35:55 UTC

Attachments (Terms of Use)

Description Robin Powell 2011-09-21 06:11:18 UTC
So mailman is working OK from the exim server per https://bugzilla.redhat.com/show_bug.cgi?id=730624 , but when a user runs sendmail/exim directly on the command line for an address that goes to mailman on the same server, it all goes to pot.

The following seems to fix it up:

module mymailman2 1.0;

require {
        type staff_t;
        type user_t;
        type mailman_mail_t;
        type exim_t;

role staff_r types mailman_mail_t;
role user_r types mailman_mail_t;


Comment 1 Daniel Walsh 2011-09-21 15:19:33 UTC
Fixed in selinux-policy-3.10.0-33.fc16

Comment 2 Fedora Update System 2011-11-16 16:17:40 UTC
selinux-policy-3.9.16-48.fc15 has been submitted as an update for Fedora 15.

Comment 3 Fedora Update System 2011-11-17 23:36:01 UTC
Package selinux-policy-3.9.16-48.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.9.16-48.fc15'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2011-12-04 02:35:55 UTC
selinux-policy-3.9.16-48.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.