Bug 228126 - postfix error due to selinux
postfix error due to selinux
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: postfix (Show other bugs)
rawhide
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Thomas Woerner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-09 22:06 EST by Florin Andrei
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-11-28 10:54:07 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Florin Andrei 2007-02-09 22:06:03 EST
Description of problem:
avc: denied { read } for comm="pickup" dev=sda3 egid=89 euid=89
exe="/usr/libexec/postfix/pickup" exit=-13 fsgid=89 fsuid=89 gid=89 items=0
name="maildrop" pid=7932 scontext=user_u:system_r:postfix_pickup_t:s0 sgid=89
subj=user_u:system_r:postfix_pickup_t:s0 suid=89 tclass=dir
tcontext=system_u:object_r:postfix_spool_maildrop_t:s0 tty=(none) uid=89 

Version-Release number of selected component (if applicable):
postfix-2.3.6-1

How reproducible:
always

Steps to Reproduce:
1. install postfix via yum
2. try and run postfix
3.
  
Actual results:
see above

Expected results:
no selinux errors

Additional info:
restorecon -v /var/spool/postfix/maildrop did not help

Source Context:  user_u:system_r:postfix_pickup_t:s0
Target Context:  system_u:object_r:postfix_spool_maildrop_t:s0
Comment 1 Bill Nottingham 2007-03-02 12:31:43 EST
Moving to 'devel' as discussed on
https://www.redhat.com/archives/fedora-devel-list/2007-March/msg00095.html.
Comment 2 Thomas Woerner 2007-09-24 12:22:50 EDT
Do you have a special postfix configuration? Or does this happen with the
standard configuration?
Comment 3 Thomas Woerner 2007-11-28 10:54:07 EST
This bug entry was in needinfo for some time. Closing due to user inactivity as
"NOT A BUG".

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