This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 507894 - cron mail delivery fails with esmtp installed
cron mail delivery fails with esmtp installed
Product: Fedora
Classification: Fedora
Component: esmtp (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Steven M. Parrish
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-06-24 12:18 EDT by Richard Henderson
Modified: 2014-09-29 12:14 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 09:16:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Richard Henderson 2009-06-24 12:18:55 EDT
Description of problem:

SELinux is preventing esmtp (system_mail_t) "read" to /.esmtp_queue/hb7RiUtM/mail (root_t). 

Yes, that's "/", not "/root" or any other home directory, as
esmtp-wrapper is expecting.

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


Steps to Reproduce:
1. Install esmtp
2. Set esmtp-wrapper as the local mta via "alternatives --config mta"
3. Wait for, or force nightly cron jobs to run.
Actual results:
SELinux error.

Expected results:
Mail delivered to root.

Additional info:
I think queueing locally delivered cron mail is a bit silly.  Perhaps
something akin to the following added to esmtp-wrapper would do the trick:

  # Don't try to queue if $HOME hasn't been setup.
  [ -n "$HOME" ] || exec $esmtp $@
Comment 1 Steven M. Parrish 2009-10-02 09:46:57 EDT
Did you try your proposed fix and did it work.  If so if you can create a patch and send it to I will include it locally and submit upstream as well.  Thanks 

Steven M. Parrish - KDE Triage Master
                  - PackageKit Triager
Fedora Bugzappers volunteer triage team
Comment 2 Bug Zapper 2010-04-27 11:13:32 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 WONTFIX if it remains open with a Fedora 
'version' of '11'.

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 prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here:
Comment 3 Bug Zapper 2010-06-28 09:16:31 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 4 Richard Henderson 2014-09-29 12:14:57 EDT

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