15 October 2025, 07:48 PM
I ran into a strange issue with our Exchange Server 2019 setup today. Mail flow has suddenly stopped messages are getting stuck in the transport queue, but none are actually being delivered to the recipients.
I checked the Microsoft Exchange Transport service, and it’s running fine. Restarted it just to be sure, but no luck. Event Viewer shows repeated warnings about message routing delays, possibly due to a DNS resolution issue.
I verified the connectors, certificates, and even the accepted domain settings (followed this guide on configuring accepted domains in Exchange 2016), and everything seems okay.
Could this be related to a database issue? One of the mailbox stores was recently repaired using EseUtil, so I’m starting to wonder if there’s a deeper corruption or indexing problem.
If anyone has faced a situation where queues fill up but mail never routes, I’d appreciate any insight. Should I try clearing the transport queue database or rebuild the transport service configuration?
Thanks in advance for any advice I’m hoping to avoid another full database repair if possible.
I checked the Microsoft Exchange Transport service, and it’s running fine. Restarted it just to be sure, but no luck. Event Viewer shows repeated warnings about message routing delays, possibly due to a DNS resolution issue.
I verified the connectors, certificates, and even the accepted domain settings (followed this guide on configuring accepted domains in Exchange 2016), and everything seems okay.
Could this be related to a database issue? One of the mailbox stores was recently repaired using EseUtil, so I’m starting to wonder if there’s a deeper corruption or indexing problem.
If anyone has faced a situation where queues fill up but mail never routes, I’d appreciate any insight. Should I try clearing the transport queue database or rebuild the transport service configuration?
Thanks in advance for any advice I’m hoping to avoid another full database repair if possible.