Among deliveries to local mailboxes, the Message Tracking Center might also list deliveries to mail-enabled Public Folders. Organizations often use Public Folders as archives for messages sent to distribution groups and, in terms of delivery, Exchange 2000 processes these messages the same way it does those sent to a local mailbox. The only way you can tell that a recipient is a Public Folder is if you recognize the recipient name as that of a Public Folder rather than a person.
The Message Tracking Center follows the progress of a message until the message reaches its destination or meets a server that doesn't have tracking enabled. As I mentioned earlier, the Message Tracking Center depends on message tracking being enabled on each server, preferably in a consistent manner across all servers in the organization. Obviously, if you don't enable message tracking on some Exchange servers in your organization, those servers won't create tracking logs and the Message Tracking Center might not give you a complete message history.
Tracking Log Format
The message tracking log format uses tab-delimited fields, including the ones listed here. You can see some of these fields in the Microsoft Excel spreadsheet that Figure 6 shows, which is an extract of a log edited for clarity.
The date and time a message was sent. Exchange 2000 sets this value to the time when the message was first submitted to the server, not when it first arrived on a server that hosts a message tracking log.
The IP address and network name of the client that generated the message.
The partner or messaging service that the Routing Engine handed the message to for processing (e.g., the Store, for local delivery).
The IP address and server name of the server that generated the message.
The recipient address. Upon message submission, the recipient address is shown in Exchange 2000 internal X.500 format. The address is shown in SMTP format after the Categorizer processes the message (event ID 1023).
An event ID that identifies the specific processing that's occurred.
A unique message ID that doesn't change, no matter how many servers the message travels through.
The priority of the message: 1 is low, 0 is normal, and 1 is high.
The total size of the message in bytes.
A flag that indicates the encryption status of the message: 1 is signed, 2 is encrypted, and 0 is clear text.
The version of the Routing Engine running on the local server or the version of the SMTP server on a remote server.
The message subject, if permitted by the server property settings. The subject is truncated to 256 bytes, if necessary.
The number of recipients.
The sender's email address. This value is the primary address of the originating mailbox, if known. It could be in X.400, SMTP, or distinguished name (DN) format, depending on the transport that introduced the message.
Prev. page
