Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining MIME Conversion
Collapse the table of content
Expand the table of content MIME Conversion

During MIME conversion, the MIME reader keeps track of which MIME parts are saved as attachments and which MIME part is promoted as the message body. If any of these MIME parts are missing a Content-Idheader (2), the MIME reader generates an X-Exchange-MIME-Skeleton-Content-Id header (2) and promotes it to the PidTagBodyContentId property ([MS-OXCMSG] section or the PidTagAttachContentId property ([MS-OXCMSG] section as appropriate. If the message did not have a TNEF MIME part, or it was not promoted, after the message is converted, the whole MIME message SHOULD be saved in the PidTagMimeSkeleton property ([MS-OXCMSG] section, with the MIME part content filtered out for MIME parts that were promoted as a message attachment or message body.

If the message body was an aggregate body, as specified in section, MIME readers SHOULD NOT set the PidTagMimeSkeleton property.

Body part contents for the following content types are included in the PidTagMimeSkeleton property even when the MIME reader has copied their contents to the Message object.

  1. MIME part content for vCard attachments is not removed from the PidTagMimeSkeleton property, even though the content is converted to a Contact object.

  2. iCalendar MIME parts are not filtered out of the PidTagMimeSkeleton property.

  3. For S/MIME messages, the PidTagMimeSkeleton property contains only root part headers (2) since the rest of the data can be retrieved from the attachment.

  4. For DSN messages, an original message attachment is filtered out only if it was promoted as an attachment. Human-readable body content is always filtered. Report parts, which are specified in [RFC3464] as message parts with a Content-Type header (2) value of "message/delivery-status", are not filtered out.

© 2015 Microsoft