Interactive Troubleshooter

Published: Sep 1, 2026

Updated: Sep 1, 2026

Exchange Server Email Queue Stuck: Fix Guide

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

An interactive root-cause diagnostic tree to systematically isolate and resolve stuck email queues on Microsoft Exchange Server. Identify transport backpressure resource limits, Send Connector DNS/TLS failures, Transport Agent deadlocks, and ESE mail.que database corruption.

Full Diagnostic Tree & Step-by-Step Overview

What specific queue behavior or queue status error are you observing in Exchange Management Shell or Queue Viewer?

Queues show high message count with 'Retry' status, or report resource throttling / backpressure
Transport service hangs, mail flow is totally frozen across submission/delivery, or high CPU on MSExchangeTransport
Corrupted mail.que database error (ESE JET failure) or messages stuck in the Poison Queue

What underlying bottleneck is causing messages to accumulate in 'Retry' status?

Exchange logs Event 15004/15005 (Backpressure) due to low disk space on queue drive or high RAM usage
Messages accumulate in outbound Send Connector queue with DNS lookup or TLS handshake timeout errors

Resolve Exchange Transport Backpressure and Clear Queue Storage Throttling

Solution:

Root Cause: Transport Resource Throttling (Backpressure Triggered)

Microsoft Exchange Transport incorporates a built-in protective monitoring mechanism called 'Backpressure'. When available free disk space on the volume hosting mail.que drops below the safety threshold (typically less than 2% to 4% free space) or physical RAM utilization spikes above 94%, Exchange rejects incoming SMTP connections and pauses message processing from queues.

# Step-by-Step Fix:

Check Current Backpressure State via Exchange Management Shell (EMS):

Open EMS and run the following command to audit resource pressure:

powershell
   Get-ExchangeServer -Identity $env:COMPUTERNAME | Format-List *Backpressure*

Inspect Windows Event Viewer under Applications and Services Logs > MSExchangeManagement for Event ID 15004 or 15005.

Free Up Disk Space on the Queue Volume:

Delete or archive historical diagnostic logs located in:

C:\Program Files\Microsoft\Exchange Server\V15\Logging\MessageTracking
C:\Program Files\Microsoft\Exchange Server\V15\Logging\ETL

Relocate Mail Queue Database (If Drive Space Cannot Be Expanded):

Use the included Exchange script to move mail.que to a larger partition:

powershell
   & '$env:ExchangeInstallPath\Scripts\Move-TransportDatabase.ps1' -QueueDatabasePath 'D:\ExchangeQueue\mail.que' -QueueDatabaseLoggingPath 'D:\ExchangeQueue\Logs'

Restart MSExchangeTransport Service:

Apply configuration changes and resume normal transport pipeline processing:

powershell
   Restart-Service MSExchangeTransport

Fix Send Connector DNS Resolution and Verify TLS Certificate Assignment

Solution:

Root Cause: Outbound DNS Resolution Failure or Expired TLS Certificate on Send Connector

Outbound messages remain in the unreachable or specific domain delivery queue when Exchange cannot resolve destination MX records via configured network adapters, or when a TLS handshake fails due to an expired, untrusted, or unassigned TLS certificate on the Send Connector.

# Step-by-Step Fix:

Inspect Stuck Queue Error Details:

Query the specific queue status in Exchange Management Shell:

powershell
   Get-Queue -Filter "Status -eq 'Retry'" | Get-Message -ResultSize Unlimited | Format-Table Identity, Subject, Status, LastError

Verify DNS Lookups for External Routing:

Test MX record lookup directly from the Exchange server:

powershell
   Resolve-DnsName -Name remote-domain.com -Type MX

If using custom network adapter DNS settings on Send Connectors, check configuration via Get-TransportService -Identity $env:COMPUTERNAME | Format-List ExternalDNS*.

Validate TLS Certificate Bound to SMTP Service:

List installed certificates and verify the SMTP service is bound:

powershell
   Get-ExchangeCertificate | Format-Table Subject, Thumbprint, Services, NotAfter

Re-assign SMTP service to a valid certificate if expired:

powershell
   Enable-ExchangeCertificate -Thumbprint <VALID_THUMBPRINT> -Services SMTP

Retry Delivery Queue Manually:

Force immediate retry on stuck connector queues:

powershell
   Retry-Queue -Identity "Unreachable" -Resubmit $true

What type of service hang or agent pipeline lockup are you experiencing?

MSExchangeTransport service is stuck in 'Stopping'/'Starting' state or crashing repeatedly
Custom or third-party Transport Agents (Antivirus, DLP, Disclaimers) causing pipeline deadlocks

Force Kill Hung MSExchangeTransport Process and Reset Transport Submission Pipeline

Solution:

Root Cause: MSExchangeTransport Thread Deadlock or Unhandled Exception Crash

The Transport service can enter an unresponsive state when underlying RPC threads deadlock between the Mailbox Transport Delivery service and the Hub Transport pipeline. In this state, the service cannot be gracefully stopped or started via standard Service Control Manager calls.

