Information Written to the Message Tracking Log
.gif "Cc539063.chm_head_left(en-us,TechNet.10).gif") |
|
.gif "Cc539063.chm_head_right(en-us,TechNet.10).gif") |
Information Written to the Message Tracking Log
The message tracking log stores each message event on a single line in the log. The event types that are used to classify each message event are explained in the following table.
Table: Event Types Used to Classify Each Message Event
| Event name | Description |
|---|---|
| BADMAIL | A message was submitted by the Pickup directory or the Replay directory that cannot be delivered or returned. |
| DELIVER | A message was delivered to a mailbox. |
| DSN | A delivery status notification (DSN) was generated. |
| EXPAND | A distribution group was expanded. |
| FAIL | A message delivery failed. |
| POISONMESSAGE | A message is put in the poison message queue or removed from the poison message queue. |
| SUSPEND | Indicates that replication has been halted for the passive copy. This state prevents the database from advancing, and logs from being copied. Possible values are True and False. |
| RECEIVE | A message was received and committed to the database. |
| REDIRECT | A message was redirected to an alternative recipient after an Active Directory directory service lookup. |
| RESOLVE | A message's recipients were resolved to a different e-mail address after an Active Directory lookup. |
| SEND | A message was sent by Simple Mail Transfer Protocol (SMTP) to a different server. |
| SUBMIT | A message was submitted by an Exchange Server 2007 computer that has the Mailbox server role installed to an Exchange Server 2007 computer that has the Hub Transport server role or Edge Transport server role installed. |
| TRANSFER | Recipients were moved to a forked message because of content conversion, message recipient limits, or agents. |
The message event information that is stored on each line is organized by fields. These fields are separated by commas. The field name is generally descriptive enough to determine the type of information it contains. However, some of the fields may be blank, or the type of information that is stored in the field may change based on the message event type as described in the table.
General descriptions of the fields that are used to classify each message tracking event are explained in the following topic: Description of Message Tracking Log Fields.