5 Appendix A: Product Behavior

Article
08/17/2021

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

Microsoft Exchange Server 2003
Microsoft Exchange Server 2007
Microsoft Exchange Server 2010
Microsoft Exchange Server 2013
Microsoft Exchange Server 2016
Microsoft Exchange Server 2019
Microsoft Office Outlook 2003
Microsoft Office Outlook 2007
Microsoft Outlook 2010
Microsoft Outlook 2013
Microsoft Outlook 2016
Microsoft Outlook 2019
Microsoft Outlook 2021
Microsoft Outlook LTSC 2024

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 2.1.3.1.1: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support multiple VCALENDAR components in an iCalendar stream. Office Outlook 2007 and Microsoft Outlook 2010 only support multiple VCALENDAR components when the METHOD property is PUBLISH.

<2> Section 2.1.3.1.1.1: Office Outlook 2003 and Exchange 2003 do not implement the 'COUNTER' value of METHOD. On export, both implementations will use the 'REPLY' value. On import, Office Outlook 2003 will treat the METHOD as 'PUBLISH', while Exchange 2003 will treat the METHOD as 'REPLY'.

<3> Section 2.1.3.1.1.1: Note that it is possible for a collection of two or more VEVENT components to represent a single appointment. However, Office Outlook 2003 has limited support for iCalendars with multiple VEVENT components. Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 have no support. Refer to the documentation on the RECURRENCE-ID Property in section 2.1.3.1.1.20.20 for additional information.

<4> Section 2.1.3.1.1.1: Office Outlook 2003 and Exchange 2003 do not implement the 'COUNTER' value of METHOD. On export, both implementations will use the 'REPLY' value. On import, Office Outlook 2003 will treat the METHOD as 'PUBLISH', while Exchange 2003 will treat the METHOD as 'REPLY'.

<5> Section 2.1.3.1.1.4: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<6> Section 2.1.3.1.1.4: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<7> Section 2.1.3.1.1.5: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<8> Section 2.1.3.1.1.5: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<9> Section 2.1.3.1.1.6: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use this property for purposes outside the scope of this algorithm.

<10> Section 2.1.3.1.1.6: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<11> Section 2.1.3.1.1.7: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use this property for purposes outside the scope of this algorithm.

<12> Section 2.1.3.1.1.7: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016 and Exchange 2019 do not support this property.

<13> Section 2.1.3.1.1.8: Exchange 2003, Exchange 2007 (when parsing iCalendar submitted via WebDAV), Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not support the X-MICROSOFT-CALSCALE property.

<14> Section 2.1.3.1.1.8: Exchange 2003, Exchange 2007 (when parsing iCalendar submitted via WebDAV), Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not support the X-MICROSOFT-CALSCALE property.

<15> Section 2.1.3.1.1.8: Exchange 2003, Exchange 2007 (when parsing iCalendar submitted via WebDAV), Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not support the X-MICROSOFT-CALSCALE property.

<16> Section 2.1.3.1.1.8: Exchange 2003, Exchange 2007 (when parsing iCalendar submitted via WebDAV), Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not support the X-MICROSOFT-CALSCALE property.

<17> Section 2.1.3.1.1.8: Exchange 2003, Exchange 2007 (when parsing iCalendar submitted via WebDAV), Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not support the X-MICROSOFT-CALSCALE property.

<18> Section 2.1.3.1.1.9: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<19> Section 2.1.3.1.1.9: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<20> Section 2.1.3.1.1.10: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use this property for purposes outside the scope of this algorithm.

<21> Section 2.1.3.1.1.10: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<22> Section 2.1.3.1.1.11: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use this property for purposes outside the scope of this algorithm.

<23> Section 2.1.3.1.1.11: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<24> Section 2.1.3.1.1.12: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use this property for purposes outside the scope of this algorithm.

<25> Section 2.1.3.1.1.12: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<26> Section 2.1.3.1.1.13: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use this property for purposes outside the scope of this algorithm.

<27> Section 2.1.3.1.1.13: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<28> Section 2.1.3.1.1.13.1: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use this property for purposes outside the scope of this algorithm.

<29> Section 2.1.3.1.1.13.1: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<30> Section 2.1.3.1.1.14: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use this property for purposes outside the scope of this algorithm.

<31> Section 2.1.3.1.1.14: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<32> Section 2.1.3.1.1.15: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use this property for purposes outside the scope of this algorithm.

<33> Section 2.1.3.1.1.15: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<34> Section 2.1.3.1.1.16: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use this property for purposes outside the scope of this algorithm.

<35> Section 2.1.3.1.1.16: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<36> Section 2.1.3.1.1.16: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<37> Section 2.1.3.1.1.16: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not have logic to avoid splitting surrogate pairs.

<38> Section 2.1.3.1.1.17: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<39> Section 2.1.3.1.1.17: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<40> Section 2.1.3.1.1.17: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<41> Section 2.1.3.1.1.18: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use this property for purposes outside the scope of this algorithm.

<42> Section 2.1.3.1.1.18: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support this property.

<43> Section 2.1.3.1.1.19: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support more than one VTIMEZONE component per iCalendar file.

<44> Section 2.1.3.1.1.19: Office Outlook 2003, Office Outlook 2007, Exchange 2003, Exchange 2007, and the initial release version of Exchange 2010 do not export or import PidLidAppointmentTimeZoneDefinitionRecur, PidLidAppointmentTimeZoneDefinitionStartDisplay, or PidLidAppointmentTimeZoneDefinitionEndDisplay. These implementations only use PidLidTimeZoneDescription and PidLidTimeZoneStruct when exporting or importing VTIMEZONE components and TZID parameters.

<45> Section 2.1.3.1.1.19: Microsoft Exchange Server 2010 Service Pack 1 (SP1), Exchange 2013, Exchange 2016, and Exchange 2019 set the wYear field to 0x0001 for the first TZRule structure in the array.

<46> Section 2.1.3.1.1.19: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use a case-sensitive TZID comparison function.

<47> Section 2.1.3.1.1.19: Office Outlook 2003, Office Outlook 2007, Exchange 2003, Exchange 2007, and the initial release version of Exchange 2010 do not export or import PidLidAppointmentTimeZoneDefinitionRecur, PidLidAppointmentTimeZoneDefinitionStartDisplay, or PidLidAppointmentTimeZoneDefinitionEndDisplay. These implementations only use PidLidTimeZoneDescription and PidLidTimeZoneStruct when exporting or importing VTIMEZONE components and TZID parameters.

<48> Section 2.1.3.1.1.19.1: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use a case-sensitive TZID comparison function.

<49> Section 2.1.3.1.1.19.1: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not override PidLidTimeZoneDescription.

<50> Section 2.1.3.1.1.19.2: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not parse the STANDARD component with the largest DTSTART.

