Skip to main content

(Mail Queue) Mail delivery failed: returning message to sender

Comments

10 comments

  • vanessa
    Can you paste a copy of your root crontab please
    0
  • soundeluxe
    Dear @vanessa, thank you very much for your answer, can you tell me, how can i copy root crontab?
    0
  • soundeluxe
    Oh, ok, i've found, i'm on putty now and i've put "crontab -e", i think this is; 0 6 * * * /usr/local/cpanel/scripts/exim_tidydb > /dev/null 2>&1 35 * * * * /usr/bin/test -x /usr/local/cpanel/bin/tail-check && /usr/local/cpanel/bin/tail-check 45 */4 * * * /usr/bin/test -x /usr/local/cpanel/scripts/update_mailman_cache && /usr/local/cpanel/scripts/update_mailman_cache 30 */4 * * * /usr/bin/test -x /usr/local/cpanel/scripts/update_db_cache && /usr/local/cpanel/scripts/update_db_cache 45 */8 * * * /usr/bin/test -x /usr/local/cpanel/bin/optimizefs && /usr/local/cpanel/bin/optimizefs 30 */2 * * * /usr/local/cpanel/bin/mysqluserstore >/dev/null 2>&1 15 */2 * * * /usr/local/cpanel/bin/dbindex >/dev/null 2>&1 15 */6 * * * /usr/local/cpanel/scripts/recoverymgmt >/dev/null 2>&1 */5 * * * * /usr/local/cpanel/bin/dcpumon >/dev/null 2>&1 29 0 * * * /usr/local/cpanel/whostmgr/docroot/cgi/cpaddons_report.pl --notify 7,22,37,52 * * * * /usr/local/cpanel/whostmgr/bin/dnsqueue > /dev/null 2>&1 15 */6 * * * /usr/local/cpanel/scripts/autorepair recoverymgmt >/dev/null 2>&1 30 5 * * * /usr/local/cpanel/scripts/optimize_eximstats > /dev/null 2>&1 */5 * * * * root sh -c "sync; echo 3 > /proc/sys/vm/drop_caches" 0 4 * * * /usr/local/cpanel/scripts/upcp --cron 0 7 * * * /usr/local/cpanel/scripts/cpbackup 2,58 * * * * /usr/local/bandmin/bandmin 0 0 * * * /usr/local/bandmin/ipaddrmap 0 2 * * * /usr/local/cpanel/bin/backup
    0
  • cPanelMichael
    Hello :) The subject of the bounced email you provided shows: [QUOTE]Subject: Cron root sh -c "sync; echo 3 > /proc/sys/vm/drop_caches"
    This matches with the following cron job you have enabled: [QUOTE]*/5 * * * * root sh -c "sync; echo 3 > /proc/sys/vm/drop_caches"
    Did you setup this cron job on your own? It's not a standard cron job included with cPanel. Thank you.
    0
  • vanessa
    You need to remove the user section of the cron job, because the user is already implied by the fact that its in the root crontab. It should look like this: */5 * * * * sh -c "sync; echo 3 > /proc/sys/vm/drop_caches"
    0
  • soundeluxe
    Dear @cPanelMichael, actually, i did not setup this cron, just my old server same use cpanel, my datacenter just make migrate old server to new server, they are setup first cpanel, after they are migrate. How can i fix it? I'm really still really new on cPanel :) [quote="cPanelMichael, post: 1687202">Hello :) The subject of the bounced email you provided shows: This matches with the following cron job you have enabled: Did you setup this cron job on your own? It's not a standard cron job included with cPanel. Thank you.
    0
  • soundeluxe
    Dear @vanessa, thank you very much again, how can i delete this one? After delete is that return everything normal? If i delete this one, fix it? [quote="vanessa, post: 1687231">You need to remove the user section of the cron job, because the user is already implied by the fact that its in the root crontab. It should look like this: */5 * * * * sh -c "sync; echo 3 > /proc/sys/vm/drop_caches"

    0
  • vanessa
    Simply edit the crontab (crontab -e) and remove the line. This will stop the error from occurring and stop related emails from being sent to you.
    0
  • soundeluxe
    Thank you very much, i've deleted that line but i'm still gettin error, what happened i dont understand. Now, i see on queue manager too much that mail; This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: root@sunucu.dijitalada.net The mail server could not deliver mail to root@sunucu.dijitalada.net. The account or domain may not exist, they may be blacklisted, or missing the proper dns entries. ------ This is a copy of the message, including all the headers. ------ Return-path: Received: from root by sunucu.dijitalada.net with local (Exim 4.82) (envelope-from ) id 1X7gIM-0000bG-Ig for root@sunucu.dijitalada.net; Thu, 17 Jul 2014 10:40:03 +0300 From: root@sunucu.dijitalada.net (Cron Daemon) To: root@sunucu.dijitalada.net Subject: Cron /usr/local/cpanel/bin/dcpumon >/dev/null 2>&1 Content-Type: text/plain; charset=UTF-8 Auto-Submitted: auto-generated X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: Message-Id: Date: Thu, 17 Jul 2014 10:40:02 +0300 /bin/sh: 1 : ambiguous redirect
    And its my new cron file; 0 6 * * * /usr/local/cpanel/scripts/exim_tidydb > /dev/null 2>&1 35 * * * * /usr/bin/test -x /usr/local/cpanel/bin/tail-check && /usr/local/cpanel/bin/tail-check 45 */4 * * * /usr/bin/test -x /usr/local/cpanel/scripts/update_mailman_cache && /usr/local/cpanel/scripts/update_mailman_cache 30 */4 * * * /usr/bin/test -x /usr/local/cpanel/scripts/update_db_cache && /usr/local/cpanel/scripts/update_db_cache 45 */8 * * * /usr/bin/test -x /usr/local/cpanel/bin/optimizefs && /usr/local/cpanel/bin/optimizefs 30 */2 * * * /usr/local/cpanel/bin/mysqluserstore >/dev/null 2>&1 15 */2 * * * /usr/local/cpanel/bin/dbindex >/dev/null 2>&1 15 */6 * * * /usr/local/cpanel/scripts/recoverymgmt >/dev/null 2>&1 */5 * * * * /usr/local/cpanel/bin/dcpumon >/dev/null 2>&1 29 0 * * * /usr/local/cpanel/whostmgr/docroot/cgi/cpaddons_report.pl --notify 7,22,37,52 * * * * /usr/local/cpanel/whostmgr/bin/dnsqueue > /dev/null 2>&1 15 */6 * * * /usr/local/cpanel/scripts/autorepair recoverymgmt >/dev/null 2>&1 30 5 * * * /usr/local/cpanel/scripts/optimize_eximstats > /dev/null 2>&1 0 4 * * * /usr/local/cpanel/scripts/upcp --cron 0 7 * * * /usr/local/cpanel/scripts/cpbackup 2,58 * * * * /usr/local/bandmin/bandmin 0 0 * * * /usr/local/bandmin/ipaddrmap 0 2 * * * /usr/local/cpanel/bin/backup
    0
  • vanessa
    You left something in place, as it clearly shows in the bounce message: /bin/sh: 1
    Make sure you restart crond. Using the 'crontab -r' command usually reloads it but maybe there was an error.
    0

Please sign in to leave a comment.