none
400 4.4.7 Message delayed

    Question

  • Hi
    I am having a prob to sending mail to some domain (not all) whenever i trying to send mail to those selected domain my mails are get stucked in queue and after some time i get NDR that is 4000 4.4.7 Message delayed.
    Appreciate perfect solution.


    Thanks
    Tuesday, February 02, 2010 9:19 PM

Answers

  • I agree with James number of reasons will generate the NDR 4.4.7 

    4.4.7

    Message expired. Message wait time in queue exceeds limit, potentially due to remote server being unavailable.

    make sure the domains you are trying to sent mail too, are valid domains, they do exist. When mail server sends out mail to another SMTP domain (mail Server), in a very basic way the errors are related to either your mail server  or the destination mail servers.

    For instance if I am trying to send mail to you and , your mail server is not liking something ( My mail server is missing PTR record, or my mail server is listed in RBL ( real time block list) list, I am sending spam mails, my MX record is missing    etc.

    Mail servers will sent mail with expectation of destination mail servers are going to accept them. During this process many things might have gone wrong, might cause message to delay or never made it to destination.

    These type of issues , the destination mail server will either reject or slow down the mails. Simple telnet test can give you much better information and you will need to perform troubleshooting to figure out where the culprit is.

    Try sending mail from command line to one of these servers to see what will be the response?


    Good luck 
    ocd

    • Marked as answer by Wintel.Amit Wednesday, June 02, 2010 11:40 AM
    Thursday, February 11, 2010 4:51 AM

All replies

  • Hi Amit; this is specifically a RCA forum. You will get better responses on other forums such as the Exchange admin forum. However the Message delayed can be a number of reasons. For example if their system is down and your system cannot reach it in the retry intervals, your users will get a message delayed. Other reasons are that the target domain is greylisting you, meaning they are throttling the amount of SMTP messages you can send per interval. If you send unsolicited mail, newsletters etc you can get greylisted.
    James Chong (MVP) MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
    • Marked as answer by Wintel.Amit Tuesday, February 23, 2010 4:42 PM
    • Unmarked as answer by Wintel.Amit Wednesday, June 02, 2010 11:40 AM
    • Proposed as answer by Mark Peter van Sijll Friday, November 30, 2012 3:05 PM
    Tuesday, February 09, 2010 6:11 PM
  • I agree with James number of reasons will generate the NDR 4.4.7 

    4.4.7

    Message expired. Message wait time in queue exceeds limit, potentially due to remote server being unavailable.

    make sure the domains you are trying to sent mail too, are valid domains, they do exist. When mail server sends out mail to another SMTP domain (mail Server), in a very basic way the errors are related to either your mail server  or the destination mail servers.

    For instance if I am trying to send mail to you and , your mail server is not liking something ( My mail server is missing PTR record, or my mail server is listed in RBL ( real time block list) list, I am sending spam mails, my MX record is missing    etc.

    Mail servers will sent mail with expectation of destination mail servers are going to accept them. During this process many things might have gone wrong, might cause message to delay or never made it to destination.

    These type of issues , the destination mail server will either reject or slow down the mails. Simple telnet test can give you much better information and you will need to perform troubleshooting to figure out where the culprit is.

    Try sending mail from command line to one of these servers to see what will be the response?


    Good luck 
    ocd

    • Marked as answer by Wintel.Amit Wednesday, June 02, 2010 11:40 AM
    Thursday, February 11, 2010 4:51 AM
  • We had this situation when Cisco MailGuard was enabled on their firewall.  Mail was queued on our edge and a telnet to their smtp address returned:

    220************************************

     

    http://support.microsoft.com/default.aspx?scid=kb;en-us;320027

    Once that was resolved, email to the domain was good to go.

    Thursday, August 18, 2011 9:36 PM
  • in our case we are experiencing a similar issue but in addition to mail we aren't seeing alerts sent.  We see the form of the message or an alert in our 'badmail' folder, but the msg isn't being sent.  No changes to our environment occured at this time.  SO increasing the time might help in the email part of it but alerts should be immediate, and they're not.


    Any ideas?


    Steven David Taub

    Thursday, June 14, 2012 8:00 PM