| < Day Day Up > |
|
This appendix documents the event identifiers that the Routing Engine logs in the message tracking logs as messages make their way from submission to delivery.
Event Identifier | Meaning | Explanation |
---|---|---|
0 | Message transfer in | The MTA completed transfer of responsibility for a message from a gateway or X.400 link into the local MTA. |
1 | Probe transfer in | The MTA completed transfer of responsibility for a probe from a gateway or X.400 link into the local MTA. |
2 | Report transfer in | The MTA completed transfer of responsibility for a report from a gateway or X.400 link into the local MTA. |
4 | Message submission | A message was submitted by a local email client (usually through the Store). |
5 | Probe submission | An X.400 probe was submitted by a local email client (usually through the 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 message from the local MTA to a gateway, X.400 link, or another MTA. |
9 | Message delivered | The MTA completed transfer of responsibility for a report from the local MTA to a gateway, X.400 link, or another MTA. |
10 | Report delivered | The MTA completed delivery of a receipt or NDR to local recipients (usually through the Store). |
29 | Message rerouted | The MTA has rerouted a message, report, or probe because of a problem with the 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 a user did not request it. In the X.400 protocols, NDRs are always rerouted back to the originating MTA, even if a user did not request the report. |
34 | Report generation | The MTA has created a delivery receipt or NDR. |
43 | Unroutable report discarded | The MTA has discarded a report because it cannot be sent to the apparent 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 was 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 was 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 was generated. |
1000 | Local delivery | The sender and recipient are on the same server. |
1001 | Backbone transfer in | A message was received from another MAPI system across a connector or gateway. |
1002 | Backbone transfer out | A message was sent to another MAPI system across a connector or gateway. |
1003 | Gateway transfer out | A message was sent through a gateway. |
1004 | Gateway transfer in | A 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 SMTP service. |
1011 | SMTP transferred outbound | Outbound mail was transferred to an SMTP recipient. |
1012 | SMTP received inbound | Inbound mail was received from the SMTP service. |
1013 | SMTP transferred inbound | Mail received by the SMTP service was transferred to the 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 SMTP service. |
1016 | SMTP report transferred out | A delivery receipt or NDR was sent to the SMTP service. |
1017 | SMTP report generated | A delivery receipt or NDR was created. |
1018 | SMTP report absorbed | The delivery receipt or NDR could not be delivered. |
1019 | SMTP submit to AQ | A new message is submitted to Advanced Queuing. |
1020 | SMTP begin outbound transfer | A message is about to be sent over the network by the SMTP service. |
1021 | SMTP bad mail | The Routing Engine transferred a message to the badmail directory. |
1022 | SMTP AQ failure | A fatal error occurred in the Advanced Queuing engine. More information is available in the Application Event log. |
1023 | SMTP local delivery | A message was successfully delivered by the Store Driver. |
1024 | SMTP submit message to categorizer | Advanced Queuing submitted a message to the categorizer. |
1025 | SMTP begin to process message | A new message is processed by Advanced Queuing. |
1026 | SMTP AQ failed message | Advanced Queuing failed to process a message. The message will be NDR'd or moved into the badmail directory. |
1027 | SMTP submit message to SD | A message was submitted to the Store Driver. |
1028 | SMTP SD local delivery | The Store Driver successfully delivered a message to a local mailbox. |
1029 | SMTP SD gateway delivery | The Store Driver transferred a message to the MTA. |
1030 | SMTP NDR | Some recipients on the message will cause an NDR to be generated (invalid email address, etc.). |
1031 | SMTP end outbound transfer | The message was successfully transferred outbound. |
1033 | ???? | |
1036 | ???? |
Third-party extensions that log events use events numbered past 2000.
| < Day Day Up > |
|