Test Message Sitting in SMTP Queue

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at https://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2006-07-06

The Microsoft® Exchange Server Analyzer Tool sends a test message from the Exchange server to the Postmaster account or a user-defined account for the Simple Mail Transfer Protocol (SMTP) domain and then scans the message tracking logs of the server to determine whether any issues were found with the delivery of the test message.

As a part of this scan, the Exchange Server Analyzer queries the EntryType property for the Exchange_MessageTrackingEntry Microsoft Windows® Management Instrumentation (WMI) class under the root\MicrosoftExchangeV2 namespace to determine why the message tracking log entries were created.

The following table lists the possible EntryType values returned.

Value Name Value

Message received through X400

0

Report received

2

Message submitted

4

Message transferred out

7

Report transferred out

8

Message delivered

9

Report delivered

10

Distribution list expanded

26

Message redirected

28

Message rerouted

29

Server downgraded by MTA

31

Report absorbed

33

Report generated

34

Unroutable report discarded

43

Message deleted by Administrator

50

Probe deleted by Administrator

51

Report deleted by Administrator

52

Message delivered locally

1000

Message transferred in over backbone

1001

Message transferred out over backbone

1002

Message transferred out over gateway

1003

Message transferred in over gateway

1004

Report transferred in over gateway

1005

Report transferred out over gateway

1006

Report generated

1007

SMTP: Message queued outbound

1010

SMTP: Message transferred out

1011

SMTP: Inbound message received

1012

SMTP: Inbound message transferred

1013

SMTP: Message rerouted

1014

SMTP: Report transferred in

1015

SMTP: Report transferred out

1016

SMTP: Report generated

1017

SMTP: Report absorbed

1018

SMTP: Message submitted to Advanced Queuing

1019

SMTP: Started outbound transfer of message

1020

SMTP: Message sent to badmail directory

1021

SMTP: Advanced Queue failure

1022

SMTP: Message delivered locally

1023

SMTP: Message submitted to Categorizer

1024

SMTP: Started message submission to Advanced Queue

1025

SMTP: Advanced Queue failed to deliver message

1026

SMTP Store Driver: Message submitted from Store

1027

SMTP Store Driver: Message delivered locally to Store

1028

SMTP Store Driver: Message submitted to MTA

1029

SMTP: Non-delivery report (NDR) generated

1030

SMTP: Message transferred out

1031

The Exchange Server Analyzer displays an error if the EntryType values returned indicate the following conditions are true:

  • The test message tracking log can be scanned successfully.

  • The test message did not successfully transfer out of the queue.

  • A Non Delivery Report (NDR) was not generated for the test message.

  • The test message was not transferred to the Badmail directory.

  • The test message is not queued for remote delivery.

  • The test message was not successfully delivered to the local store.

  • The test message is not scheduled to retry categorization.

  • The test message is not scheduled to retry routing.

  • The test message is not scheduled to retry local delivery.

This error means that the test message is sitting in one of the SMTP queues and additional analysis is necessary to determine the reason it is stuck there.

To resolve this error, use the NSlookup utility to review possible issues with Domain Name System (DNS) resolution. For connection and protocol issues such as Host unreachable errors, use Telnet.exe to try to connect to the destination computer. To troubleshoot protocol errors, increase diagnostic logging for the MSExchangeTransport service for the SMTP component, and review the logs for errors. Alternatively, you can use the Network Monitor (Netmon.exe) tool to obtain information about network connection errors. To reproduce the problem, you may have to force the queue to try again. Examine the event log for possible errors associated with the Microsoft Exchange Information Store service.

For more information about how to modify logging settings, see "How to Modify Logging Settings for MSExchangeTransport" in the "Troubleshooting Mail Flow and SMTP" section of the Exchange Server Transport and Routing Guide (https://go.microsoft.com/fwlink/?LinkId=47579).

For more information about how to troubleshoot SMTP queues, see the following Exchange resources: