Outbound mail queues on Exchange Hub Transport spiked to 10k+. Best way to triage the bottleneck?

OCD77 Ephelios 0 Reputation points
2026-07-16T05:58:02.6166667+00:00

Morning all.

Our outbound mail queues on the primary Exchange Hub Transport server have properly gone pear-shaped—we’ve currently got a backlog sitting at 10,000+ messages and counting.

Need to quickly isolate where the bottleneck is before things get completely choked. Could use a sanity check on how to cleanly triage this. What’s the best way to determine if we’re looking at a DNS/MX lookup failure, anti-spam agent blocking, or if we're simply getting throttled on the outbound send connectors?

Moved from: Windows for Business | Windows 365 Business

Exchange | Exchange Server | Other
Exchange | Exchange Server | Other

A robust email, calendaring, and collaboration platform developed by Microsoft, designed for enterprise-level communication and data management.Miscellaneous topics that do not fit into specific categories.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Teddie-D 19,760 Reputation points Microsoft External Staff Moderator
    2026-07-16T07:21:54.7433333+00:00

    Hi @OCD77 Ephelios

    An outbound mail queue backlog of 10,000+ messages usually requires identifying where messages are getting stuck and reviewing the queue error details first. Based on the results, you can determine whether the issue is related to DNS/MX lookup issues, remote server throttling, transport agents, Send Connector configuration, or Exchange resource constraints.

    1.Check the current queue status

    Identify the affected queue:

    Get-Queue | Sort MessageCount -Descending | ft Identity,Status,MessageCount,NextHopDomain,LastError -Auto

    Review:

    NextHopDomain

    • If most messages are going to one specific domain, the issue may be with that remote mail system.
    • If multiple external domains are affected, the issue is more likely related to your Exchange server, DNS, networking, or Send Connector.

    LastError

    • This is usually the key information to determine whether the issue is DNS, connection failure, SMTP rejection, throttling, or another transport issue.

    Reference: Queues and messages in queues in Exchange Server | Microsoft Learn

    2.If the error indicates DNS issues, test MX lookup for an affected recipient domain

    Use the domain shown in NextHopDomain:

    Resolve-DnsName <recipient-domain.com> -Type MX

    This helps confirm whether Exchange can resolve the destination mail server correctly.

    3.If the error shows temporary SMTP errors, review protocol logs

    If you see errors such as:

    • 421
    • 451
    • 4.7.x
    • connection timeout
    • TLS negotiation errors

    check SMTP protocol logs to determine whether remote servers are throttling, rejecting, or failing the connection.

    Please know that while our initial response might not resolve the issue right away, your input is incredibly valuable. With a bit more detail, we’ll work together to find the best solution for you.    

    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.  

    Was this answer helpful?

Your answer

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