Bug 553277
| Summary: | regression in selinux-policy-2.4.6-255.el5_4.3 breaks postfix /usr/sbin/sendmail interface | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Tuomo Soini <tis> |
| Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
| Status: | CLOSED DUPLICATE | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.4.z | CC: | andri, bugzilla.redhat, dave-bugzilla, dwalsh, rhel, segvfault |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-01-09 13:50:44 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Tuomo Soini
2010-01-07 15:07:28 UTC
I don't have a problem with that. Not sure why the change was made. I have same problem: selinux-policy-2.4.6-255.el5_4.3 postfix-2.3.3-2.1.el5_2 mailx-8.1.1-44.2.2 If i disable SELinux works fine ...but if its enable i get: # mail root Subject: test test . Cc: send-mail: warning: premature end-of-input on /usr/sbin/postdrop -r while reading input attribute name send-mail: fatal: root(0): unable to execute /usr/sbin/postdrop -r: Success and in audit.log i dont see any entry about this Postfix work good with SELinux enabled i can receive and send mails with mail clients I also have the same problem: postfix/sendmail[20232]: warning: premature end-of-input on /usr/sbin/postdrop -r while reading input attribute name postfix/sendmail[20232]: fatal: gabriel(532): unable to execute /usr/sbin/postdrop -r: Success I lost all mail forwarded with procmail. Gabriel I have posted a fix for this in the duplicate. *** This bug has been marked as a duplicate of bug 553492 *** |