Hi All,
I installed a new CentOS 5.5 box and I am getting a daily e-mail (I am not sure how this was triggered) with XNTPD logs, HTTP Error and Disk Space).
It is being sent to root@www.6colors.co which bounces, but I have a catch all so it does get to me.
How do I change where this e-mail is sent? I have tried in /etc/postfix/main.cd, master.cf, bounce.cf.default, etc and I don't see where this is set.
Can anyone help out?
Best, -Jason
On Wed, 2010-12-22 at 08:12 -0800, Jason T. Slack-Moehrle wrote:
I installed a new CentOS 5.5 box and I am getting a daily e-mail (I am not sure how this was triggered) with XNTPD logs, HTTP Error and Disk Space).
It is being sent to root@www.6colors.co which bounces, but I have a catch all so it does get to me.
How do I change where this e-mail is sent? I have tried in /etc/postfix/main.cd, master.cf, bounce.cf.default, etc and I don't see where this is set.
Its LOGWATCH what is doing it. It will be scheduled in / ETC / CRONTAB
Regards,
Paul.
Hi
you have to add the record to /etc/aliases:
root: you@adress.tld
and then run: newaliases
Pavel
Dne 22.12.2010 17:17, Always Learning napsal(a):
On Wed, 2010-12-22 at 08:12 -0800, Jason T. Slack-Moehrle wrote:
I installed a new CentOS 5.5 box and I am getting a daily e-mail (I am not sure how this was triggered) with XNTPD logs, HTTP Error and Disk Space).
It is being sent to root@www.6colors.co which bounces, but I have a catch all so it does get to me.
How do I change where this e-mail is sent? I have tried in /etc/postfix/main.cd, master.cf, bounce.cf.default, etc and I don't see where this is set.
Its LOGWATCH what is doing it. It will be scheduled in / ETC / CRONTAB
Regards,
Paul.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 12/22/2010 10:12 AM, Jason T. Slack-Moehrle wrote:
Hi All,
I installed a new CentOS 5.5 box and I am getting a daily e-mail (I am not sure how this was triggered) with XNTPD logs, HTTP Error and Disk Space).
It is being sent to root@www.6colors.co which bounces, but I have a catch all so it does get to me.
How do I change where this e-mail is sent? I have tried in /etc/postfix/main.cd, master.cf, bounce.cf.default, etc and I don't see where this is set.
Can anyone help out?
If you are running the default sendmail, put an alias for root in /etc/aliases and restart sendmail or run 'newaliases'.
On Wed, 2010-12-22 at 10:25 -0600, Les Mikesell wrote:
If you are running the default sendmail, put an alias for root in /etc/aliases and restart sendmail or run 'newaliases'.
Or you can edit
/etc/share/logwatch/scripts/logwatch.pl
and change line 64
$Config{'mailto'} = "root";
Happy Christmas everyone,
Paul.
On Wed, 2010-12-22 at 10:25 -0600, Les Mikesell wrote:
If you are running the default sendmail, put an alias for root in /etc/aliases and restart sendmail or run 'newaliases'.
Or you can edit
/etc/share/logwatch/scripts/logwatch.pl
and change line 64
$Config{'mailto'} = "root";
Exactly what I did earlier.
-Jason
If you are running the default sendmail, put an alias for root in /etc/aliases and restart sendmail or run 'newaliases'.
Or you can edit
/etc/share/logwatch/scripts/logwatch.pl
and change line 64
$Config{'mailto'} = "root";
Exactly what I did earlier.
I would strongly recommend using /etc/aliases and NOT editing logwatch.pl as any updates to logwatch will collide with your edit, leaving you with .rpmnew files to merge.
On 12/22/2010 12:58 PM, John R Pierce wrote:
If you are running the default sendmail, put an alias for root in /etc/aliases and restart sendmail or run 'newaliases'.
Or you can edit
/etc/share/logwatch/scripts/logwatch.pl
and change line 64
$Config{'mailto'} = "root";
Exactly what I did earlier.
I would strongly recommend using /etc/aliases and NOT editing logwatch.pl as any updates to logwatch will collide with your edit, leaving you with .rpmnew files to merge.
And, there may be other interesting/critical mail coming to root.
On Wed, 22 Dec 2010, Les Mikesell wrote:
*snipped*
And, there may be other interesting/critical mail coming to root.
Good point.
I always have root's email sent to my own user account.
That's one of the things my ALI scripts sets up for me.
echo echo "Processing /etc/aliases config file" echo
# Backup the newly installed aliases configuration file. cp -vpR $ETC_DIR/aliases $ETC_DIR/aliases$ORG_SUFX echo
# Use sed to edit the new aliases file and change # who should get root's email.
echo "Setting up who gets root's email"
sed -i s/#root:.*marc/'root: keith'/ $2/aliases
echo cat $ETC_DIR/aliases echo
Kind Regards,
Keith Roberts
On Wed, 2010-12-22 at 10:25 -0600, Les Mikesell wrote:
If you are running the default sendmail, put an alias for root in /etc/aliases and restart sendmail or run 'newaliases'.
Or you can edit
/etc/share/logwatch/scripts/logwatch.pl
and change line 64
$Config{'mailto'} = "root";
The upside is that this works for logwatch.
The downside is that this *only* works for logwatch.
Aside from the aliases which were previously mentioned, it's just as simple to create /root/.forward, which would then include an entry for the email address to which want the email to be sent.
On Wed, Dec 22, 2010 at 11:12 AM, Jason T. Slack-Moehrle slackmoehrle@me.com wrote:
Hi All,
I installed a new CentOS 5.5 box and I am getting a daily e-mail (I am not sure how this was triggered) with XNTPD logs, HTTP Error and Disk Space).
It is being sent to root@www.6colors.co which bounces, but I have a catch all so it does get to me.
How do I change where this e-mail is sent? I have tried in /etc/postfix/main.cd, master.cf, bounce.cf.default, etc and I don't see where this is set.
Can anyone help out?
Best, -Jason
If you're running sendmail, put an alias in /root/.forward. That gets *all* root email forwarded to the appropriate account, not just cron jobs. It also doesn't require editing of system files such as /etc/aliases.
On 12/22/10 2:24 PM, Nico Kadel-Garcia wrote:
If you're running sendmail, put an alias in /root/.forward. That gets *all* root email forwarded to the appropriate account, not just cron jobs. It also doesn't require editing of system files such as /etc/aliases.
that's a borderline bizarre rationale. /etc/aliases is specifically intended for this, even has a sample line in it to forward root's mail.
On 12/22/2010 4:53 PM, John R Pierce wrote:
On 12/22/10 2:24 PM, Nico Kadel-Garcia wrote:
If you're running sendmail, put an alias in /root/.forward. That gets *all* root email forwarded to the appropriate account, not just cron jobs. It also doesn't require editing of system files such as /etc/aliases.
that's a borderline bizarre rationale. /etc/aliases is specifically intended for this, even has a sample line in it to forward root's mail.
I suppose it does have the advantage of not having to deal with .rpmsave or .rpmnew files if an update would ever modify the contents of /etc/aliases.
On Wed, Dec 22, 2010 at 5:53 PM, John R Pierce pierce@hogranch.com wrote:
On 12/22/10 2:24 PM, Nico Kadel-Garcia wrote:
If you're running sendmail, put an alias in /root/.forward. That gets *all* root email forwarded to the appropriate account, not just cron jobs. It also doesn't require editing of system files such as /etc/aliases.
that's a borderline bizarre rationale. /etc/aliases is specifically intended for this, even has a sample line in it to forward root's mail.
Not at all. If you have a sitewide deployment kickstart system, you do *NOT* want to push dynamic edits to /etc/aliases if you don't have to. And different SMTP servers have distinct handling, or even locations, of the aliases file. Is it /etc/aliases? /etc/mail/aliases? /usr/local/etc/aliases? Do you want to manipulate it on a host by host basis and keep consistent /etc/aliases deployed across all hosts? You pick the situation!!!!
I run into a *LOT* of bizarre situations.