The header section is composed of several headers with each header on a separate line (each line is terminated by a CR/LF pair). Each header is composed of a header name followed by a colon and a header value (for example, Subject: message subject).
The following table describes the headers that are used.
| Header Name | Description |
|---|---|
| MIME-Version | Describes the MIME version used. It should contain the value 1.0. Example: MIME-Version: 1.0 |
| Date | Indicates the time the message was submitted by the sender. It is formatted as {sender-local-date} {sender-local-time} {sender-local-time-zone}. Example: Date: 21 Jul 1996 20:12:06-0300 Month names: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, and Dec Time zones should be numeric and prefixed with a "–" (minus sign) or a "+" (plus sign); that is, no named time zones. |
| From | Indicates the sender of the message. For applications using the Exchange Connector, this header is formatted as {sender-friendly-name<user-email-alias@server-input-queue-label>}; where the user e-mail alias is the user's alias in the Microsoft Exchange system (corresponds to the PR_ACCOUNT property of the user) and server-input-queue-label is the label of the Exchange Connector's input queue. Example: From: Jane Doe <janedoe@Exchangeserverinputqueue> For applications using the MAPI Transport Provider, it is formatted as {sender-friendly-name <sender-queue-label>}. Where the sender-queue-label is the MSMQ queue label associated with the sender. Example: From: John Doe <johndoe> |
| Subject | Indicates the subject of the message. The subject text is not formatted. Example: Subject: message subject |
| To | Lists each message recipient separated by a comma. Each recipient is formatted as {recipient-friendly-name <recipient-address>}. For the MSMQ MAPI Transport Provider, the recipient address is the label of the MAPI user input queue associated with the recipient. Example: To: John Doe<johndoe> For the MSMQ Exchange Connector, the recipient name includes the user name plus the label of the Exchange Connector's server input queue. Example: To: Jane Doe<janedoe@ServerInputQueueLabel> |
| Cc | Optional. Lists the copied message recipients separated by a comma. Each recipient is formatted as {recipient-friendly-name <recipient-address>}. For the MSMQ MAPI Transport Provider, the recipient address is the label of the MAPI user input queue associated with the recipient. Example: To: John Doe<johndoe> For the MSMQ Exchange Connector, the recipient name includes the user name plus the label of the Exchange Connector's server input queue. Example: To: Jane Doe<janedoe@ServerInputQueueLabel> |
| Bcc | Optional. Lists the hidden copied message recipients separated by a comma. Each recipient is formatted as {recipient-friendly-name <recipient-address>}. For the MSMQ MAPI Transport Provider, the recipient address can be the MSMQ queue label associated with the recipient. Example: Bcc: John Doe<johndoe> For MSMQ Exchange Connector, the recipient name includes the user name plus the MSMQ queue label of the connector's queue. Example: Bcc: Jane Doe<janedoe@ExchangeConnectorQueueLabel> |
| Content-Type | Optional. Describes the content of the body section of the message. It can have one of the following values (the default is "text/plain; charset=us-ascii"): text/plain; charset=us-ascii This means that this is a regular message, and the body section contains the message text. Example: Content-Type: text/plain; charset=us-ascii application/x-ms-tnef This means that this is a TNEF message and the body section contains the TNEF data of the message. Example: Content-Type: application/x-ms-tnef multipart/form-data; boundary=boundary-string This means that the form and body section have multiple parts, and each part describes a single form field (name, value, and so on). The boundary-string separates multiple parts in the body section (see Body Section).
Example: Content-Type: multipart/form-data; |
| Content-Transfer-Encoding | Describes the encoding of the body section (if it contains binary data). The only legal header value is binary (that is, no encoding of binary data). Example: Content-Transfer-Encoding: binary |
| X-Form-Name | Name of the form whose fields are described in the body section. This header is not necessary on text messages, only on form messages. The name here corresponds to the name defined by the Exchange Form Designer (see the Item Type field in the General tab of the Form Properties dialog box) and the PR_MESSAGE_CLASS property of the form. Example: X-Form: IPM.ORGANIZATION.SAMPLE |
| X-Delivery-Report-Requested | Specifies whether the receiving application should return a delivery report when the message is received. Valid values are True or False. Example: X-Delivery-Report-Requested: True |
| X-Non-Delivery-Report-Requested | Specifies whether a non-delivery report should be sent back. Valid values are True or False. Example: X-Non-Delivery-Report-Requested: True |
| X-Report-Date | Indicates the time the report was submitted. This header is only set for delivery or non-delivery report messages. It is formatted as the Date header mentioned previously. Example: X-Report-Date: 22 Jul 1996 21:12:06 –0300 |
| X-Report-To | Specifies the recipient of the delivery or non-delivery report. This header is set only on delivery or non-delivery report messages. It is formatted as the To header above but contains only one recipient. Example: X-Report-To: John Doe<johndoe> |
| X-Report-Delivered-To X-Report-Delivered-Cc X-Report-Delivered-Bcc |
Specifies recipients who received a previously sent mail. These headers are only set on delivery report messages. X-Report-Delivered-To specifies the delivered recipients from the To list of the original e-mail. X-Report-Delivered-Cc specifies the delivered recipients from the Cc list of the original e-mail. X-Report-Delivered-Bcc specifies the delivered recipients from the Bcc list of the original e-mail. They are formatted as the To header above, but contain the delivery time as well. The delivery time is formatted as the Date header above and appears between round brackets after the recipient's address. Example: X-Report-Delivered-To: John Doe<johndoe>(22 Jul 1996 21:11:06 –0300), Jane Doe<mailto:janedoe@ExchangeConnectorQueueLabel >(21 Jul 1996 20:06:06 –0300) |
| X-Report-Not-Delivered-To X-Report- Not-Delivered-Cc X-Report- Not-Delivered-Bcc |
Specifies recipients who did not receive a previously sent mail. These headers are set only on non-delivery report messages. X-Report-Not-Delivered-To specifies the non-delivered recipients from the To list of the original e-mail. X-Report-Not-Delivered-Cc specifies the non-delivered recipients from the Cc list of the original e-mail. X-Report-Not-Delivered-Bcc specifies the non-delivered recipients from the Bcc list of the original e-mail. They are formatted as the X-Report-Delivered-To header above but contain the non-delivery reason instead of the delivery time. The non-delivery reason is not formatted and appears between round brackets after the recipient's address. Example: X-Report-Not-Delivered-To: John Doe<johndoe>(Communication failure), Jane Doe<mailto:janedoe@ExchangeConnectorQueueLabel >(Recipient is not known at this address) |
For samples of the MSMQ mail format, see Sample Form Message and Sample Text Message.