<51> Section 2.1.3.1.1.19.2: Office Outlook 2003 parses the first occurrence of the STANDARD component in the VTIMEZONE.

<52> Section 2.1.3.1.1.19.2: Exchange 2010 SP1, Exchange 2013, Exchange 2016, and Exchange 2019 parse all STANDARD components in the VTIMEZONE that have unique years in their DTSTART subcomponents.

<53> Section 2.1.3.1.1.19.2: Exchange 2003, Exchange 2007, and the initial release version of Exchange 2010 fail if more than one STANDARD component is present in a VTIMEZONE.

<54> Section 2.1.3.1.1.19.2.1: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not set the fields of the stStandardDate field according to the table.

<55> Section 2.1.3.1.1.19.2.1: Office Outlook 2003 imports RDATE if RRULE is not present.

<56> Section 2.1.3.1.1.19.2.1: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 import DTSTART if RRULE is not present.

<57> Section 2.1.3.1.1.19.2.1: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use the year 1601.

<58> Section 2.1.3.1.1.19.2.2: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import VTIMEZONEs with RRULEs that use BYMONTHDAY instead of BYDAY.

<59> Section 2.1.3.1.1.19.2.2: For transitions between Daylight Saving Time and Standard Time based on a specific day of the month, Office Outlook 2003 instead omits the RRULE and exports PidLidTimeZoneStruct.stStandardDate as an RDATE. Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 omit both the RRULE and RDATE, relying on DTSTART to convey the transition date.

<60> Section 2.1.3.1.1.19.2.3: Office Outlook 2003 exports the TZNAME property with value 'Standard Time'.

<61> Section 2.1.3.1.1.19.3: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not parse the DAYLIGHT component with the largest DTSTART.

<62> Section 2.1.3.1.1.19.3: Office Outlook 2003 parses the first occurrence of the DAYLIGHT component in the VTIMEZONE.

<63> Section 2.1.3.1.1.19.3: Exchange 2010 SP1, Exchange 2013, Exchange 2016, and Exchange 2019 parse all DAYLIGHT components in the VTIMEZONE that have unique years in their DTSTART subcomponents.

<64> Section 2.1.3.1.1.19.3: Exchange 2003, Exchange 2007, and the initial release version of Exchange 2010 fail if more than one DAYLIGHT component is present in a VTIMEZONE.

<65> Section 2.1.3.1.1.19.3: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do export a DAYLIGHT component for time zones that do not observe DST. In this case, the TZOFFSETFROM and TZOFFSETTO properties for both the DAYLIGHT and STANDARD components are all set to the same value.

<66> Section 2.1.3.1.1.19.3.3: Office Outlook 2003 exports the TZNAME property with value 'Daylight Saving Time'.

<67> Section 2.1.3.1.1.20.1: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 ignore ATTACH properties.

<68> Section 2.1.3.1.1.20.1: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 ignore ATTACH properties.

<69> Section 2.1.3.1.1.20.1: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, Outlook 2019, Exchange 2007 (when parsing iCalendar submitted via MIME), Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 ignore ATTACH properties specified as CID URIs and, instead, import all of the MIME attachments into the Message object, regardless of whether or not they are referenced in the iCalendar stream.

<70> Section 2.1.3.1.1.20.1: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 ignore ATTACH properties.

<71> Section 2.1.3.1.1.20.1: Prior to Microsoft Exchange Server 2007 Service Pack 1 (SP1), Exchange 2007 (when parsing iCalendar submitted via MIME) does not export ATTACH properties specified as CID URIs.

<72> Section 2.1.3.1.1.20.1: Prior to Exchange 2007 SP1, Exchange 2007 (when parsing iCalendar submitted via MIME) does not export ATTACH properties specified as CID URIs.

<73> Section 2.1.3.1.1.20.1: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not export ATTACH properties encoded with base64 encoding.

<74> Section 2.1.3.1.1.20.1.2: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 ignore ATTACH properties.

<75> Section 2.1.3.1.1.20.1.4: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 ignore ATTACH properties.

<76> Section 2.1.3.1.1.20.1.4: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not export ATTACH properties encoded with base64 encoding.

<77> Section 2.1.3.1.1.20.2: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not parse attendee properties with value 'invalid:nomail'.

<78> Section 2.1.3.1.1.20.2: Office Outlook 2007 does not import attendees with a CUTYPE other than "RESOURCE" or "ROOM" and a ROLE of "NON-PARTICIPANT" to PidLidNonSendableBcc.

<79> Section 2.1.3.1.1.20.2: Office Outlook 2007 imports attendees with a CUTYPE other than "RESOURCE" or "ROOM" and a ROLE of "NON-PARTICIPANT" to PidLidNonSendableCc.

<80> Section 2.1.3.1.1.20.2: Office Outlook 2003 imports only one attendee property when the METHOD property has value 'REPLY'. For any other value of METHOD, Office Outlook 2003 does not import any attendee properties.

<81> Section 2.1.3.1.1.20.2: Office Outlook 2003 does not perform address book lookups on attendee properties. A one-off EntryID is created.

<82> Section 2.1.3.1.1.20.2: Office Outlook 2003 does not set this property.

<83> Section 2.1.3.1.1.20.2: Office Outlook 2003 does not set this property.

<84> Section 2.1.3.1.1.20.2: Office Outlook 2003 does not set this property.

<85> Section 2.1.3.1.1.20.2: Office Outlook 2003 incorrectly adds the RECIP_ORGANIZER (0x00000002) bit to this property.

<86> Section 2.1.3.1.1.20.2: Office Outlook 2003 uses MAPI_TO (0x00000001).

<87> Section 2.1.3.1.1.20.2: Office Outlook 2003, Exchange 2003, Office Outlook 2007, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import the PARTSTAT parameter as PidTagRecipientTrackStatus.

<88> Section 2.1.3.1.1.20.2: Office Outlook 2003, Exchange 2003, Office Outlook 2007, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import the X-MS-OLK-RESPTIME parameter.

<89> Section 2.1.3.1.1.20.2: Exchange 2003 does not use this table.

<90> Section 2.1.3.1.1.20.2: Office Outlook 2007 sets PidTagRecipientType to 0x00000002 for attendees with a CUTYPE other than "RESOURCE" or "ROOM" and a ROLE of "NON-PARTICIPANT".

<91> Section 2.1.3.1.1.20.2: Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not check PidLidAppointmentStateFlags before exporting attendee properties.

<92> Section 2.1.3.1.1.20.2: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, and Exchange 2013, Exchange 2016, and Exchange 2019 omit the attendee property if no SMTP address is available.

<93> Section 2.1.3.1.1.20.2: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not export PidLidNonSendableTo, PidLidNonSendableCc, or PidLidNonSendableBcc.

