Servers that are upgraded to version 58 will find out that the cronjob for mailman has been erased. This will break the sending out of digests.
When I discovered this, I re-added the cronjob using the script at ../mailman/cron/crontab.in. However this is not working either. The cronjob is running according to /var/log/cron but digests are not being sent out. I then noticed there is a difference in the command line for the cron entry that handles the sending out of digests:
New:
0 12 * * * mailman /usr/local/cpanel/scripts/restartsrv_mailman --status &> /dev/null && /usr/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/senddigests
Previous:
0 12 * * * /usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/senddigests
Can someone else confirm this and can I get cPanel to look into this? The fact that the original cronjob was erased after the upgrade is problematic and has caused me a big headache! Not very good quality control if you ask me.
When I discovered this, I re-added the cronjob using the script at ../mailman/cron/crontab.in. However this is not working either. The cronjob is running according to /var/log/cron but digests are not being sent out. I then noticed there is a difference in the command line for the cron entry that handles the sending out of digests:
New:
0 12 * * * mailman /usr/local/cpanel/scripts/restartsrv_mailman --status &> /dev/null && /usr/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/senddigests
Previous:
0 12 * * * /usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/senddigests
Can someone else confirm this and can I get cPanel to look into this? The fact that the original cronjob was erased after the upgrade is problematic and has caused me a big headache! Not very good quality control if you ask me.