Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1292747 - Satellite's email configuration should use sendmail by default and not 'smtp.example.com'
Summary: Satellite's email configuration should use sendmail by default and not 'smtp....
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Email
Version: 6.1.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Stephen Benjamin
QA Contact: Bruno Rocha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-18 09:33 UTC by Rich Jerrido
Modified: 2019-09-25 20:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 17:01:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15704 0 None None None 2016-07-15 14:32:10 UTC

Description Rich Jerrido 2015-12-18 09:33:43 UTC
Description of problem:


As a user I would like to have the default email configuration (specified in /etc/foreman/email.yml) to be changes to 'localhost' from 'smtp.example.com'

The reasoning for this is the following:

* Almost every server system has a local MTA (even if all that MTA does is relay mail to another). 
* If I mail-enable a user accidentally without specifying an MTA, many of my tasks that send email (repository sync or content view promotion) end in a 'warning' state due to not being able to connect to 'smtp.example.com' 
* Having the email sent to my local MTA allows the MTA the ability to retry delivery, queue the message and various other mail delivery tasks that MTA are good at. 

Version-Release number of selected component (if applicable):
katello-2.2.0.16-1.el7sat.noarch
foreman-1.7.2.49-1.el7sat.noarch




Additional info:

Comment 1 Stephen Benjamin 2016-07-15 14:32:08 UTC
Created redmine issue http://projects.theforeman.org/issues/15704 from this bug

Comment 2 Stephen Benjamin 2016-07-15 14:42:14 UTC
I think sendmail has a better chance of 'just working' on a un*x system

Comment 3 Evgeni Golov 2016-07-15 15:07:24 UTC
+1 on sendmail

Comment 4 Bryan Kearney 2016-07-15 16:10:27 UTC
Upstream bug assigned to stbenjam

Comment 5 Bryan Kearney 2016-07-15 16:10:30 UTC
Upstream bug assigned to stbenjam

Comment 7 Bryan Kearney 2016-07-18 12:12:03 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/15704 has been closed

Comment 10 Bruno Rocha 2016-11-17 18:29:39 UTC
Verified in:

satellite-6.3.0-6.1.beta.el7sat.noarch - RHEL7
katello-3.2.0-3.rc3.el7.noarch
foreman-1.13.1-1.el7.noarch

Conclusion:

it defaults to sendmail

cat /etc/foreman/email.yaml 
# Outgoing email settings

production:
  delivery_method: :sendmail

Comment 11 Bryan Kearney 2018-02-21 17:01:59 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0336


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