exchangefaq.org
brought to you by Simpler-Webb

Table of Contents

Exchange 2003 FAQ
Exchange 2000 FAQ
Exchange 5.5 FAQ

Exchange Resource Manager

Find out how you can manage rooms and resources though Exchange with out the hassles and complications of scripting!

ยป Download a free trial today

01


EventID

Title

Description

0Message transfer inThe MTA completed transfer of responsibility for a message from a gateway, X.400 link, or other MTA into the local MTA.
1Probe transfer inThe MTA completed transfer of responsibility for a probe from a gateway, X.400 link, or other MTA into the local MTA.
2Report transfer inThe MTA completed transfer of responsibility for a report from a gateway, X.400 link, or other MTA into the local MTA.
4Message submissionA message was submitted by a local e-mail client (usually through the Information Store/MDB).
5Probe submissionAn X.400 probe was submitted by a local e-mail client (usually through the Information Store).
6Probe transfer outThe MTA completed transfer of responsibility for a probe from the local MTA to a gateway, X.400 link, or another MTA.
7Message transfer outThe MTA completed transfer of responsibility for a message from the local MTA to a gateway, X.400 link, or another MTA.
8Report transfer outThe MTA completed transfer of responsibility for a report from the local MTA to a gateway, X.400 link, or another MTA.
9Message deliveredThe MTA completed delivery of a message to local recipients (usually through the Information Store).
10Report deliveredThe MTA completed delivery of a receipt or NDR to local recipients (usually through the Information Store).
26Distribution list expansionThe MTA has expanded a distribution list to produce a new message that has recipients who are distribution list members.
28Message redirectedThe 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.
29Message reroutedThe MTA has rerouted a message, report, or probe because of problems with next route X.400 link or MTA.
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 X.400 protocol, NDRs are always routed back to the sending MTA even if the user did not request a report.
34Report generationThe MTA has created a delivery receipt or NDR.
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 outboundOutbound mail was queued for delivery by the Internet Mail Service.
1011SMTP transferred outboundOutbound mail was transferred to an Internet recipient.
1012SMTP received inboundInbound mail was received by the Internet Mail Service.
1013SMTP transferred inboundMail received by the Internet Mail Service was transferred to the Information Store.
1014SMTP message reroutedAn Internet message is being rerouted or forwarded to the proper location.
1015SMTP report transferred inA delivery receipt or NDR was received by the Internet Mail Service.
1016SMTP report transferred outA delivery receipt or NDR was sent to the Internet Mail Service.
1017SMTP report generatedA delivery receipt or NDR was created.
1018SMTP report absorbedThe receipt or NDR could not be delivered.
1019SMTP submit message to AQA new message is submitted to Advanced Queuing.
1020SMTP begin outbound transferA message is about to be sent over the wire by SMTP.
1021SMTP bad mailThe message was transferred to the badmail directory.
1022SMTP AQ failureA fatal Advanced Queuing error occurred. Information about the failure is written to the Event Manager.
1023SMTP local deliveryA message was successfully delivered by a store drive (logged by Advanced Queue).
1024SMTP submit message to catAdvanced Queuing submitted a message to the categorizer.
1025SMTP begin submit messageA new message is submitted to Advanced Queuing.
1026SMTP AQ failed messageAdvanced Queuing could not process the message. The message will be NDRed or put into badmail.
1027SMTP submit message to SDA message was submitted to the store driver by the MTA.
1028SMTP SD local deliveryStore driver successfully delivered a message (logged by store driver).
1029SMTP SD gateway deliveryStore driver transferred the message to the MTA.
1030SMTP NDR allAll recipients were NDRed.
1031SMTP end outbound transferThe message was successfully transferred outbound.
2000User MinMinimum 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 |