<94> Section 2.1.3.1.1.20.2.1: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not export PidLidNonSendableTo, PidLidNonSendableCc, or PidLidNonSendableBcc.

<95> Section 2.1.3.1.1.20.2.2: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not export the CUTYPE parameter.

<96> Section 2.1.3.1.1.20.2.2: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not export the CUTYPE parameter.

<97> Section 2.1.3.1.1.20.2.3: Office Outlook 2003, Exchange 2003, Office Outlook 2007, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import the PARTSTAT parameter for calendars with a METHOD of PUBLISH.

<98> Section 2.1.3.1.1.20.2.3: Office Outlook 2003, Exchange 2003, Office Outlook 2007, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not export the PARTSTAT parameter for calendars with a METHOD of PUBLISH.

<99> Section 2.1.3.1.1.20.2.3: Office Outlook 2003, Office Outlook 2007, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not export the PARTSTAT parameter for calendars with a METHOD of PUBLISH.

<100> Section 2.1.3.1.1.20.2.4: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 export a ROLE of 'REQ-PARTICIPANT' instead of omitting the ROLE parameter.

<101> Section 2.1.3.1.1.20.2.4: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not export PidLidNonSendableTo, PidLidNonSendableCc, or PidLidNonSendableBcc.

<102> Section 2.1.3.1.1.20.2.6: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, Exchange 2019, Office Outlook 2003, and Office Outlook 2007 do not import the X-MS-OLK-RESPTIME parameter.

<103> Section 2.1.3.1.1.20.2.6: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, Exchange 2019, Office Outlook 2003, and Office Outlook 2007 do not export the X-MS-OLK-RESPTIME parameter from PidLidAppointmentReplyTime.

<104> Section 2.1.3.1.1.20.3: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not apply this filter.

<105> Section 2.1.3.1.1.20.3: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 consider all of the following to be whitespace characters: Unicode characters U+0009, U+000A, U+000B, U+000C, U+000D, U+0020, U+0085, U+00A0, U+1680, U+2000, U+2001, U+2002, U+2003, U+2004, U+2005, U+2006, U+2007, U+2008, U+2009, U+200A, U+200B, U+2028, U+2029, U+202F, U+3000.

<106> Section 2.1.3.1.1.20.3: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not apply this filter.

<107> Section 2.1.3.1.1.20.3: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not apply this filter.

<108> Section 2.1.3.1.1.20.3: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not have logic to avoid splitting surrogate pairs.

<109> Section 2.1.3.1.1.20.3: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not apply this filter.

<110> Section 2.1.3.1.1.20.4: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 map SENSITIVITY_PERSONAL (0x00000001) to the 'PERSONAL' value of the CLASS property.

<111> Section 2.1.3.1.1.20.4: Office Outlook 2003 does not support the 'X-PERSONAL' value of the CLASS property. SENSITIVITY_PERSONAL (0x00000001) is exported as 'PRIVATE'.

<112> Section 2.1.3.1.1.20.5: Exchange 2007 (when parsing iCalendar submitted via WebDAV) and Office Outlook 2003 do not import or export the COMMENT property. For backwards compatibility, if the METHOD property of the VCALENDAR component is set to 'REPLY' or 'COUNTER', then Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 will export PidTagBody as both COMMENT and DESCRIPTION. In this same case, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 will import PidTagBody from COMMENT, falling back on DESCRIPTION if a COMMENT is not specified. Regardless of the METHOD property of the VCALENDAR, Exchange 2007 (when parsing iCalendar submitted via MIME) will import PidTagBody from DESCRIPTION, falling back on the COMMENT property if no DESCRIPTION is specified. Exchange 2010 will import PidTagBody from DESCRIPTION and ignore COMMENT. Microsoft Exchange Server 2010 Service Pack 2 (SP2), Exchange 2013, Exchange 2016, and Exchange 2019 will import PidTagBody from COMMENT only if the METHOD property is set to 'REPLY' or 'COUNTER' and the DESCRIPTION property is not specified.

<113> Section 2.1.3.1.1.20.6: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the CONTACT property.

<114> Section 2.1.3.1.1.20.6: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not apply this filter.

<115> Section 2.1.3.1.1.20.6: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016 and Outlook 2019 consider all of the following to be whitespace characters: Unicode characters U+0009, U+000A, U+000B, U+000C, U+000D, U+0020, U+0085, U+00A0, U+1680, U+2000, U+2001, U+2002, U+2003, U+2004, U+2005, U+2006, U+2007, U+2008, U+2009, U+200A, U+200B, U+2028, U+2029, U+202F, U+3000.

<116> Section 2.1.3.1.1.20.6: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not apply this filter.

<117> Section 2.1.3.1.1.20.6: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not apply this filter.

<118> Section 2.1.3.1.1.20.6: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not apply this filter.

<119> Section 2.1.3.1.1.20.6: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not have logic to avoid splitting surrogate pairs.

<120> Section 2.1.3.1.1.20.6: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not apply this filter.

<121> Section 2.1.3.1.1.20.6: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the contact property.

<122> Section 2.1.3.1.1.20.7: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the CREATED property.

<123> Section 2.1.3.1.1.20.8: Regardless of the METHOD property of the VCALENDAR, Exchange 2003 and Office Outlook 2003 map DTSTART and DTEND to PidLidAppointmentStartWhole and PidLidAppointmentEndWhole, respectively. Exchange 2003 and Office Outlook 2003 ignore X-MS-OLK-ORIGINALSTART and X-MS-OLK-ORIGINALEND. Furthermore, Exchange 2003 and Office Outlook 2003 never export PidLidAppointmentProposedStartWhole or PidLidAppointmentProposedEndWhole.

<124> Section 2.1.3.1.1.20.8: Regardless of the METHOD property of the VCALENDAR, Exchange 2003 and Office Outlook 2003 map DTSTART and DTEND to PidLidAppointmentStartWhole and PidLidAppointmentEndWhole, respectively. Exchange 2003 and Office Outlook 2003 ignore X-MS-OLK-ORIGINALSTART and X-MS-OLK-ORIGINALEND. Furthermore, Exchange 2003 and Office Outlook 2003 never export PidLidAppointmentProposedStartWhole or PidLidAppointmentProposedEndWhole.

<125> Section 2.1.3.1.1.20.8: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not set PidLidAppointmentDuration.

<126> Section 2.1.3.1.1.20.8: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 require that X-MICROSOFT-CDO-ALLDAYEVENT be set to 'TRUE' if the Calendar object is to be imported as all day. Office Outlook 2003 requires that a VALUE parameter be set to 'DATE' for both DTSTART and DTEND if the Calendar object is to be imported as all day.

<127> Section 2.1.3.1.1.20.8: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-ALLDAYEVENT or X-MICROSOFT-MSNCALENDAR-ALLDAYEVENT properties.

