Description of problem:
SELinux is preventing esmtp from 'getattr' accesses on the file /.esmtp_queue/BG0F4LzE/mail.
***** Plugin restorecon (99.5 confidence) suggests ************************
If you want to fix the label.
/.esmtp_queue/BG0F4LzE/mail default label should be default_t.
Then you can run restorecon.
Do
# /sbin/restorecon -v /.esmtp_queue/BG0F4LzE/mail
***** Plugin catchall (1.49 confidence) suggests **************************
If you believe that esmtp should be allowed getattr access on the mail file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep esmtp /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
Additional Information:
Source Context system_u:system_r:system_mail_t:s0-s0:c0.c1023
Target Context system_u:object_r:root_t:s0
Target Objects /.esmtp_queue/BG0F4LzE/mail [ file ]
Source esmtp
Source Path esmtp
Port <Unknown>
Host (removed)
Source RPM Packages
Target RPM Packages
Policy RPM selinux-policy-3.13.1-126.fc22.noarch
Selinux Enabled True
Policy Type targeted
Enforcing Mode Permissive
Host Name (removed)
Platform Linux (removed) 4.0.4-301.fc22.x86_64 #1 SMP Thu
May 21 13:10:33 UTC 2015 x86_64 x86_64
Alert Count 1
First Seen 2015-05-31 09:00:07 CEST
Last Seen 2015-05-31 09:00:07 CEST
Local ID 2bd56fae-33b8-436d-9d5d-6dbd1c3429cf
Raw Audit Messages
type=AVC msg=audit(1433055607.43:570): avc: denied { getattr } for pid=6760 comm="esmtp" path="/.esmtp_queue/BG0F4LzE/mail" dev="dm-3" ino=131076 scontext=system_u:system_r:system_mail_t:s0-s0:c0.c1023 tcontext=system_u:object_r:root_t:s0 tclass=file permissive=1
Hash: esmtp,system_mail_t,root_t,file,getattr
Version-Release number of selected component:
selinux-policy-3.13.1-126.fc22.noarch
Additional info:
reporter: libreport-2.5.1
hashmarkername: setroubleshoot
kernel: 4.0.4-301.fc22.x86_64
type: libreport
Potential duplicate: bug 1212108
Comment 1Dan Mossor [danofsatx]
2015-09-17 19:31:34 UTC
*** This bug has been marked as a duplicate of bug 1149164 ***