2.2.168 [RFC6047] Section 2.4 Content-Type Header Field
V0341:
The specification states that a MIME body part containing content information that conforms to [RFC6047] MUST have an "Content-Type" value of "text/calendar", as specified in [RFC2045].
Microsoft Office Outlook 2007, Microsoft Outlook 2010, Microsoft Outlook 2013, Microsoft Outlook 2016, Microsoft Outlook 2019
On export, Outlook exports iMIP data in MIME parts with a Content-Type of "text/calendar". .ics files attached to e-mail messages have a Content-Type of "application/octet-stream".
On import, MIME parts that contain iMIP data MUST have a Content-Type header of "text/calendar" in order for Outlook to treat them as iMIP data.
V0342:
The specification states that the "Content-Type" header field, as specified in [RFC2045], must also include the type parameter "method", and the value MUST be the same as the value of the METHOD calendar property within the iCalendar object.
Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, Outlook 2019
On import, if the value of the method parameter of the Content-Type header does not match the value of the METHOD property in the iCalendar object, the value of the METHOD property in the iCalendar object is used.
V0343:
The specification states that a MIME message containing multiple iCalendar objects with different method values must be further encapsulated with a "multipart/mixed" MIME entity.
Office Outlook 2007
Office Outlook 2007 does not export multiple iCalendar objects as iMIP data in one MIME message. In "multipart/mixed" MIME messages, Outlook only exports iMIP data as the first child of the "multipart/mixed" MIME part (or a descendant of that first child). iCalendar data located elsewhere in a "multipart/mixed" MIME message is intended to be an .ics attachment.
On import, Office Outlook 2007 only searches the first child (and its descendants) of a "multipart/mixed" MIME part for iMIP data. Any iCalendar data found elsewhere in a "multipart/mixed" MIME message is treated as an attachment.
Outlook 2010, Outlook 2013, Outlook 2016, Outlook 2019
Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019and behave identically to Office Outlook 2007, with the following exception:
Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 search in all children of a "multipart/mixed" MIME part for iMIP data. If multiple children contain iMIP data, all but the first are treated as attachments.
V0344:
The specification states that a "charset" parameter MUST be present if the iCalendar object contains characters that are not part of the US-ASCII character set.
Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, Outlook 2019
Outlook exports the "charset" parameter of the Content-Type header as "utf-8". On import, Outlook ignores the "charset" parameter on the Content-Type header and always imports iMIP data as UTF-8.
V0345:
The specification states that the optional "component" parameter defines the iCalendar component type contained within the iCalendar object.
Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, Outlook 2019
Outlook does not export the "component" parameter of the Content-Type header, and ignores it on import.
V0346:
The specification states that in order to permit the information in the scheduling message to be understood by MIME user agents that do not support the "text/calendar" content type, scheduling messages SHOULD be sent with an alternative, human-readable form of the information.
Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, Outlook 2019
If the meeting has an attachment, Outlook exports the iMIP data as a child in a "multipart/alternative" MIME part that also contains a plain-text representation of the data.
On import, Outlook uses the first "text/html" child of a "multipart/alternative" parent to replace the DESCRIPTION property of the iMIP data.