<128> Section 2.1.3.1.1.20.8: Regardless of the METHOD property of the VCALENDAR, Exchange 2003 and Office Outlook 2003 map DTSTART and DTEND to PidLidAppointmentStartWhole and PidLidAppointmentEndWhole, respectively. Exchange 2003 and Office Outlook 2003 ignore X-MS-OLK-ORIGINALSTART and X-MS-OLK-ORIGINALEND. Furthermore, Exchange 2003 and Office Outlook 2003 never export PidLidAppointmentProposedStartWhole or PidLidAppointmentProposedEndWhole.

<129> Section 2.1.3.1.1.20.8: Regardless of the METHOD property of the VCALENDAR, Exchange 2003 and Office Outlook 2003 map DTSTART and DTEND to PidLidAppointmentStartWhole and PidLidAppointmentEndWhole, respectively. Exchange 2003 and Office Outlook 2003 ignore X-MS-OLK-ORIGINALSTART and X-MS-OLK-ORIGINALEND. Furthermore, Exchange 2003 and Office Outlook 2003 never export PidLidAppointmentProposedStartWhole or PidLidAppointmentProposedEndWhole.

<130> Section 2.1.3.1.1.20.8: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not export all day appointments in floating time.

<131> Section 2.1.3.1.1.20.8: Office Outlook 2007 exports non-recurring, non-all day appointments in UTC time.

<132> Section 2.1.3.1.1.20.8.1: Office Outlook 2003, Office Outlook 2007, Exchange 2003, Exchange 2007, and the initial release version of Exchange 2010 do not export or import PidLidAppointmentTimeZoneDefinitionRecur.

<133> Section 2.1.3.1.1.20.8.1: Office Outlook 2003, Office Outlook 2007, Exchange 2003, Exchange 2007, and the initial release version of Exchange 2010 do not export or import PidLidAppointmentTimeZoneDefinitionEndDisplay.

<134> Section 2.1.3.1.1.20.8.1: Office Outlook 2003, Office Outlook 2007, Exchange 2003, Exchange 2007, and the initial release version of Exchange 2010 do not export or import PidLidAppointmentTimeZoneDefinitionRecur.

<135> Section 2.1.3.1.1.20.8.1: Office Outlook 2003, Office Outlook 2007, Exchange 2003, Exchange 2007, and the initial release version of Exchange 2010 do not export or import PidLidAppointmentTimeZoneDefinitionEndDisplay.

<136> Section 2.1.3.1.1.20.8.2: Office Outlook 2003 requires that a VALUE parameter be set to 'DATE' for both DTSTART and DTEND if the Calendar object is to be imported as all day.

<137> Section 2.1.3.1.1.20.9: Exchange 2003 and Exchange 2007 import DTSTAMP as PidLidAttendeeCriticalChange.

<138> Section 2.1.3.1.1.20.10: Regardless of the METHOD property of the VCALENDAR, Exchange 2003 and Office Outlook 2003 map DTSTART and DTEND to PidLidAppointmentStartWhole and PidLidAppointmentEndWhole, respectively. Exchange 2003 and Office Outlook 2003 ignore X-MS-OLK-ORIGINALSTART and X-MS-OLK-ORIGINALEND. Furthermore, Exchange 2003 and Office Outlook 2003 never export PidLidAppointmentProposedStartWhole or PidLidAppointmentProposedEndWhole.

<139> Section 2.1.3.1.1.20.10: Regardless of the METHOD property of the VCALENDAR, Exchange 2003 and Office Outlook 2003 map DTSTART and DTEND to PidLidAppointmentStartWhole and PidLidAppointmentEndWhole, respectively. Exchange 2003 and Office Outlook 2003 ignore X-MS-OLK-ORIGINALSTART and X-MS-OLK-ORIGINALEND. Furthermore, Exchange 2003 and Office Outlook 2003 never export PidLidAppointmentProposedStartWhole or PidLidAppointmentProposedEndWhole.

<140> Section 2.1.3.1.1.20.10: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not set PidLidAppointmentDuration.

<141> Section 2.1.3.1.1.20.10: Exchange 2003, Exchange 2007, and Exchange 2010 require that X-MICROSOFT-CDO-ALLDAYEVENT be set to 'TRUE' if the Calendar object is to be imported as all day. Office Outlook 2003 requires that a VALUE parameter be set to 'DATE' for both DTSTART and DTEND if the Calendar object is to be imported as all day. Exchange 2010 SP1, Exchange 2013, Exchange 2016, and Exchange 2019 import an appointment as an all-day appointment if the VALUE parameter is set to 'DATE' for the DTSTART property and the DTEND and DURATION properties are missing.

<142> Section 2.1.3.1.1.20.10: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-ALLDAYEVENT or X-MICROSOFT-MSNCALENDAR-ALLDAYEVENT properties.

<143> Section 2.1.3.1.1.20.10: Exchange 2010 SP2, Exchange 2013, Exchange 2016, and Exchange 2019 use the value of DTSTART to derive the end time if both the DTEND and DURATION properties are not specified.

<144> Section 2.1.3.1.1.20.10: Regardless of the METHOD property of the VCALENDAR, Exchange 2003 and Office Outlook 2003 map DTSTART and DTEND to PidLidAppointmentStartWhole and PidLidAppointmentEndWhole, respectively. Exchange 2003 and Office Outlook 2003 ignore X-MS-OLK-ORIGINALSTART and X-MS-OLK-ORIGINALEND. Furthermore, Exchange 2003 and Office Outlook 2003 never export PidLidAppointmentProposedStartWhole or PidLidAppointmentProposedEndWhole.

<145> Section 2.1.3.1.1.20.10: Regardless of the METHOD property of the VCALENDAR, Exchange 2003 and Office Outlook 2003 map DTSTART and DTEND to PidLidAppointmentStartWhole and PidLidAppointmentEndWhole, respectively. Exchange 2003 and Office Outlook 2003 ignore X-MS-OLK-ORIGINALSTART and X-MS-OLK-ORIGINALEND. Furthermore, Exchange 2003 and Office Outlook 2003 never export PidLidAppointmentProposedStartWhole or PidLidAppointmentProposedEndWhole.

<146> Section 2.1.3.1.1.20.10: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not export all day appointments in floating time.

<147> Section 2.1.3.1.1.20.10: Office Outlook 2007 exports non-recurring, non-all day appointments in UTC time.

<148> Section 2.1.3.1.1.20.10.1: Office Outlook 2003, Office Outlook 2007, Exchange 2003, Exchange 2007, and the initial release version of Exchange 2010 do not export or import PidLidAppointmentTimeZoneDefinitionRecur.

