Well, I feel silly. There are three places MAILTO can affect crond: /etc/crontab, /etc/crond.d/0hourly, and /etc/anacrontab. Once I set this in these 3 files, I started getting mail from crond. Thank you all for your help. --- Chad Cordero Information Technology Consultant Enterprise & Cloud Services Information Technology Services California State University, San Bernardino 5500 University Pkwy San Bernardino, CA 92407-2393 Main Line: 909/537-7677 Direct Line: 909/537-7281 Fax: 909/537-7141 http://support.csusb.edu/ --- Disclaimer: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. From: CentOS <centos-bounces@xxxxxxxxxx> on behalf of Richard <lists-centos@xxxxxxxxxxxxxxxxxxxxx> Reply-To: CentOS mailing list <centos@xxxxxxxxxx> Date: Thursday, July 20, 2017 at 6:54 AM To: CentOS mailing list <centos@xxxxxxxxxx> Subject: Re: Cron sending to root after changing MAILTO Date: Thursday, July 20, 2017 02:25:52 +0000 From: Richard <lists-centos@xxxxxxxxxxxxxxxxxxxxx> Date: Wednesday, July 19, 2017 23:31:10 +0000 From: Chad Cordero <ccordero@xxxxxxxxx> It’s being rejected before it even reaches the mailbox, so forwarding won’t work. Crond should really be using the MAILTO variable and it’s not. In my testing, this worked as advertised. Changing the "MAILTO=" in /etc/crontab from the default "root" to either a local username or a remote address resulted in the crontab messages being delivered to the desired mailboxes. I think I'd put a test command into the crontab and watch the logs to see what might be going on -- including making certain that the crontab is reloading correctly after changing the "mailto" value. Separately, but related, did you run newaliases or postalias after you added the entry to "root:" in /etc/aliases? Re-reading earlier messages, are the commands in question being invoked out of /etc/crontab, /etc/cron.daily, etc. or user-level crontabs? The "mailto" value is crontab file specific, so setting it in /etc/crontab would only effect commands run from there (a file that isn't used much any longer). As the /etc/cron.daily, etc. jobs are now run from /etc/anacrontab you'd need to adjust the "mailto" in that file for things run that way. If run from a user-level crontab the "mailto" needs to be in that user's crontab file. [cron.hourly is run out of /etc/cron.d/0hourly, not anacrontab, and has its own "mailto".] _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx https://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx https://lists.centos.org/mailman/listinfo/centos