The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

no immediate delivery: load average xx

Discussion in 'E-mail Discussions' started by webstyler, May 15, 2013.

  1. webstyler

    webstyler Well-Known Member

    Joined:
    Nov 20, 2003
    Messages:
    432
    Likes Received:
    0
    Trophy Points:
    16
    Hello

    customer send email but delivery delayed for more than 3 hours ..

    2013-05-11 17:03:01 1Ubuh1-0004dK-1F <= xx
    2013-05-11 17:03:01 1Ubuh1-0004dK-1F no immediate delivery: load average 12.74
    2013-05-11 20:33:50 1Ubuh1-0004dK-1F SMTP connection outbound xx
    2013-05-11 20:33:51 1Ubuh1-0004dK-1F => xx R=lookuphost T=remote_smtp H=xx
    2013-05-11 20:33:51 1Ubuh1-0004dK-1F Completed

    Possible to set retry rules for re-send with less waiting time ??

    Thanks
     
  2. Veeble-Adam

    Veeble-Adam Active Member

    Joined:
    May 7, 2013
    Messages:
    43
    Likes Received:
    0
    Trophy Points:
    6
    cPanel Access Level:
    Root Administrator
  3. webstyler

    webstyler Well-Known Member

    Joined:
    Nov 20, 2003
    Messages:
    432
    Likes Received:
    0
    Trophy Points:
    16
    Yes

    the question is how to set retry rule for this to force to retry after x minutes and not after more than 3 hours ?

    I know how to work with retry rules, but not found this specify error ()
     
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,694
    Likes Received:
    654
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    The primary issue I see is this notice:

    Code:
    no immediate delivery: load average 12.74
    This indicates delivery is not possible because your server load is higher than the configured load threshold defined in the /etc/exim.conf file. You can find that value via:

    Code:
    # grep queue_only_load /etc/exim.conf 
    You will need to increase this value via the "Advanced Editor" tab of "WHM Home » Service Configuration » Exim Configuration Manager", or reduce the load on the server to allow for delivery.

    Thank you.
     
  5. webstyler

    webstyler Well-Known Member

    Joined:
    Nov 20, 2003
    Messages:
    432
    Likes Received:
    0
    Trophy Points:
    16
    Hello Michael

    yes, but in our scenario server has been "overloaded" only for a few minutes while the delivery was delayed for hours

    so, we would like to settings the retry rules for this any x minutes and not any 4/5 hours :)

    Thanks
     
  6. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,694
    Likes Received:
    654
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    By default, Exim specifies retries every 15 minutes for 2 hours, then increasing retry intervals, starting at 1 hour and increasing each time by a factor of 1.5, up to 16 hours, then retries every 8 hours until 4 days have passed since the first failed delivery. This is documented at:

    32. Retry configuration

    You can edit these rules via the "Advanced Editor" in "WHM Home » Service Configuration » Exim Configuration Manager". The section is titled:

    "Section: RETRYBLOCK"

    Thank you.
     
  7. webstyler

    webstyler Well-Known Member

    Joined:
    Nov 20, 2003
    Messages:
    432
    Likes Received:
    0
    Trophy Points:
    16
    Hi Michael

    ok, but you known what is the specified rule for this ?

    example : for quota I can set

    * quota F,1h,15m; G,2d,1h,2;

    but what for delivered delay / load average ? there is error defined ?

    Thanks
     
  8. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,694
    Likes Received:
    654
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    These messages are placed in the queue and the standard retry rules apply. I'm not aware of a method to implement custom retry rules for these specific types of messages.

    Thank you.
     
Loading...

Share This Page