Cron Job Email Messages

We have had some email issues that have been corrected recently which, as a result, time nicely with the beginning of email messages coming from our cron jobs. My web host tells me that cron is working right, that our cron jobs are running, and the C5 dashboard tells me that our cron jobs are running correctly. However, every single time a cron job runs I receive an email with the results. My webhost also tells me that there is no cpanel setting in our host that would send or not send email, that there is probably a configuration in my CMS to send cron results over email when they run.

My question is this: Is there such a setting? The only cron job is the automated job cron entry that C5 produces on the automated jobs page. On that page the only thing email related I see is the "Process Email Posts" job.

Should I be receiving cron results with each run with C5 by default? I really only want to know if there is a problem.


View Replies: View Best Answer
ob7dev replied on at Permalink Reply
If you want the results of an automated job emailed to you, according to my research you can set up the Default job to run via cron on the server, and you can then pipe the cron results to a mail command so that you get those emailed to you.

I don't know if c5 is set up to send the email itself from PHP after a job is run, but I do know you can set up the automated job to run through cron on your server and from the server you can email the results to yourself.

When I run the Default automated job via the URL in c5, I don't receive an email with results.
So if you're getting email results of the automated job, then I'm assuming your running the automated job through cron and not via the c5 URL method. And if cron is emailing you the results then your server is set up to send the cron results (probably to the admin user of the server).
ConcreteOwl replied on at Permalink Best Answer Reply
I use my server cron jobs to perform all sorts of tasks on my sites, I prevent emails being sent to me by appending this code to the command line
>/dev/null 2>&1
bayleafmedia replied on at Permalink Reply
This is the option I went for. Thanks ConcreteOwl
Tate204 replied on at Permalink Reply
You may try as a trigger, easy to find issue.