Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1271129 - Setting email_reply_address is not used without restart of Foreman
Summary: Setting email_reply_address is not used without restart of Foreman
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Email
Version: 6.1.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
Assignee: Stephen Benjamin
QA Contact: Og Maciel
URL: http://projects.theforeman.org/issues...
Depends On:
Blocks: 1122832
TreeView+ depends on / blocked
Reported: 2015-10-13 08:33 UTC by Peter Vreman
Modified: 2019-09-26 15:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-07-27 08:57:56 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 12155 0 None None None 2016-04-22 16:21:57 UTC
Red Hat Product Errata RHBA-2016:1500 0 normal SHIPPED_LIVE Red Hat Satellite 6.2 Base Libraries 2016-07-27 12:24:38 UTC

Description Peter Vreman 2015-10-13 08:33:18 UTC
Description of problem:
Changing the setting email_reply_address the new value is not used until Foreman is restarted

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

How reproducible:

Steps to Reproduce:
1. Change the email_reply_address setting to foobar
2. Trigger a mail sending

Actual results:
The from address is still using the original from address and not the updated foobar

Expected results:
Mail from address is changed to foobar

Additional info:

Comment 1 Bryan Kearney 2015-10-13 17:54:28 UTC
Created redmine issue http://projects.theforeman.org/issues/12155 from this bug

Comment 3 Bryan Kearney 2015-10-15 14:03:58 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/12155 has been closed
Applied in changeset commit:4fdf2f97ad63898dee899f8fe77dd9e47221ffca.

Comment 5 Bryan Kearney 2015-11-13 19:02:34 UTC
Upstream bug assigned to stbenjam@redhat.com

Comment 7 Og Maciel 2016-03-22 19:39:30 UTC
Verified this issue using Satellite 6.2.0 SNAP 4.0 build on a RHEL 7.2 x86_64 system.


* Configure your Satellite system to use email notifications by updating your /etc/foreman/email.yaml file and providing valid values for all required attributes
* Restart the entire stack by running katello-service restart
* Once the system is back online, use the web ui and update your user's configuration (click on your user name on the upper right corner of the UI after you've logged in and click the My Account link) to include a valid email address
  NOTE: using gmail accounts most likely won't work, so use another email
* Then, under the Email Preferences form (still in the My Account page), enable all types of email notifications available
* Create a new custom YUM repository (use https://omaciel.fedorapeople.org/fakerepo02/ for example) and synchronize it

You should receive an email stating that the new repo was successfully synced.

* Update the email address to another valid email address and repeat the steps of creating a new repo (use https://omaciel.fedorapeople.org/fakerepo01/ this time) and syncing it.

Comment 10 errata-xmlrpc 2016-07-27 08:57:56 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.


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