This seems to be a strange setup.  Looks lke for some reason esmtp thinks / is your root homedir rather then /root?

Any idea why

Description of problem:
1. Ran dnf update

Additional info:
reporter:       libreport-2.2.3
hashmarkername: setroubleshoot
kernel:         3.15.10-201.fc20.x86_64
type:           libreport

Re: /root vs / - I don't remember specifically making any changes to the system for it to think / is root's home dir.

This bug happens to me about once or twice in a month.
It seems to be caused by the smartd (smartmontools) and freshclam (clamav) daemons trying to send some mail instead of logging.
I think adding a rule to allow this behavior is wrong, instead the bug(s) causing write access to /.esmtp/ should be fixed.

Why is it located directly in / ?

There is/was a similiar bug in abrt where $HOME was not set.
btw: this happens on x86_64 with both F20 and F21.

(In reply to Christian Stadelmann from comment #4)
> This bug happens to me about once or twice in a month.
> It seems to be caused by the smartd (smartmontools) and freshclam (clamav)
> daemons trying to send some mail instead of logging.
> I think adding a rule to allow this behavior is wrong, instead the bug(s)
> causing write access to /.esmtp/ should be fixed.

definitely.

And before doing that, a new version of ESMTP has been out for many years and should finally find its way into Fedora - #1051667

Hi, please see also bug 1202562.

Shortly: cronie does NOT set HOME env var when it runs sendmail (which is a symlink to esmtp-wrapper).

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Hello guys, I have the same problem on F22:

SELinux is preventing esmtp from read access on the file /.esmtp_queue/WcQXCAjq/mail.

*****  Plugin restorecon (99.5 confidence) suggests   ************************

If you want to fix the label. 
/.esmtp_queue/WcQXCAjq/mail default label should be default_t.
Then you can run restorecon.
Do
# /sbin/restorecon -v /.esmtp_queue/WcQXCAjq/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/WcQXCAjq/mail [ file ]
Source                        esmtp
Source Path                   esmtp
Port                          <Unknown>
Host                          w541
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-128.13.fc22.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     w541
Platform                      Linux w541 4.1.6-201.fc22.x86_64 #1 SMP Fri Sep 4
                              17:49:24 UTC 2015 x86_64 x86_64
Alert Count                   832897
First Seen                    2015-09-19 10:28:06 CEST
Last Seen                     2015-09-20 09:27:05 CEST
Local ID                      a8af909f-0209-45d7-9992-96949c9f5aa0

Raw Audit Messages
type=AVC msg=audit(1442734025.596:886907): avc:  denied  { read } for  pid=27732 comm="esmtp" path="/.esmtp_queue/WcQXCAjq/mail" dev="dm-3" ino=431662 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




I deleted the directory (because the system was cluttered with the load), which resulted in:

SELinux is preventing mkdir from write access on the directory /.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that mkdir should be allowed write access on the  directory 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 mkdir /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                / [ dir ]
Source                        mkdir
Source Path                   mkdir
Port                          <Unknown>
Host                          w541
Source RPM Packages           
Target RPM Packages           filesystem-3.2-32.fc22.x86_64
Policy RPM                    selinux-policy-3.13.1-128.13.fc22.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     w541
Platform                      Linux w541 4.1.6-201.fc22.x86_64 #1 SMP Fri Sep 4
                              17:49:24 UTC 2015 x86_64 x86_64
Alert Count                   4241
First Seen                    2015-09-20 09:28:01 CEST
Last Seen                     2015-09-23 08:17:01 CEST
Local ID                      ba2e3f5b-6e53-4dbd-b7ac-a621d60dac16

Raw Audit Messages
type=AVC msg=audit(1442989021.181:908854): avc:  denied  { write } for  pid=17890 comm="mkdir" name="/" dev="dm-3" ino=2 scontext=system_u:system_r:system_mail_t:s0-s0:c0.c1023 tcontext=system_u:object_r:root_t:s0 tclass=dir permissive=0


Hash: mkdir,system_mail_t,root_t,dir,write


I wanted to kill `esmtp` process, but it did not exist. After couple of minutes the load ceased and the system was usable again.

OK I read it's because esmtp is started by cron:

    /usr/sbin/sendmail -FCronDaemon -i -odi -oem -oi -t -f root


not setting the $HOME dir. So what I did to avoid high utilization every couple of minutes I added:

    [ $HOME ] || HOME="/root"

at the beginning of the `/usr/bin/esmtp-wrapper` file and it works fine for me.

(In reply to Lukas Doktor from comment #12)
> OK I read it's because esmtp is started by cron:

most frequently but not entirely. You have also demons which have "/" as home dir but not the permission to actually write anything there and might invoke sendmail.

Your fix will also not work if the recipient is anything else than local root. aliases expansion won't work and remote delivery would require a cron job doing "mailq -s" from time to time. 
Local delivery can be fixed to work without the queue but the case of a demon with "/" as home dir and remote delivery is nasty, would require a globally writable queue dir with all the known pitfalls.

Description of problem:
No steps to repro. I was away from my computer for several hours; when I came back, a notification informed me of the SELinux alert.

Version-Release number of selected component:
selinux-policy-3.13.1-128.16.fc22.noarch

Additional info:
reporter:       libreport-2.6.2
hashmarkername: setroubleshoot
kernel:         4.1.10-200.fc22.x86_64
type:           libreport

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.