Email

Manage the system account's email and Cron notifications

Reviewed on 3 min read espacio de correo cron

cPanel's system account can pile up automatic notifications, especially the output of Cron jobs. It is separate from the domain's usual addresses, and its content also uses up hosting space.

Find out what is generating messages

Go to cPanel > Email Disk Usage and select the system account, usually identified by the cPanel username. Check which folders take up the most space. You can also find it in Email Accounts and open Check Email when that option is offered.

Look through a sample by date and subject. A job that keeps repeating an error can generate thousands of notifications; emptying the inbox does not fix that cause. Keep the messages you need to diagnose it.

Clean up after reviewing

You can select specific messages in webmail or use Manage next to a folder in Email Disk Usage. Before deleting permanently, keep a separate copy of what you need and check that you can open it.

Do not choose Previously viewed just because the notifications have been read, or All messages if you do not want to clear the whole folder. Delete Permanently and emptying the Trash cannot be undone. The email clean-up guide explains the criteria available.

Adjust Cron reports

In cPanel > Advanced > Cron Jobs, the Cron email field sets the general recipient for job output. Check that someone reads that address and that the notifications are useful.

For a job you have already checked and whose output you do not need to keep, adding this to the end of the command:

> /dev/null 2>&1

discards both normal output and errors. It can prevent unnecessary notifications, but it can also hide failures. If you need diagnostics, have the script log to a private location, with rotation, and report the relevant errors.

Typing MAILTO= in the Command field does not set the Cron recipient as a separate crontab variable. To have only some jobs send email, keep the general recipient and adjust each job's output. If each one needs to notify a different address, handle that sending from the script itself or ask us about the case before changing it.

Check the next run

Make sure the job is still doing its work and that its errors remain visible through the channel you chose. Check whether the inbox stops growing and wait for usage to be recalculated. Do not mistake the notifications disappearing for a successful run.

You may also find useful

Something wrong or out of date? Tell us and we will review it.