Export (0) Print
Expand All

3 Structure Examples

The following is an example of the Envelope-Part structure contained in a journal record message, followed by an explanation of the various syntax elements. Note that the line numbers are not present in the actual Envelope-Part structure but are shown here so that the structure can be discussed line by line.

1 Sender: sender@contoso.com
2 Subject: Sample Message
3 Message-ID: <12345@contoso.com>
4 To: dl-to-member1@contoso.com, Expanded: dl-to@contoso.com
5 To: dl-to-member2@contoso.com, Expanded: dl-to@contoso.com
6 Cc: fwd@contoso.com, Forwarded: user@contoso.com
7 Bcc: dl-bcc-member@contoso.com, Expanded: dl-bcc@contoso.com
8 Bcc: fwd2@contoso.com, Forwarded: user2@contoso.com
9 Recipient: user-unk@contoso.com
  1. The sender of the original message was sender@contoso.com.

  2. The subject of the original message was "Sample Message".

  3. The value of the Message-ID field, as specified in [RFC2822] section 3.6.4, of the original message was "12345@contoso.com".

  4. The original message was sent to dl-to@contoso.com as a To recipient, which is a distribution list that was expanded to dl-to-member1@contoso.com and dl-to-member2@contoso.com (captured in line 5) by the server.

  5. See (4).

  6. The original message was sent to user@contoso.com as a Cc recipient, which was changed by the email server to fwd@contoso.com because recipient forwarding was configured. user@contoso.com did not receive a copy of the message because there is no occurrence of the recipient-specification field where user@contoso.com was listed in the forward-path field.

  7. The original message was sent by the mail client to dl-bcc@contoso.com as a Bcc recipient, which is a distribution list that was expanded to dl-bcc-member@contoso.com.

  8. The original message was sent to user2@contoso.com as a Bcc recipient, which was rewritten by the email server to fwd2@contoso.com because recipient forwarding was configured. user2@contoso.com did not receive a copy of the message because there is no occurrence of the recipient-specification field where user2@contoso.com was listed in the forward-path field.

  9. Finally, there is no information about whether user-unk@contoso.com was sent the original message as a To recipient, Cc recipient, or Bcc recipient. It is also not known whether this recipient (1) received the message due to distribution list expansion, recipient forwarding, or being directly addressed by the sender. The value of the recipient field indicates that the server was only able to capture that user-unk@contoso.com was a recipient (1) of the message and no further recipient (1) metadata was available.

Show:
© 2014 Microsoft