Article ID: 246959
Article Last Modified on 2/27/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
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 number | Event type | Description | Comments |
---|---|---|---|
0 | Message transfer in | The message transfer agent (MTA) received a message from a server, connector, or gateway. | |
1 | Probe transfer in | The MTA received an X.400 probe from a server, connector, or gateway. | |
2 | Report transfer in | A delivery receipt or non-delivery report (NDR) was received from a server, connector, or gateway. | |
4 | Message submission | A local e-mail client submitted a message (through the information store). | |
5 | Probe submission | A local e-mail client submitted an X.400 probe (usually through the information store). | |
6 | Probe transfer out | The MTA completed transfer of an X.400 probe to a gateway, X.400 link, or another MTA. | |
7 | Message transfer out | The MTA sent the message to a server, connector, or gateway. | |
8 | Report transfer out | The MTA sent the delivery receipt or NDR to a server, connector, or gateway. | |
9 | Message delivered | The message was delivered to a mailbox or public folder. | |
10 | Report delivered | A delivery receipt or NDR was delivered to a mailbox. | |
26 | Distribution list expansion | A recipient distribution list was expanded so that the message can be sent to different addresses. | |
28 | Message redirected | The message was sent to a mailbox other than that of the recipient. | |
29 | Message rerouted | The message was routed to an alternate path. | |
31 | Downgrading | The MTA has mapped a message, report, or probe into the 1984 X.400 protocol before transferring it to a remote 1984 MTA. | |
33 | Report absorption | The 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. | |
34 | Report generation | A delivery receipt or NDR has been created. | |
43 | Unroutable report discarded | The MTA has discarded a report because the report cannot be routed to its destination. | |
50 | Gateway deleted message | The administrator deleted an X.400 message that was queued by the MTA for transfer to a gateway. No delivery report is generated. | |
51 | Gateway deleted probe | The administrator deleted an X.400 probe that was queued by the MTA for transfer to a gateway. No delivery report is generated. | |
52 | Gateway deleted report | The administrator deleted an X.400 report that was queued by the MTA for transfer to a gateway. No delivery report is generated. | |
1000 | Local delivery | The sender and recipient are on the same server. | |
1001 | Backbone transfer in | Mail was received from another Messaging Application Programming Interface (MAPI) system across a connector or gateway. | |
1002 | Backbone transfer out | Mail was sent to another MAPI system across a connector or gateway. | |
1003 | Gateway transfer out | The message was sent through a gateway. | |
1004 | Gateway transfer in | The message was received from a gateway. | |
1005 | Gateway report transfer in | A delivery receipt or NDR was received from a gateway. | |
1006 | Gateway report transfer out | A delivery receipt or NDR was sent through a gateway. | |
1007 | Gateway report generation | A gateway generated an NDR for a message. | |
1010 | SMTP queued outbound | ||
1011 | SMTP transferred outbound | Outbound mail was transferred to an Internet recipient. | |
1012 | SMTP received inbound | Inbound mail was received from the SMTP connector. | |
1013 | SMTP transferred inbound | ||
1014 | SMTP message rerouted | An Internet message was rerouted or forwarded to the proper location. | |
1015 | SMTP report transferred in | The SMTP connector received a delivery receipt or NDR. | |
1016 | SMTP report transferred out | A delivery receipt or NDR was sent to the SMTP connector. | |
1017 | SMTP report generated | A delivery receipt or NDR was created. | |
1018 | SMTP report absorbed | The receipt or NDR could not be delivered. | |
1019 | SMTP submitted message to advanced queuing | For use by SMTP transport. | |
1020 | SMTP outbound transfer | For use by SMTP transport. | |
1021 | SMTP bad mail | For use by SMTP transport. | |
1022 | SMTP advanced queuing failure | For use by SMTP transport. | |
1023 | SMTP local delivery | For use by SMTP transport. | |
1024 | SMTP submit message to categorizer | For use by SMTP transport. | |
1025 | SMTP begin submit message | For use by SMTP transport. | |
1026 | SMTP advanced queuing failed message | For use by SMTP transport. | |
1027 | SMTP submit message to store driver | The information store driver has picked up a message from the information store. | |
1028 | SMTP store driver local delivery | The information store driver has delivered a message to the information store for local delivery. | |
1029 | SMTP store driver gateway delivery | The information store driver has delivered a message to the information store for gateway delivery. | |
1030 | SMTP NDR all | For use by SMTP transport. | |
1031 | SMTP end outbound transfer | For use by SMTP transport. |
Keywords: kbinfo KB246959