This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(144, 95%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJH%3C/text%3E%3C/svg%3E)
Good morning,
I have an Exchange environment with an Edge Transport server running 2019 and two Mailbox servers running 2016 CU21 that are both part of a DAG. The DAG was a new install and mailflow was functioning correctly for about 3-4 days, but then mail has started not delivering intermittently. I did notice that one of the queues on the new Mailbox server for Submission has over 13,000 emails in it.
I have tried to make sure the licensing is correct and the receive connectors are correct, but the issue persists.
Any help would be greatly appreciated.
![](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 occur after you install the new mailbox server into the environment?
Can you find some error or warning events logged in the event viewer>application log on the new Mailbox server?
For example, event 15004-15007.
If any, it may indicates the server is having back pressure problems.
Please also try restarting the Microsoft Exchange Transport service on the new Mailbox server and see if the messages would leave the queue.
If the response 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.
II have tried a few times to restart the Transport service. I see that the messages are indictating deferred by categorized agent.
Hi,
Thanks for the update.
I suppose it may be caused by back pressure.
Please have a check if there are related events in the application log.
The issue was the Malware Agent on the new mailbox server. Once that Transport Agent was disabled and the Transport service was restarted, mail started to flow out of the backlogged queue.
Glad to hear the issue has been resolved.
Thanks for the sharing.
Please feel free to mark your reply as the answer to the question.
It would be helpful to other community members.
Thanks for your understanding.
If the issue has been resolved, please feel free to mark your reply as the answer to the question.
It will highlight the answer and be helpful to other community members.
Thanks for your sharing.