<149> Section 2.1.3.1.1.20.10.1: Office Outlook 2003, Office Outlook 2007, Exchange 2003, Exchange 2007, and the initial release version of Exchange 2010 do not export or import PidLidAppointmentTimeZoneDefinitionStartDisplay.

<150> Section 2.1.3.1.1.20.10.1: Office Outlook 2003, Office Outlook 2007, Exchange 2003, Exchange 2007, and the initial release version of Exchange 2010 do not export or import PidLidAppointmentTimeZoneDefinitionRecur.

<151> Section 2.1.3.1.1.20.10.1: Office Outlook 2003, Office Outlook 2007, Exchange 2003, Exchange 2007, and the initial release version of Exchange 2010 do not export or import PidLidAppointmentTimeZoneDefinitionStartDisplay.

<152> Section 2.1.3.1.1.20.10.2: Office Outlook 2003 requires that a VALUE parameter be set to 'DATE' for both DTSTART and DTEND if the Calendar object is to be imported as all day.

<153> Section 2.1.3.1.1.20.11: For backwards compatibility, if the METHOD property of the VCALENDAR component is set to 'REPLY' or 'COUNTER', then Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 will export PidTagBody as both COMMENT and DESCRIPTION. In this same case, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 will import PidTagBody from DESCRIPTION if a COMMENT is not specified. Regardless of the METHOD property of the VCALENDAR, Exchange 2007 (when parsing iCalendar submitted via MIME) will import PidTagBody from DESCRIPTION, falling back on the COMMENT property if no DESCRIPTION is specified. Exchange 2010 will import PidTagBody from DESCRIPTION. Exchange 2010 SP2, Exchange 2013, Exchange 2016, and Exchange 2019 will import PidTagBody from COMMENT only if the METHOD property is set to 'REPLY' or 'COUNTER' and the DESCRIPTION property is not specified.

<154> Section 2.1.3.1.1.20.11.1: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the LANGUAGE parameter.

<155> Section 2.1.3.1.1.20.12: Office Outlook 2003 does not import or export the DURATION property.

<156> Section 2.1.3.1.1.20.13: Exchange 2003, Exchange 2007, Exchange 2007 SP1, Microsoft Exchange Server 2007 Service Pack 2 (SP2), Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 ignore all instances of EXDATE except the last one in the VEVENT. Exchange 2003, Exchange 2007 SP2, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 also ignore instances of EXDATE that have more than one value.

<157> Section 2.1.3.1.1.20.13: The initial release version of Exchange 2010 and Exchange 2010 SP1 ignore values of EXDATE that are specified in a time zone other than the time zone specified by PidLidTimeZoneStruct. Exchange 2010 SP2, Exchange 2013, Exchange 2016, and Exchange 2019 convert values of EXDATE to the time zone specified by PidLidTimeZoneStruct.

<158> Section 2.1.3.1.1.20.13: Exchange 2003, Exchange 2007 (when parsing iCalendar submitted via WebDAV), Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not support the X-MICROSOFT-EXDATE property.

<159> Section 2.1.3.1.1.20.13: In certain cases, RecurrencePattern.DeletedInstanceDates will be exported as a X-MICROSOFT-EXDATE instead of an EXDATE. See section 2.1.3.1.1.20.39. Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 export EXDATEs with times set to noon in the time zone specified by PidLidTimeZoneStruct.

<160> Section 2.1.3.1.1.20.13.2: Office Outlook 2003 requires that a VALUE parameter be set to 'DATE' for both DTSTART and DTEND if the Calendar object is to be imported as all day.

<161> Section 2.1.3.1.1.20.14: Exchange 2003 and Exchange 2007 import LAST-MODIFIED as PidLidAttendeeCriticalChange.

<162> Section 2.1.3.1.1.20.14: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the LAST-MODIFIED property.

<163> Section 2.1.3.1.1.20.15: Office Outlook 2003 does not apply this filter.

<164> Section 2.1.3.1.1.20.15: Office Outlook 2003 does not apply this filter.

<165> Section 2.1.3.1.1.20.15: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not have logic to avoid splitting surrogate pairs.

<166> Section 2.1.3.1.1.20.15.1: Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 import the ALTREP parameter on the LOCATION property to the PidNameLocationUrl (section 2.1.3.4.3) property.

<167> Section 2.1.3.1.1.20.15.1: Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 export the PidNameLocationUrl property to the ALTREP parameter on the LOCATION property.

<168> Section 2.1.3.1.1.20.15.2: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the LANGUAGE parameter.

<169> Section 2.1.3.1.1.20.16: Office Outlook 2003 does not import the organizer property when the METHOD property has a value of 'REPLY'.

<170> Section 2.1.3.1.1.20.16: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not export ATTACH properties encoded with base64 encoding.

<171> Section 2.1.3.1.1.20.16: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not export ATTACH properties encoded with base64 encoding.

<172> Section 2.1.3.1.1.20.16: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not export ATTACH properties encoded with base64 encoding.

<173> Section 2.1.3.1.1.20.16: If the METHOD property of the iCalendar is 'REPLY', Office Outlook 2003 exports the first entry in the recipient table as an organizer, ignoring the constraints specified in section 2.1.3.1.1.20.16. For other values of the METHOD property, Office Outlook 2003 exports the Address Book object specified by PidTagSentRepresentingEntryId as an organizer.

<174> Section 2.1.3.1.1.20.16: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 omit the organizer property if no SMTP address is available.

<175> Section 2.1.3.1.1.20.18: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support RDATEs.

<176> Section 2.1.3.1.1.20.18: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support RDATEs.

<177> Section 2.1.3.1.1.20.18: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support RDATEs.

<178> Section 2.1.3.1.1.20.18.2: Office Outlook 2003 requires that a VALUE parameter be set to 'DATE' for both DTSTART and DTEND if the Calendar object is to be imported as all day.

<179> Section 2.1.3.1.1.20.20: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 only import or export the RECURRENCE-ID property in the context of a VCALENDAR component with exactly one VEVENT child and with a METHOD property of value 'REQUEST', 'REPLY', or 'CANCEL'.

<180> Section 2.1.3.1.1.20.20: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 only import or export the RECURRENCE-ID property in the context of a VCALENDAR component with exactly one VEVENT child and with a METHOD property of value 'REQUEST', 'REPLY', or 'CANCEL'.

<181> Section 2.1.3.1.1.20.20: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 only import or export the RECURRENCE-ID property in the context of a VCALENDAR component with exactly one VEVENT child and with a METHOD property of value 'REQUEST', 'REPLY', or 'CANCEL'.

<182> Section 2.1.3.1.1.20.20: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 only import or export the RECURRENCE-ID property in the context of a VCALENDAR component with exactly one VEVENT child and with a METHOD property of value 'REQUEST', 'REPLY', or 'CANCEL'.

