Description of problem: SELinux is preventing esmtp from 'read' accesses on the file /.esmtp_queue/WaIplPgF/mail. ***** Plugin restorecon (99.5 confidence) suggests ************************ If you want to fix the label. /.esmtp_queue/WaIplPgF/mail default label should be default_t. Then you can run restorecon. Do # /sbin/restorecon -v /.esmtp_queue/WaIplPgF/mail ***** Plugin catchall (1.49 confidence) suggests ************************** If you believe that esmtp should be allowed read 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/WaIplPgF/mail [ file ] Source esmtp Source Path esmtp Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-116.fc22.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.0.0-0.rc2.git0.1.fc22.x86_64 #1 SMP Tue Mar 3 21:24:17 UTC 2015 x86_64 x86_64 Alert Count 1 First Seen 2015-03-11 01:14:05 YEKT Last Seen 2015-03-11 01:14:05 YEKT Local ID 0572a3f9-9389-46d2-8679-67b203c0e1d7 Raw Audit Messages type=AVC msg=audit(1426018445.646:612): avc: denied { read } for pid=6073 comm="esmtp" path="/.esmtp_queue/WaIplPgF/mail" dev="sda1" ino=1831428 scontext=system_u:system_r:system_mail_t:s0-s0:c0.c1023 tcontext=system_u:object_r:root_t:s0 tclass=file permissive=0 Hash: esmtp,system_mail_t,root_t,file,read Version-Release number of selected component: selinux-policy-3.13.1-116.fc22.noarch Additional info: reporter: libreport-2.4.0 hashmarkername: setroubleshoot kernel: 4.0.0-0.rc2.git0.1.fc22.x86_64 type: libreport Potential duplicate: bug 1140493
Same issue like this one 1140493.
Description of problem: Happened after installing Fedora 22. Had only run 'dnf update' and added online accounts such as Google Version-Release number of selected component: selinux-policy-3.13.1-122.fc22.noarch Additional info: reporter: libreport-2.5.1 hashmarkername: setroubleshoot kernel: 4.0.1-300.fc22.x86_64 type: libreport
*** Bug 1215186 has been marked as a duplicate of this bug. ***
Description of problem: I don't know what casued the problem but this is a duplicate of a problem reported against Fedora 21 (1149164). Version-Release number of selected component: selinux-policy-3.13.1-128.1.fc22.noarch Additional info: reporter: libreport-2.6.0 hashmarkername: setroubleshoot kernel: 4.0.5-300.fc22.x86_64 type: libreport
Description of problem: I don't know how this happened or what has caused it. I do know that the same machine had a similar problem when using Fedora 21. The machine was not upgraded using fedup but by doing a new install and then restoring just data. The problem had not occured until today, although I have had problems with SELinux troubleshooter that may have hidden it. Version-Release number of selected component: selinux-policy-3.13.1-128.2.fc22.noarch Additional info: reporter: libreport-2.6.0 hashmarkername: setroubleshoot kernel: 4.0.6-300.fc22.x86_64 type: libreport
Description of problem: When I booted up my system today I saw this error pop up in SELinux. At first I thought it may be the type of error that could be fixed with a restart but after restarting the computer the error appeared again. It does not appear immediately; it usually appears within a minute or two after the machine boots up and is logged in. I am giving the option to use restorecon to fix the file but since I do not know what type of file this is I'd rather not alter it since it could be malicious. Version-Release number of selected component: selinux-policy-3.13.1-128.12.fc22.noarch Additional info: reporter: libreport-2.6.2 hashmarkername: setroubleshoot kernel: 4.1.6-201.fc22.x86_64 type: libreport
Description of problem: This error appeared after the machine had been on for several hours. It appears to originate in the folder that coorisponds with my mail program evoloution. I have the option to use restorecon but I'm not sure if I should do that sicne I don't recognize the file. Version-Release number of selected component: selinux-policy-3.13.1-128.12.fc22.noarch Additional info: reporter: libreport-2.6.2 hashmarkername: setroubleshoot kernel: 4.1.6-201.fc22.x86_64 type: libreport
*** This bug has been marked as a duplicate of bug 1149164 ***