This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I just set up an exchange 2019 server.
Sending mail does not work : email is stuck into Draft with the following message:
"Your message will be sent, but we're not quite ready, Check back in couple of minute."
After sometime the message changes for "Something went wrong and we haven't been able to send your message yet."
Sometimes, after rebooting server, the message goes to Sent Items, but is not received in recipient's mailbox.
The same issue was raised in the past your-message-will-be-sent-but-were-not-quite-ready but no diagnostic was posted.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
Does this issue also occur when sending to internal mailboxes (mailboxes hosted by Exchange server)?
If you run Get-Queue in Exchange Management Shell, would you see some messages stuck in queue?
If yes, you may try restart the Microsoft Exchange Transport service on Exchange server and see if the messages are leaving queue.
Sometimes, after rebooting server, the message goes to Sent Items, but is not received in recipient's mailbox.
Did the sender receive any NDR messages indicating the message delivery failed?
Does this issue also occur when sending to internal mailboxes (mailboxes hosted by Exchange server)?
Yes. I only tried internal mailboxes so far.
It even occurs when sending to oneself.
If you run Get-Queue in Exchange Management Shell, would you see some messages stuck in queue?
Welcome to the Exchange Management Shell!
[...]
VERBOSE: Connecting to exchange.groupe605.com.
VERBOSE: Connected to exchange.groupe605.com.
[PS] C:\Users\Administrator>get-queue
Identity DeliveryType Status MessageCount Velocity RiskLevel OutboundIPPool NextHopDomain
-------- ------------ ------ ------------ -------- --------- -------------- -------------
exchange\Submission Undefined Ready 0 0 Normal 0 Submission
I don't know how to interpret this.
Thanks for the information.
What is the DNS server setting of the NIC on your Exchange server?
The preferred DNS server should be domain controller and the alternative server should be left blank.
And since rebooting the server moves the messages to sent items, please also search the message tracking log and see if you can see the delivery process:
Get-MessageTrackingLog -sender <sender mailbox> -recipients <recipient mailbox> -messagesubject <subject>
I don't see the messages move to Sent after reboot anymore.
Below are the 3 test messages from/to user ******@groupe605.com (Test 3 to 5) but the results are different:
VERBOSE: Connected to exchange.groupe605.com.
[PS] C:\Users\Administrator> Get-MessageTrackingLog -Sender ******@groupe605.com -Recipients ******@groupe605.com -Messa
geSubject 'Test 3 (Pilar -> Pilar)'
Timestamp EventId Source Sender Recipients MessageSubject
--------- ------- ------ ------ ---------- --------------
3/19/2022 12:32:57 PM RECEIVE STOREDRIVER ******@groupe605.com {pilarp@groupe605.... Test 3 (Pilar -> P...
3/19/2022 12:32:57 PM [identical]
[output omitted]
3/19/2022 7:00:07 PM [identical]
3/19/2022 7:00:09 PM [identical]
[output omitted]
3/21/2022 1:57:58 PM [identical]
3/21/2022 1:57:59 PM [identical]
3/21/2022 1:58:00 PM [identical]
[output omitted]
3/21/2022 2:01:53 PM [identical]
3/21/2022 2:04:23 PM [identical]
3/21/2022 2:09:23 PM RECEIVE STOREDRIVER ******@groupe605.com {pilarp@groupe605.... Test 3 (Pilar -> P...
[PS] C:\Users\Administrator> Get-MessageTrackingLog -Sender ******@groupe605.com -Recipients ******@groupe605.com -MessageSubject 'Test 4 (Pilar -> Pilar)'
[PS] C:\Users\Administrator> Get-MessageTrackingLog -Sender ******@groupe605.com -Recipients ******@groupe605.com -MessageSubject 'Test 5 (Pilar -> Pilar)'
[PS] C:\Users\Administrator>
What is the current status of Microsoft Exchange Transport service?
And can you find some error or warning events generated in the event viewer>application log?
I am sorry I have overlooked your recommandation about the alternative server at first.
Removing it solved the problem. (I don't understand why but i am so relieved.)
Thank you.
Glad to hear the issue has been resolved!
I have converted my reply to an answer.
Please feel free to accept it as the answer to the question if it helped you with this issue.
Thanks for your understanding.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 57.99999999999999%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYA%3C/text%3E%3C/svg%3E)
It Worked for me; wrong DNS was the problem. Thanks Kael Yao-MSFT