<183> Section 2.1.3.1.1.20.20: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 only import or export the RECURRENCE-ID property in the context of a VCALENDAR component with exactly one VEVENT child and with a METHOD property of value 'REQUEST', 'REPLY', or 'CANCEL'.

<184> Section 2.1.3.1.1.20.20: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 only import or export the RECURRENCE-ID property in the context of a VCALENDAR component with exactly one VEVENT child and with a METHOD property of value 'REQUEST', 'REPLY', or 'CANCEL'.

<185> Section 2.1.3.1.1.20.20.2: Office Outlook 2003 requires that a VALUE parameter be set to 'DATE' for both DTSTART and DTEND if the Calendar object is to be imported as all day.

<186> Section 2.1.3.1.1.20.21: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the RESOURCES property.

<187> Section 2.1.3.1.1.20.21: Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 consider all of the following to be whitespace characters: Unicode characters U+0009, U+000A, U+000B, U+000C, U+000D, U+0020, U+0085, U+00A0, U+1680, U+2000, U+2001, U+2002, U+2003, U+2004, U+2005, U+2006, U+2007, U+2008, U+2009, U+200A, U+200B, U+2028, U+2029, U+202F, U+3000.

<188> Section 2.1.3.1.1.20.21: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the RESOURCES property.

<189> Section 2.1.3.1.1.20.21: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the LAST-MODIFIED property.

<190> Section 2.1.3.1.1.20.21: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the RESOURCES property.

<191> Section 2.1.3.1.1.20.22: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, Outlook 2019, Exchange 2003, and Exchange 2007 (when parsing iCalendar submitted via WebDAV) import a PidLidAppointmentSequence of 0x00000000 if no SEQUENCE property is specified.

<192> Section 2.1.3.1.1.20.23: Office Outlook 2003 does not import or export the STATUS property.

<193> Section 2.1.3.1.1.20.24: Office Outlook 2003 does not apply these filters.

<194> Section 2.1.3.1.1.20.24: Office Outlook 2003 does not apply these filters.

<195> Section 2.1.3.1.1.20.24: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not have logic to avoid splitting surrogate pairs.

<196> Section 2.1.3.1.1.20.24: Office Outlook 2003 leaves PidTagSubject unset when no SUMMARY is present.

<197> Section 2.1.3.1.1.20.24: Office Outlook 2003 omits the SUMMARY property if PidTagSubject is unset or empty.

<198> Section 2.1.3.1.1.20.24.1: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the LANGUAGE parameter.

<199> Section 2.1.3.1.1.20.24.1: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the LANGUAGE parameter.

<200> Section 2.1.3.1.1.20.25: Exchange 2003, Exchange 2007, and Exchange 2010 map the TRANSP property directly to PidNameCalendarTransparent. Update Rollup 7 for Exchange Server 2007 Service Pack 3 (SP3), Update Rollup 2 for Exchange Server 2010 Service Pack 2 (SP2), Exchange 2013, Exchange 2016, and Exchange 2019 import the TRANSP property into PidLidBusyStatus if the X-MICROSOFT-CDO-BUSYSTATUS and X-MICROSOFT-MSNCALENDAR-BUSYSTATUS properties are absent.

<201> Section 2.1.3.1.1.20.25: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 map the TRANSP property directly to PidNameCalendarTransparent.

<202> Section 2.1.3.1.1.20.25: Exchange 2003, Exchange 2007, Exchange 2010, Office Outlook 2003, Office Outlook 2007, and Outlook 2010 do not support the value 0x00000004 for the PidLidBusyStatus property ([MS-OXOCAL] section 2.2.1.2).

<203> Section 2.1.3.1.1.20.26: The ByteArrayID is case-sensitive in Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019.

<204> Section 2.1.3.1.1.20.27: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-ALT-DESC property.

<205> Section 2.1.3.1.1.20.27: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-ALT-DESC property.

<206> Section 2.1.3.1.1.20.28: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 check to see if DTEND falls on midnight in the time zone specified by DTSTART.

<207> Section 2.1.3.1.1.20.28: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-ALLDAYEVENT or X-MICROSOFT-MSNCALENDAR-ALLDAYEVENT properties.

<208> Section 2.1.3.1.1.20.28: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not have logic to avoid splitting surrogate pairs.

<209> Section 2.1.3.1.1.20.28: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not have logic to avoid splitting surrogate pairs.

<210> Section 2.1.3.1.1.20.28: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 export X-MICROSOFT-CDO-ALLDAYEVENT.

<211> Section 2.1.3.1.1.20.29: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not import or export X-MICROSOFT-CDO-APPT-SEQUENCE.

<212> Section 2.1.3.1.1.20.29: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 export PidLidAppointmentSequence as X-MICROSOFT-CDO-APPT-SEQUENCE.

<213> Section 2.1.3.1.1.20.30: Exchange 2003 and Exchange 2007 (when parsing iCalendar submitted via WebDAV) import and export the X-MICROSOFT-CDO-ATTENDEE-CRITICAL-CHANGE property.

<214> Section 2.1.3.1.1.20.30: Exchange 2003 and Exchange 2007 (when parsing iCalendar submitted via WebDAV) import and export the X-MICROSOFT-CDO-ATTENDEE-CRITICAL-CHANGE property.

<215> Section 2.1.3.1.1.20.31: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-BUSYSTATUS property.

<216> Section 2.1.3.1.1.20.33: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 export an X-MICROSOFT-CDO-INSTTYPE with values: 0 if the appointment is non-recurring, 1 if the appointment is recurring, and 3 if the appointment is an exception of a recurring appointment.

<217> Section 2.1.3.1.1.20.34: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<218> Section 2.1.3.1.1.20.34: Update Rollup 2 for Exchange 2010 SP2, Exchange 2013, Exchange 2016, and Exchange 2019 set the value of PidLidBusyStatus to 0x00000001 if the METHOD property is REQUEST and the X-MICROSOFT-CDO-INTENDEDSTATUS property is present.

<219> Section 2.1.3.1.1.20.34: Exchange 2010 does not copy the value of PidLidBusyStatus into the PidLidIntendedBusyStatus property. Update Rollup 2 for Exchange 2010 SP2, Exchange 2013, Exchange 2016, and Exchange 2019 do copy the value of PidLidBusyStatus into the PidLidIntendedBusyStatus property. Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<220> Section 2.1.3.1.1.20.34: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<221> Section 2.1.3.1.1.20.34: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<222> Section 2.1.3.1.1.20.35: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not import or export the X-MICROSOFT-CDO-OWNERAPPTID property.

<223> Section 2.1.3.1.1.20.36: Exchange 2003 and Exchange 2007 (when parsing iCalendar submitted via WebDAV) import and export the X-MICROSOFT-CDO-OWNER-CRITICAL-CHANGE property.

