RFC 822 headers are mapped to MAPI properties as follows. PR_SENDER_* is an abbreviation for the following 5 properties:
Similar abbreviations are used for PR_SENT_REPRESENTING_* and other groups of message properties.
| SMTP header | MAPI property |
|---|---|
| From: | Outbound: PR_SENDER_*; inbound: PR_SENDER_* and PR_SENT_REPRESENTING_* |
| Date: | Outbound: current time; inbound: PR_MESSAGE_DELIVERY_TIME |
| To: | PR_DISPLAY_NAME and PR_EMAIL_ADDRESS for recipients where PR_RECIPIENT_TYPE is MAPI_TO |
| Cc: | PR_DISPLAY_NAME and PR_EMAIL_ADDRESS for recipients where PR_RECIPIENT_TYPE is MAPI_CC |
| Bcc: | PR_DISPLAY_NAME and PR_EMAIL_ADDRESS for recipients where PR_RECIPIENT_TYPE is MAPI_BCC |
| Received: | No corresponding MAPI property; put local host name and your component name here |
| Return-receipt-to: | PR_REPORT_NAME and PR_REPORT_ENTRYID |
| Reply-to: | PR_REPLY_RECIPIENT_ENTRIES and PR_REPLY_RECIPIENT_NAMES |
| Subject: | PR_SUBJECT No particular length limitation. |
| MIME-version: | Always "1.0" |
| X-MS-Attachment: | For compatibility with MS Mail SMTP gateway. filename size mm-dd-yyy hh:mm Details below. |
| entire SMTP message envelope | PR_TRANSPORT_MESSAGE_HEADERS |
| header name TBD | PR_SEND_RICH_INFO for sender only. The TBD header should be used to determine whether the sender is capable of interpreting TNEF content in a reply. |
| MessageID: | PR_TNEF_CORRELATION_KEY |
| Content-type | Either text/plain or multipart/mixed. See "Message Content" section. |
The X-MS-Attachment header is formatted as four tokens, separated by a space:
name size date time
The first token is the filename, which may contain embedded spaces, so this header should be parsed from the right on inbound messages. The size is in bytes; the date is formatted as mm-dd-yyyy, and the time as hh:mm.
Note MessageID is not mapped to PR_SEARCH_KEY because the SMTP domain has specific requirements on the format of the message identifier which make it impossible to encode an arbitrary MAPI message identifier. Instead, MessageID is mapped to PR_TNEF_CORRELATION_KEY. This property is a transport-defined property that is set by the transport sending an outbound message and used by a transport receiving an inbound message. For more information, see Developing a TNEF-Enabled Transport Provider.