Just an update to my last mail.
I should have mentioned that the other cron job on the domain that produces a report is for an autoresponder script, and nothing to do with emptying mailboxes.
I've just checked my mailbox for the cron that I set to run every five minutes, and it shows emails from 20th April. So the cron doesn't appear to have impacted on the mailbox since I edited it.
I looked at the disk usage for the email account in cPanel and it's showing usage of 55mb for that mailbox! I only have 22 emails in there according to Webmail, so not sure what has gone wrong there. I checked another account and emptied a mailbox that showed 10mb usage. After logging out. clearing cache, and logging back in, the disk usage is still showing 10mb for that email account.
It does look like something is broken?
I've just downloaded the log from - /var/log/cron and here is an extract for today -
Code:
Apr 22 11:45:01 webhost1 CROND[10119]: (magicalw) CMD (find /home/magicalw/mail/domain.com/myles/cur -type f -mtime +1 -exec rm {} \; )
Apr 22 11:45:01 webhost1 CROND[10121]: (root) CMD (/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1)
Apr 22 11:50:01 webhost1 CROND[11397]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Apr 22 11:50:01 webhost1 CROND[11401]: (root) CMD (/usr/local/maldetect/maldet --mkpubpaths >> /dev/null 2>&1)
Apr 22 11:50:01 webhost1 CROND[11404]: (magicalw) CMD (find /home/magicalw/mail/domain.com/myles/cur -type f -mtime +1 -exec rm {} \; )
Apr 22 11:50:01 webhost1 CROND[11405]: (root) CMD (/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1)
Apr 22 11:55:01 webhost1 CROND[11656]: (magicalw) CMD (find /home/magicalw/mail/domain.com/myles/cur -type f -mtime +1 -exec rm {} \; )
Apr 22 11:55:01 webhost1 CROND[11659]: (root) CMD (/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1)
Apr 22 11:58:01 webhost1 CROND[11802]: (root) CMD (/usr/local/bandmin/bandmin)
Apr 22 11:58:01 webhost1 CROND[11804]: (root) CMD (/usr/local/cpanel/whostmgr/bin/dnsqueue > /dev/null 2>&1)
Apr 22 12:00:01 webhost1 CROND[11902]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Apr 22 12:00:01 webhost1 CROND[11904]: (root) CMD (/usr/local/maldetect/maldet --mkpubpaths >> /dev/null 2>&1)
Apr 22 12:00:01 webhost1 CROND[11914]: (magicalw) CMD (/usr/bin/perl /home/magicalw/public_html/cgi-bin/arp3/arp3-auto.pl 1>&2 > /dev/null)
Apr 22 12:00:01 webhost1 CROND[11917]: (root) CMD (/usr/local/cpanel/bin/dcpumon >/dev/null 2>&1)
Apr 22 12:00:02 webhost1 CROND[11920]: (magicalw) CMD (find /home/magicalw/mail/domain.com/myles/cur -type f -mtime +1 -exec rm {} \; )
Apr 22 12:01:01 webhost1 CROND[12004]: (root) CMD (run-parts /etc/cron.hourly)
Apr 22 12:01:01 webhost1 run-parts(/etc/cron.hourly)[12004]: starting modsecparse.pl
Apr 22 12:01:01 webhost1 run-parts(/etc/cron.hourly)[12011]: finished modsecparse.pl
Apr 22 12:02:01 webhost1 CROND[12051]: (root) CMD (/usr/local/bandmin/bandmin)
It does show that the cron job - find /home/magicalw/mail/domain.com/myles/cur -type f -mtime +1 -exec rm {} \; is running every five minutes.
Not sure what the next step might be?