<224> Section 2.1.3.1.1.20.36: Exchange 2003 and Exchange 2007 (when parsing iCalendar submitted via WebDAV) import and export the X-MICROSOFT-CDO-OWNER-CRITICAL-CHANGE property.

<225> Section 2.1.3.1.1.20.37: If the METHOD property has value 'REPLY', Exchange 2003 and Exchange 2007 (when parsing iCalendar submitted via WebDAV) will import X-MICROSOFT-CDO-REPLYTIME as PidLidAttendeeCriticalChange in addition to PidLidAppointmentReplyTime.

<226> Section 2.1.3.1.1.20.37: Exchange 2003 and Exchange 2007 (when parsing iCalendar submitted via WebDAV) import and export the X-MICROSOFT-CDO-REPLYTIME property.

<227> Section 2.1.3.1.1.20.38: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MICROSOFT-DISALLOW-COUNTER property.

<228> Section 2.1.3.1.1.20.39: Exchange 2003, Exchange 2007 (when parsing iCalendar submitted via WebDAV), Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not import or export the X-MICROSOFT-EXDATE property.

<229> Section 2.1.3.1.1.20.39: Exchange 2003, Exchange 2007 (when parsing iCalendar submitted via WebDAV), Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not import or export the X-MICROSOFT-EXDATE property.

<230> Section 2.1.3.1.1.20.40: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, Exchange 2019, Office Outlook 2003, and Office Outlook 2007 do not import or export the X-MICROSOFT-ISDRAFT property. Specifically, on import, those implementations treat X-MICROSOFT-ISDRAFT as unset.

<231> Section 2.1.3.1.1.20.40: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, Exchange 2019, Office Outlook 2003, and Office Outlook 2007 do not import or export the X-MICROSOFT-ISDRAFT property. Specifically, on import, those implementations treat X-MICROSOFT-ISDRAFT as unset.

<232> Section 2.1.3.1.1.20.41: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MICROSOFT-MSNCALENDAR-ALLDAYEVENT property.

<233> Section 2.1.3.1.1.20.42: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MICROSOFT-MSNCALENDAR-BUSYSTATUS property.

<234> Section 2.1.3.1.1.20.43: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MICROSOFT-MSNCALENDAR-IMPORTANCE property.

<235> Section 2.1.3.1.1.20.44: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<236> Section 2.1.3.1.1.20.45.2: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, Outlook 2019, Exchange 2003, and Exchange 2007 (when parsing iCalendar submitted via WebDAV) do not import or export the X-MICROSOFT-RRULE property.

<237> Section 2.1.3.1.1.20.46: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-ALLOWEXTERNCHECK property.

<238> Section 2.1.3.1.1.20.47: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-APPTLASTSEQUENCE property.

<239> Section 2.1.3.1.1.20.48: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-APPTSEQTIME property.

<240> Section 2.1.3.1.1.20.48: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-APPTSEQTIME property.

<241> Section 2.1.3.1.1.20.49: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-AUTOFILLLOCATION property.

<242> Section 2.1.3.1.1.20.50: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-AUTOSTARTCHECK property.

<243> Section 2.1.3.1.1.20.51: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-COLLABORATEDOC property.

<244> Section 2.1.3.1.1.20.52: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-CONFCHECK property.

<245> Section 2.1.3.1.1.20.53: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-CONFTYPE property.

<246> Section 2.1.3.1.1.20.54: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-DIRECTORY property.

<247> Section 2.1.3.1.1.20.55: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-MWSURL property.

<248> Section 2.1.3.1.1.20.56: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-NETSHOWURL property.

<249> Section 2.1.3.1.1.20.57: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-ONLINEPASSWORD property.

<250> Section 2.1.3.1.1.20.58: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-ORGALIAS property.

<251> Section 2.1.3.1.1.20.59: Regardless of the METHOD property of the VCALENDAR, Exchange 2003 and Office Outlook 2003 map DTSTART and DTEND to PidLidAppointmentStartWhole and PidLidAppointmentEndWhole, respectively. Exchange 2003 and Office Outlook 2003 ignore X-MS-OLK-ORIGINALSTART and X-MS-OLK-ORIGINALEND. Furthermore, Exchange 2003 and Office Outlook 2003 never export PidLidAppointmentProposedStartWhole or PidLidAppointmentProposedEndWhole.

<252> Section 2.1.3.1.1.20.59: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not set PidLidAppointmentDuration.

<253> Section 2.1.3.1.1.20.60: Regardless of the METHOD property of the VCALENDAR, Exchange 2003 and Office Outlook 2003 map DTSTART and DTEND to PidLidAppointmentStartWhole and PidLidAppointmentEndWhole, respectively. Exchange 2003 and Office Outlook 2003 ignore X-MS-OLK-ORIGINALSTART and X-MS-OLK-ORIGINALEND. Furthermore, Exchange 2003 and Office Outlook 2003 never export PidLidAppointmentProposedStartWhole or PidLidAppointmentProposedEndWhole.

<254> Section 2.1.3.1.1.20.60: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not set PidLidAppointmentDuration.

<255> Section 2.1.3.1.1.20.61: Office Outlook 2003, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not import or export the X-MS-OLK-SENDER property.

<256> Section 2.1.3.1.1.20.61: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 export PidLidAppointmentSequence as X-MICROSOFT-CDO-APPT-SEQUENCE.

<257> Section 2.1.3.1.1.20.61: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 export PidLidAppointmentSequence as X-MICROSOFT-CDO-APPT-SEQUENCE.

<258> Section 2.1.3.1.1.20.61: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 export PidLidAppointmentSequence as X-MICROSOFT-CDO-APPT-SEQUENCE.

<259> Section 2.1.3.1.1.20.61: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 export PidLidAppointmentSequence as X-MICROSOFT-CDO-APPT-SEQUENCE.

<260> Section 2.1.3.1.1.20.61: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 export PidLidAppointmentSequence as X-MICROSOFT-CDO-APPT-SEQUENCE.

<261> Section 2.1.3.1.1.20.61.1: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 export PidLidAppointmentSequence as X-MICROSOFT-CDO-APPT-SEQUENCE

<262> Section 2.1.3.1.1.20.62: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, Outlook 2019, and Exchange 2003 ignore TRIGGER properties that are specified as Date-Time.

<263> Section 2.1.3.1.1.20.62: In this case, Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 set PidLidReminderDelta to 0x0000000F for all Calendar objects.

<264> Section 2.1.3.1.1.20.62: Office Outlook 2003 does not set PidLidReminderSignalTime.

<265> Section 2.1.3.1.1.20.62: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, Outlook 2019, and Exchange 2003 ignore TRIGGER properties that are specified as Date-Time.

