+++ This bug was initially created as a clone of Bug #484612 +++

This problem has to do with the mechanism for sending mail inside the MonitoringScout service when it starts up. We wants that email to be sent with a custom "from" and "reply-to" section.  Right now, the email is sent from a static HTTPS-MX email address.  There are many configuration directives that could be used to satisfy this from the config files, however they are never called.

Here's the program flow for the start up script to the email being sent:
/home/nocpulse/bin/npBootstrap.pl
-> populates $gritchMsg with output string found in email that needs to be changed.
-> Line 116:  $soapbox->gritch("Email subject", $gritchMsg);  # called to send message

/usr/lib/perl5/site_perl/5.8.5/NOCpulse/Gritch.pm
-> Line 64:  $self->mx gets populated from the "targetMX" config directive "gritch" section of /etc/NOCpulse.ini
-> Line 211: $self->sendmail($subject,$message); # sends the mail
-> Line 385: Starts to create a LWP request to https://satellite/cgi-bin/https_mx.cgi
-> Line 400: Makes HTTPS request to itself on /cgi-bin/https_mx.cgi

/etc/httpd/conf/rhn/rhn_monitoring.conf
-> Line 34:  Creates a handler for /cgi-bin/https_mx.cgi to be NOCpulse::HttpsMX

/usr/lib/perl5/site_perl/5.8.5/NOCpulse/HttpsMX.pm
-> Line 32:  Sends a mail message from to, subject and body parameters passed to cgi.

There is nothing in this process that configures the "from" field in the email.  That value is statically set to HTTPS-MX in the invocation of the sendmail command.  In order for this to work, there would need to be a configuration directive placed into the /etc/NOCpulse.ini file (replyToEmail maybe?) which Gritch.pm would need to use to send the mail.  Then, a corresponding POST parameter in HttpsMX.pm to accept another parameter for from/reply-to.  

In all honesty, the HttpsMx.pm module should be beefed up substantially to handle advanced configurations.  It would take minimal changes and provide much more flexible notifications.