XADM: Message Tracking Event IDs and Description (246959)



The information in this article applies to:

  • Microsoft Exchange 2000 Server

This article was previously published under Q246959

SUMMARY

You can enable message tracking logs to troubleshoot the flow or status of a message in Microsoft Exchange 2000 Server. The logs that are generated have a column labeled Event-ID, which provides information on the action taken on the message such as sent, received, delete, retrieve. The table in the "More Information" section presents a complete list of the Event IDs used in Exchange 2000, with descriptions. Every attempt has been made to match these events to Microsoft Exchange Server 5.5 events.

MORE INFORMATION

Event numberEvent typeDescriptionComments
0Message transfer inThe message transfer agent (MTA) received a message from a server, connector, or gateway.
1Probe transfer in The MTA received an X.400 probe from a server, connector, or gateway.
2Report transfer inA delivery receipt or non-delivery report (NDR) was received from a server, connector, or gateway.
4Message submissionA local e-mail client submitted a message (through the information store).
5Probe submission A local e-mail client submitted an X.400 probe (usually through the information store).
6Probe transfer out The MTA completed transfer of an X.400 probe to a gateway, X.400 link, or another MTA.
7Message transfer outThe MTA sent the message to a server, connector, or gateway.
8Report transfer outThe MTA sent the delivery receipt or NDR to a server, connector, or gateway.
9 Message deliveredThe message was delivered to a mailbox or public folder.
10Report deliveredA delivery receipt or NDR was delivered to a mailbox.
26 Distribution list expansionA recipient distribution list was expanded so that the message can be sent to different addresses.
28Message redirectedThe message was sent to a mailbox other than that of the recipient.
29Message reroutedThe message was routed to an alternate path.
31DowngradingThe MTA has mapped a message, report, or probe into the 1984 X.400 protocol before transferring it to a remote 1984 MTA.
33Report absorptionThe MTA has scheduled a report for deletion because the user did not request it. In the X.400 protocol, NDRs are always routed back to the sending MTA even if the user did not request a report.
34Report generationA delivery receipt or NDR has been created.
43Unroutable report discardedThe MTA has discarded a report because the report cannot be routed to its destination.
50Gateway deleted messageThe administrator deleted an X.400 message that was queued by the MTA for transfer to a gateway. No delivery report is generated.
51Gateway deleted probeThe administrator deleted an X.400 probe that was queued by the MTA for transfer to a gateway. No delivery report is generated.
52Gateway deleted reportThe administrator deleted an X.400 report that was queued by the MTA for transfer to a gateway. No delivery report is generated.
1000Local deliveryThe sender and recipient are on the same server.
1001Backbone transfer inMail was received from another Messaging Application Programming Interface (MAPI) system across a connector or gateway.
1002Backbone transfer outMail was sent to another MAPI system across a connector or gateway.
1003Gateway transfer outThe message was sent through a gateway.
1004Gateway transfer inThe message was received from a gateway.
1005Gateway report transfer inA delivery receipt or NDR was received from a gateway.
1006Gateway report transfer outA delivery receipt or NDR was sent through a gateway.
1007Gateway report generationA gateway generated an NDR for a message.
1010SMTP queued outbound
1011SMTP transferred outboundOutbound mail was transferred to an Internet recipient.
1012SMTP received inboundInbound mail was received from the SMTP connector.
1013SMTP transferred inbound
1014SMTP message reroutedAn Internet message was rerouted or forwarded to the proper location.
1015SMTP report transferred inThe SMTP connector received a delivery receipt or NDR.
1016SMTP report transferred outA delivery receipt or NDR was sent to the SMTP connector.
1017SMTP report generatedA delivery receipt or NDR was created.
1018SMTP report absorbedThe receipt or NDR could not be delivered.
1019SMTP submitted message to advanced queuingFor use by SMTP transport.
1020SMTP outbound transfer For use by SMTP transport.
1021SMTP bad mailFor use by SMTP transport.
1022SMTP advanced queuing failureFor use by SMTP transport.
1023SMTP local deliveryFor use by SMTP transport.
1024SMTP submit message to categorizerFor use by SMTP transport.
1025SMTP begin submit messageFor use by SMTP transport.
1026SMTP advanced queuing failed messageFor use by SMTP transport.
1027SMTP submit message to store driverThe information store driver has picked up a message from the information store.
1028SMTP store driver local deliveryThe information store driver has delivered a message to the information store for local delivery.
1029SMTP store driver gateway deliveryThe information store driver has delivered a message to the information store for gateway delivery.
1030SMTP NDR allFor use by SMTP transport.
1031SMTP end outbound transferFor use by SMTP transport.

Modification Type:MinorLast Reviewed:4/25/2005
Keywords:kbinfo KB246959