# Step-by-Step Fix:

Identify PID and Force Kill Hung Service Process:

Open Command Prompt as Administrator and terminate the stuck process:

cmd
   taskkill /F /FI "SERVICES eq MSExchangeTransport"

Reset Associated Mailbox Transport Services:

Restart both delivery and submission helpers to clear pipeline deadlocks:

powershell
   Restart-Service MSExchangeDelivery
   Restart-Service MSExchangeSubmission
   Restart-Service MSExchangeTransport

Verify TCP Port 25 Bindings:

Ensure no third-party software (e.g., antivirus mail proxy) has hijacked SMTP Port 25:

cmd
   netstat -ano | findstr :25

Check Queue Processing Flow:

Run Get-Queue in EMS to confirm that active message delivery has resumed.

Disable Malfunctioning Transport Agents and Audit Event Log Exceptions

Solution:

Root Cause: Third-Party Transport Agent Crash or Unhandled Exception in Pipeline

Exchange evaluates messages through registered Transport Agents (e.g., Antivirus scanners, DLP filters, signature append tools). If an agent throws an unhandled exception during the OnEndOfData or OnSubmittedMessage events, the Transport engine halts pipeline processing, causing queues to fill indefinitely.

# Step-by-Step Fix:

List Installed Transport Agents:

Display all registered agents and their current execution status:

powershell
   Get-TransportAgent

Identify Failing Agent via Application Event Log:

Look for Event ID 1051 or 16023 in Application Logs detailing agent failure stack traces.

Disable Suspect Transport Agent:

Temporarily disable the third-party agent to bypass pipeline evaluation:

powershell
   Disable-TransportAgent -Identity "FailingAgentName"

Restart Transport Service to Flush Agent Context:

powershell
   Restart-Service MSExchangeTransport

Monitor Queue Recovery:

Verify messages clear out of active queues. Re-enable or update the agent once a vendor patch is applied.

What type of database failure or corrupted message queue state are you handling?

Corrupted mail.que ESE JET database file (Event ID 400 validation error / 454 ESE error)
Malformed or corrupted messages isolated inside the Exchange Poison Queue

Rebuild Corrupted mail.que Extensible Storage Engine (ESE) Database

Solution:

Root Cause: Extensible Storage Engine (ESE) Queue Database Corruption

The Exchange queue database (mail.que) is an ESE database file. Physical disk bad sectors, ungraceful server shutdowns, or storage drops can corrupt mail.que or its transaction log files (trn.log), preventing the MSExchangeTransport service from starting or mounting the queue.

# Step-by-Step Fix:

Stop MSExchangeTransport Service:

powershell
   Stop-Service MSExchangeTransport

Locate Queue Database Directory:

Navigate to the default queue path:

C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue

Rename Corrupted Queue Folder:

Rename the Queue folder to Queue.old (this preserves old queue data for potential recovery via ESEUTIL repair if required):

cmd
   ren "C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue" Queue.old

Restart MSExchangeTransport Service to Recreate Database:

Restarting the service automatically builds a brand-new, healthy mail.que file and clean transaction logs:

powershell
   Start-Service MSExchangeTransport

Verify New Queue Creation:

Confirm a new Queue directory has been generated and Get-Queue returns a healthy Ready state.

Inspect, Export, and Purge Messages from the Exchange Poison Queue

Solution:

Root Cause: Malformed Message Content Triggering Poison Queue Isolation

When a specific email contains corrupt MIME headers, malformed attachment structures, or payload data that crashes the transport worker process repeatedly (typically 3 crashes), Exchange flags the item as 'poison' and moves it into the isolated Poison Queue to prevent complete mail flow breakdown.

# Step-by-Step Fix:

Query Poison Queue Contents:

Inspect isolated messages in EMS:

powershell
   Get-Queue -Identity Poison | Get-Message

Export Suspect Message for Forensic Inspection (Optional):

Suspend message and export to .eml format:

powershell
   Suspend-Message -Identity "Poison\<MessageID>"
   Export-Message -Identity "Poison\<MessageID>" | AssembleMessage -Path "C:\PoisonMessages\corrupt_msg.eml"

Delete Poison Message Without Sending Non-Delivery Report (NDR):

Purge the offending message to ensure it cannot re-enter and disrupt the pipeline:

powershell
   Remove-Message -Identity "Poison\<MessageID>" -WithNDR $false

Resume Transport Pipeline Processing:

Verify no remaining items exist in the Poison Queue using Get-Queue -Identity Poison.

Related Diagnostic Guides

Google Account Suspicious Activity? How to Check for Unknown Devices

Microsoft Account Hacked? How to Recover and Secure Your Account

Fast Charging Not Working? How to Check USB PD and Quick Charge Support

Laptop Using Integrated Graphics Instead of Dedicated GPU? Here's How to Fix It

Google Family Link Not Blocking Apps? Here's How to Fix It

Subscribe to StepDiag

Embed Guide on Your Website