Red Hat Bugzilla – Bug 115005
Web Traceback forges From: dev-null@rhn.redhat.com
Last modified: 2007-07-31 10:30:46 EDT
Description of problem: When I triggered Bug# 114979, I received a "Web Traceback" containing information about the satellite state at the time of the incident. That email originated from my local system, however the following email headers incorrectly show that the sending system to be: From dev-null@rhn.redhat.com Wed Feb 4 21:18:58 2004 Return-Path: <dev-null@rhn.redhat.com> (snip) X-Authentication-Warning: qa.ckloiber.com: apache set sender to Red Hat Network <dev-null@rhn.redhat.com> using -f (snip) From: Red Hat Network <dev-null@rhn.redhat.com> (snip) Errors-To: Red Hat Network <dev-null@rhn.redhat.com> (The full text of the Web Traceback is attatched to Bugzilla# 114979)
Defer to rhn330
I'll make this a configurable variable for the rhn340sat release.
The From: email address can now be configured via the /etc/rhn/rhn.conf file by setting the 'web.default_mail_from' parameter. If this parameter is not set, a default of 'Red Hat Network <dev-null@rhn.redhat.com>' will be used. Test plan: After installing a satellite, edit /etc/rhn/rhn.conf with something like: web.default_mail_from = booga@redhat.com or web.default_mail_from = booga <booga@redhat.com> Save the file and then restart httpd. After that, do something that generates an email (tickle code to cause a traceback, create a new user or other such event) and verify that the email received has a From: header equal to what you put in rhn.conf. If that is not the case, this bug fails qa.
Looks good.
Put the following in /etc/rhn/rhn.conf web.default_mail_from = Red Hat (Vienna, VA) Satellite<admin@rhnsat.vienna.redhat.com> Restarted httpd & taskomatic and now the From: looks like: From: Red Hat Satellite <admin@redhat.com> It looks like it stripped out everything between the () . It also changed the domain name (dropped the hostname and the first part of the domainname).
The () strippage is your email client I believe. The domain munging is our "corporate rewrite rules in the corporate email exchanger" (according to nhansen). I see the same behavior.
As I'm sure this bug is working in production, I'm going to move it to closed.