Exchange 2019: message defered

Mikhail Firsov 1,881 Reputation points
2020-09-03T16:03:44.267+00:00

Hello,

After installing a new Exchange Server 2019 I tried to send the first message in Outlook 2019 from admin@... to @Arjun ... The result: the message has been sent but never arrived at admin's Inbox:

![22571-02.png][1]
![22454-01.png][2]

According to the Message Tracking Logs it has been defered:
![22455-05.png][1]

The question: what can I do to find out what has caused this delay?

Thank you in advance,
Michael

Exchange | Exchange Server | Management
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Joyce Shen - MSFT 16,701 Reputation points
    2020-09-04T02:44:31.297+00:00

    Hi @Mikhail Firsov , whether the mail has been delivered successfully now?

    Since it's the newly installed Exchange server, it may take some time to prepare the configuration which may lead to the submitdefer of the message.

    In addition, please check if the Mailbox Transport Submission service and Transport service are running properly on your server.
    And verify if the disk is almost full. If yes, free some space and then check the result.
    You could check if there is any event logs of Back Pressure which will lead to the message delay as well. Like eventid 15004,15006,15007...

    Last, you could also check the mails in queue, retry the delayed or failed items.


    If an Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Mikhail Firsov 1,881 Reputation points
    2020-09-04T09:01:39.04+00:00

    Hi joyceshen-MSFT,

    Thank you for the reply!

    Today (one day later) I checked the Inbox and the logs once again - the message still "defered". Since it's the new installation and it's not even "connected" to the Internet I can rule out the back pressure completely (of course I've checked the logs for the Back Pressure-related events). All Exchange services are running and I failed to find any error in the Application, System and Exchange-specific logs that could indicate the source of the problem, so it just doesn't work.

    After sending the second test message I checked the Delivery Reports once again and this time there was the error:

    22687-e3-1.png

    Restarting the server leads to 5 Exchange services stopped - they won't start until I have started them manually - rather strange :((( I've been using exactly this test server for many Exchange installations (2013, 2016, 2019) and this is the first time Exchange just does not work after successfull installation. This time I have installed Exchange Server 2019 CU6 Enterprise... maybe there were any bugs in this version or my hardware is not good for it???


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.