Stop cron emails

Silence the email cron sends after every run, while keeping the ones that actually indicate a failure.

Stop receiving an email every time a cron job runs. Applies to shared, reseller and Premium hosting.

Cron emails you anything a job prints. A job running every five minutes that prints a single line produces nearly 300 emails a day, and they quickly become noise nobody reads — which means a real failure goes unnoticed too.

Discard everything

Append to the command:

0 2 * * * /home/cpaneluser/backup.sh > /dev/null 2>&1

> /dev/null sends normal output (STDOUT) nowhere.
2>&1 sends errors (STDERR) to the same place.

Together they silence the job completely.

Better: keep the errors

Discarding errors too means a broken job fails silently, and you find out when something downstream is missing.

0 2 * * * /home/cpaneluser/backup.sh > /dev/null

This discards normal output but still emails you anything written to STDERR — silence when it works, a message when it does not. That is usually what you want.

Or route them elsewhere

The Cron Email field at the top of cPanel's Cron Jobs page sets where all cron output goes. Point it at a mailbox you can filter rather than your main address.

Clearing the field entirely disables cron email for the account — including genuine errors, so prefer per-job redirection.

Cron emails count towards your sending limits and consume disk space in the destination mailbox. Several noisy jobs can produce thousands of messages a month.

If they keep arriving

The redirection is in the wrong place. It must be at the end of the whole command, after any arguments.
The job writes to STDERR. With > /dev/null alone, errors still arrive — which is the intended behaviour. Add 2>&1 if you want silence regardless.
A wrapper script is sending its own mail, independently of cron.