FAQs / Exchange 2003 / Tracking Log EventIDs
01
EventID
Title
Description
0 Message transfer in The MTA completed transfer of responsibility for a message from a gateway, X.400 link, or other MTA into the local MTA. 1 Probe transfer in The MTA completed transfer of responsibility for a probe from a gateway, X.400 link, or other MTA into the local MTA. 2 Report transfer in The MTA completed transfer of responsibility for a report from a gateway, X.400 link, or other MTA into the local MTA. 4 Message submission A message was submitted by a local e-mail client (usually through the Information Store/MDB). 5 Probe submission An X.400 probe was submitted by a local e-mail client (usually through the Information Store). 6 Probe transfer out The MTA completed transfer of responsibility for a probe from the local MTA to a gateway, X.400 link, or another MTA. 7 Message transfer out The MTA completed transfer of responsibility for a message from the local MTA to a gateway, X.400 link, or another MTA. 8 Report transfer out The MTA completed transfer of responsibility for a report from the local MTA to a gateway, X.400 link, or another MTA. 9 Message delivered The MTA completed delivery of a message to local recipients (usually through the Information Store). 10 Report delivered The MTA completed delivery of a receipt or NDR to local recipients (usually through the Information Store). 26 Distribution list expansion The MTA has expanded a distribution list to produce a new message that has recipients who are distribution list members. 28 Message redirected The MTA has redirected a message or probe to an alternate recipient because of incorrect configuration data for the original recipient, or failure to route the object or reassignment of data contained in the message. 29 Message rerouted The MTA has rerouted a message, report, or probe because of problems with next route X.400 link or MTA. 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 X.400 protocol, NDRs are always routed back to the sending MTA even if the user did not request a report. 34 Report generation The MTA has created a delivery receipt or NDR. 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 Outbound mail was queued for delivery by the Internet Mail Service. 1011 SMTP transferred outbound Outbound mail was transferred to an Internet recipient. 1012 SMTP received inbound Inbound mail was received by the Internet Mail Service. 1013 SMTP transferred inbound Mail received by the Internet Mail Service was transferred to the Information Store. 1014 SMTP message rerouted An Internet message is being rerouted or forwarded to the proper location. 1015 SMTP report transferred in A delivery receipt or NDR was received by the Internet Mail Service. 1016 SMTP report transferred out A delivery receipt or NDR was sent to the Internet Mail Service. 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 submit message to AQ A new message is submitted to Advanced Queuing. 1020 SMTP begin outbound transfer A message is about to be sent over the wire by SMTP. 1021 SMTP bad mail The message was transferred to the badmail directory. 1022 SMTP AQ failure A fatal Advanced Queuing error occurred. Information about the failure is written to the Event Manager. 1023 SMTP local delivery A message was successfully delivered by a store drive (logged by Advanced Queue). 1024 SMTP submit message to cat Advanced Queuing submitted a message to the categorizer. 1025 SMTP begin submit message A new message is submitted to Advanced Queuing. 1026 SMTP AQ failed message Advanced Queuing could not process the message. The message will be NDRed or put into badmail. 1027 SMTP submit message to SD A message was submitted to the store driver by the MTA. 1028 SMTP SD local delivery Store driver successfully delivered a message (logged by store driver). 1029 SMTP SD gateway delivery Store driver transferred the message to the MTA. 1030 SMTP NDR all All recipients were NDRed. 1031 SMTP end outbound transfer The message was successfully transferred outbound. 2000 User Min Minimum value allowed for a third-party event. Put all non-MS events at this value or higher.
Last Updated by Simpler-Webb on 3/29/2004 10:11:56 AM (QID #1132)
Categories: Exchange 2003/Tracking Log EventIDs |