Nag 3.3.1 emai address not changed

[csbender]

Hi folks 
I am new to the community glad to join you.

We were no longer receiving Nagios alerts. Apparently because IT killed the 
email account for the previous owner. 

I decided to have alerts sent directly to me, as I researched the web I found 
two files to edit. 

nagios.cfg 
db_nagiossql_v3.sql

Painful to say I probably shouldn't have done this. Anyway the maillog is below
and they look correct.

Feb 29 16:41:55 ng postfix/pickup[1947]: 2DC5F18928E4: uid=181 from=<nagios>
Feb 29 16:41:55 ng postfix/cleanup[4317]: 2DC5F18928E4: 
message-id=<20120229164155.2DC5F18928E4 at ng.localdomain>
Feb 29 16:41:55 ng postfix/qmgr[1948]: 2DC5F18928E4: 
from=<nagios at ng.localdomain>, size=777, nrcpt=1 (queue active)
Feb 29 16:41:55 ng postfix/smtp[4319]: 2DC5F18928E4: to=<OLD.USER at abc.com>, 
relay=wmsexg01.abc.com[10.200.104.15]:25, delay=0.24, delays=0.09/0/0.01/0.14, 
dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 3EE5CB18940)
Feb 29 16:41:55 ng postfix/qmgr[1948]: 2DC5F18928E4: removed



Problem is the email is coming from the old user email. I am trying to make it 
come from myself. I have restarted postfix and Nagios but the email is still 
coming fomr old user .

[02-29-2012 16:20:31]  Nagios 3.3.1 starting... (PID=2282) 

First is there a way to clean up these files or test them to see what is wrong?
Second how can I change the email address from which all Nagios emails are 
deliverred from?


Thanks in advance

Regards

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null