Error 400 4.4.7 Message Delayed in Exchange 2016

Tej Pratap Shukla | Modified: August 2, 2016 | Exchange Server 2016, General Info | 3 Minutes Reading

Hello guys In this article I am going to discuss about error 400 4.4.7 Message Delayed in Exchange Server 2016. I will discuss two different type of solutions in this write up. One solution will be general, which every exchange admin must check before occurrence of error 400 4.4.7 message delay situation. And in second solution I will discuss about configuring protocol logging in exchange server.
Message delayed error is not very big deal for some Administrators. Generally they ignore it till that time when huge number of emails stuck in delivery queue. You may get below displayed message as shown in image after sending the mail. Generally this error is cause of send connector or receive connector. Therefore it is really a good practice to configure all connectors again when every solution or fixes failed.  download (6)

General Solution to Resolve Error 400 4.4.7 Message Delayed

As in general solution  follow these:

  1. Check the outbound mail can verify whether mail is going through the smarthost or not.
  2. Now check for consultants of all send connectors, whether it is configured to submit to smarthost or not. If not then configure it.
  3. After configuring you would see that the Message Delivery Queue will be empty after sometimes and all stuck messages would be delivered.

Configuring Protocol Logging in Exchange Server 2016

You should re-configure protocol logging when general solution fails. If after following above solution everything goes well then you need not to configure Protocol logging. Protocol logging can be configured using Exchange Admin Center (EAC) and Shell Commands. But in this Article I am going to describe setting up protocol logging using shell commands.

Enable or Disable Protocol Logging for Send & Receive Connector

The below command is applicable for transport service on mailbox server and edge transport server. See below mentioned commands:

  1. Run below written command for enabling protocol logging for receive connector.
    Set-RecieveConnector "serverName\connection from abc.com" -ProtoclolLoggingLevel Verbose
    Where:
    serverName is server Name.
    abc.com is connection name.
  2. Run Below command for disabling protocol logging for receive connector.
    Set-RecieveConnector "connection to internet" -ProtoclolLoggingLevel none
  3. Run below written command for enabling protocol logging for send connector.
    Set-SendConnector "serverName\connection from abc.com" -ProtoclolLoggingLevel Verbose
  4. Run below command to disable protocol logging for send connector.
    Set-SendConnector "connection to internet" -ProtoclolLoggingLevel none

Enable or Disable Protocol Logging for Intra-Organization

Intra-Organization means within an organization. Therefore by execution of below written commands, you will be enable or disable Protocol Logging within an organization. Lets see the commands:

  1. Run below command to enable logging in intra-organization
    Set-TransportService ServerName -IntraOrgConnectorProtocolLogginLevel Verbose
  2. Run below command to disable logging in itra-organization
    Set-FrontEndTransportService ServerName -IntraOrgConnectorProtocolLoggingLevel none

Check whether protocol logging is disabled or enabled by running below commands:

Run below mentioned command to check the complete report of mailbox server and edge transport server check complete report - Error 400 4.4.7

Conclusion

In this article I have discussed about resolving and fixing the error 400 4.4.7 message delayed in exchange server 2016. I have discussed the two way for fixing the error in which one was the quick fix and the other was long procedure in which I have configured protocol logging.