<266> Section 2.1.3.2.1.2: For Office Outlook 2003, the maximum INTERVAL of a YEARLY recurrence is 1.

<267> Section 2.1.3.2.1.10: Office Outlook 2003 does not apply this filter.

<268> Section 2.1.3.2.1.11: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 export an X-MICROSOFT-CDO-INSTTYPE with values: 0 if the appointment is non-recurring, 1 if the appointment is recurring, and 3 if the appointment is an exception of a recurring appointment.

<269> Section 2.1.3.2.2: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, Outlook 2019, Exchange 2003, and Exchange 2007 (when parsing iCalendar submitted via WebDAV) do not import or export the X-MICROSOFT-RRULE property.

<270> Section 2.1.3.2.2: Exchange 2003, Exchange 2007, and Exchange 2010 do not set the PidLidClipStart property ([MS-OXOCAL] section 2.2.1.14) or the PidLidClipEnd property ([MS-OXOCAL] section 2.2.1.15). Exchange 2010 SP2, Exchange 2013, Exchange 2016, and Exchange 2019 set the PidLidClipStart and PidLidClipEnd properties as specified.

<271> Section 2.1.3.2.2.1: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<272> Section 2.1.3.2.2.1: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<273> Section 2.1.3.2.2.1: Exchange 2007 (when parsing iCalendar submitted via MIME), Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not follow this guidance.

<274> Section 2.1.3.2.2.1: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not import or export the X-MICROSOFT-CDO-OWNERAPPTID property.

<275> Section 2.1.3.2.2.1: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 export 0x00002021 EndType values as a COUNT part instead of an UNTIL part.

<276> Section 2.1.3.2.2.1: If EndType is 0x00002021, Exchange 2007, Exchange 2007 SP1, and Exchange 2007 SP2 set the UNTIL recurrence part to midnight on the date specified by EndDate.

<277> Section 2.1.3.2.2.1: Office Outlook 2003 will export FirstDOW as the WKST recurrence part, regardless of whether or not it is relevant.

<278> Section 2.1.3.2.2.2: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<279> Section 2.1.3.2.2.2: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<280> Section 2.1.3.2.2.2: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 export 0x00002021 EndType values as a COUNT part instead of an UNTIL part.

<281> Section 2.1.3.2.2.2: If EndType is 0x00002021, Exchange 2007, Exchange 2007 SP1, and Exchange 2007 SP2 set the UNTIL recurrence part to midnight on the date specified by EndDate.

<282> Section 2.1.3.2.2.2: Office Outlook 2003 will export FirstDOW as the WKST recurrence part, regardless of whether it is relevant.

<283> Section 2.1.3.2.2.3: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<284> Section 2.1.3.2.2.3: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 will promote MONTHLY recurrences with an INTERVAL of 12 to a YEARLY recurrence.

<285> Section 2.1.3.2.2.3: Office Outlook 2003 imports BYMONTHDAY directly into PatternTypeSpecific.Month.Day.

<286> Section 2.1.3.2.2.3: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<287> Section 2.1.3.2.2.3: Office Outlook 2003 exports PatternTypeSpecific.Month.Day directly as BYMONTHDAY.

<288> Section 2.1.3.2.2.3: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 export 0x00002021 EndType values as a COUNT part instead of an UNTIL part.

<289> Section 2.1.3.2.2.3: If EndType is 0x00002021, Exchange 2007, Exchange 2007 SP1, and Exchange 2007 SP2 set the UNTIL recurrence part to midnight on the date specified by EndDate.

<290> Section 2.1.3.2.2.3: Office Outlook 2003 will export FirstDOW as the WKST recurrence part, regardless of whether it is relevant.

<291> Section 2.1.3.2.2.4: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<292> Section 2.1.3.2.2.4: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 will promote MONTHLY recurrences with an INTERVAL of 12 to a YEARLY recurrence.

<293> Section 2.1.3.2.2.4: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<294> Section 2.1.3.2.2.4: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 export 0x00002021 EndType values as a COUNT part instead of an UNTIL part.

<295> Section 2.1.3.2.2.4: If EndType is 0x00002021, Exchange 2007, Exchange 2007 SP1, and Exchange 2007 SP2 set the UNTIL recurrence part to midnight on the date specified by EndDate.

<296> Section 2.1.3.2.2.4: Office Outlook 2003 will export FirstDOW as the WKST recurrence part, regardless of whether or not it is relevant.

<297> Section 2.1.3.2.2.5: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<298> Section 2.1.3.2.2.5: Office Outlook 2003 does not support Yearly Recurrence with an INTERVAL other than 1.

<299> Section 2.1.3.2.2.5: Office Outlook 2003 imports BYMONTHDAY directly into PatternTypeSpecific.Month.Day.

<300> Section 2.1.3.2.2.5: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<301> Section 2.1.3.2.2.5: Office Outlook 2003 exports PatternTypeSpecific.Month.Day directly as BYMONTHDAY.

<302> Section 2.1.3.2.2.5: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 export 0x00002021 EndType values as a COUNT part instead of an UNTIL part.

<303> Section 2.1.3.2.2.5: If EndType is 0x00002021, Exchange 2007, Exchange 2007 SP1, and Exchange 2007 SP2 set the UNTIL recurrence part to midnight on the date specified by EndDate.

<304> Section 2.1.3.2.2.5: Office Outlook 2003 will export FirstDOW as the WKST recurrence part, regardless of whether or not it is relevant.

<305> Section 2.1.3.2.2.6: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<306> Section 2.1.3.2.2.6: Office Outlook 2003 does not support Yearly Recurrence with an INTERVAL other than 1.

<307> Section 2.1.3.2.2.6: Office Outlook 2003 does not import or export the X-MICROSOFT-CDO-INTENDEDSTATUS or X-MICROSOFT-MSNCALENDAR-INTENDEDSTATUS properties.

<308> Section 2.1.3.2.2.6: Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 export 0x00002021 EndType values as a COUNT part instead of an UNTIL part.

<309> Section 2.1.3.2.2.6: If EndType is 0x00002021, Exchange 2007, Exchange 2007 SP1, and Exchange 2007 SP2 set the UNTIL recurrence part to midnight on the date specified by EndDate.

<310> Section 2.1.3.2.2.6: Office Outlook 2003 will export FirstDOW as the WKST recurrence part, regardless of whether it is relevant.

<311> Section 2.1.3.2.4: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not implement this compatibility fix for Office Outlook 2003.

<312> Section 2.1.3.2.4: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not implement this compatibility fix for Office Outlook 2003.

<313> Section 2.1.3.2.4: Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not implement this compatibility fix for Office Outlook 2003.

<314> Section 2.1.3.3: Exchange 2007 sets these additional properties.

Share via

5 Appendix A: Product Behavior

Additional resources