If a cron generates any output while it's running, it tries to email it to [EMAIL PROTECTED]
ssmtp is your default MTA, and it's default configuration points to the host mail, at port 25. As mail doesn't resolve to any mail server, that's the sSMTP error you're seeing. If you don't want cron mails, you can redirect ( > ) the output to a file or /dev/null. You could also configure sSMTP to have a reverse alias, so that when it tries to e-mail root, it'll e-mail [EMAIL PROTECTED] This would involve also changing sSMTP to be aware of your ISP's mail hub. -Chris On 20:58 Fri 17 Feb , Michael Kintzios wrote: > Hi All, > > I have not (knowingly) set up my syslog-ng, logrotate, or some other > application to send me mail, so I am curious where this little message came > from: > ======================================= > Feb 17 20:10:02 study1 cron[12102]: (root) CMD (test -x /usr/sbin/run-crons > && /usr/sbin/run-crons ) > Feb 17 20:11:58 study1 sSMTP[12061]: Unable to locate mail > Feb 17 20:11:58 study1 sSMTP[12061]: Cannot open mail:25 > Feb 17 20:11:58 study1 cron[12047]: (root) MAIL (mailed 69 bytes of output > but got status 0x0001 ) > Feb 17 20:20:01 study1 cron[12132]: (root) CMD (test -x /usr/sbin/run-crons > && /usr/sbin/run-crons ) > Feb 17 20:30:01 study1 cron[12144]: (root) CMD (test -x /usr/sbin/run-crons > && /usr/sbin/run-crons ) > ======================================= > > Any ideas? > -- > Regards, > Mick > -- Christopher Cowart Unix Systems Administrator Residential Computing, UC Berkeley "May all your pushes be popped"
signature.asc
Description: Digital signature
