Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 126458 - RHN Applet does not email status to correct address
RHN Applet does not email status to correct address
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rhn-applet (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Depends On:
  Show dependency treegraph
Reported: 2004-06-21 18:17 EDT by Johnny Proton
Modified: 2012-06-20 12:03 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 12:03:57 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 Johnny Proton 2004-06-21 18:17:15 EDT
I have replicated this problem using RHEL 3.0 and Fedora Core 1 & 2. 
My hosting partner, Rackspace, feels the problem is with the RHN
applet but I'm not sure.

Basically, if I SSH as root into my new system and run "up2date
--configure --nox", item #25 is "Admin Email Address".  It's always
defaulted to root@localhost but I want it to be something else.

No matter what I set that address to, it never emails me *anything*
except to root@localhost.  What is the point of this field?  This
applies when I run an update myself as well as when the rhn_check
applet does its scheduled maintenance.

This is a big one for people with dedicated servers.  I think there
should be a lot of people affected by this bug.
Comment 2 Jiri Pallich 2012-06-20 12:03:57 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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