6 Appendix A: Product Behavior

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

  • Microsoft Exchange Server 2003

  • Microsoft Exchange Server 2007

  • Microsoft Exchange Server 2010

  • Microsoft Exchange Server 2013

  • Microsoft Exchange Server 2016

  • Microsoft Office Outlook 2003

  • Microsoft Office Outlook 2007

  • Microsoft Outlook 2010

  • Microsoft Outlook 2013

  • Microsoft Outlook 2016

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product 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.2.3:  When Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 are in Cached Mode and the local cached copy of the category list is in conflict with the copy on the server, Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 do not escape the single quote character.

<2> Section 2.2.5: Exchange 2003 and Office Outlook 2003 do not read or write configuration data FAI messages.

<3> Section 2.2.5.1:  Exchange 2003 uses the string "Exchange.11", and Office Outlook 2003 uses the string "Outlook.11" for the version attribute. Exchange 2007 uses the string "Exchange.12", and Office Outlook 2007 uses the string "Outlook.12" for the version attribute. Exchange 2010 uses the string "Exchange.14", and Outlook 2010 uses the string "Outlook.14" for the version attribute. Exchange 2013 uses the string "Exchange.15", and Outlook 2013 uses the string "Outlook.15" for the version attribute. Exchange 2016 uses the string "Exchange.16", and Outlook 2016 uses the string "Outlook.16" for the version attribute.

<4> Section 2.2.5.1.1: Office Outlook 2003 and Office Outlook 2007 do not support the piAutoDeleteReceipts property.

<5> Section 2.2.5.2.1: Exchange 2003, Exchange 2007, Office Outlook 2003, and Office Outlook 2007 neither read nor write the Name element.

<6> Section 2.2.5.2.2: Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 ignore any digits after the first 3, which means that the maximum precision of elements of the dateTimeRestrictedType is milliseconds.

<7> Section 2.2.5.2.2: This restriction on the category name is supported only by Exchange 2003.

<8> Section 2.2.5.2.2: Exchange 2003 does not use the keyboardShortcut attribute data.

<9> Section 2.2.5.2.2: Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 write the usage count as indicated. However, the most frequently used list is not implemented, and the usageCount attribute is not used.

<10> Section 2.2.5.2.2: Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 will write the last session that this category was applied or changed by the user, but this value is not used.

<11> Section 2.2.5.2.2: Exchange 2003 and Microsoft Office Outlook 2003 Service Pack 3 (SP3) do not support renaming categories.

<12> Section 2.2.5.2.2: Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 will increment this number on every session. A new session occurs for these clients either when the user starts Office Outlook 2007, Outlook 2010,  Outlook 2013, or Outlook 2016 or when not less than 12 hours have elapsed since the previous session.

<13> Section 2.2.5.2.3: Exchange 2003, Exchange 2007, Office Outlook 2003, and Office Outlook 2007 do not store the settings defined in this section.

<14> Section 2.2.5.2.3: Exchange 2010, Exchange 2013, and Exchange 2016 set the value of the OptedInto attribute to "False".

<15> Section 2.2.6: View definitions are used only by Office Outlook 2003 and Office Outlook 2007.

<16> Section 2.2.6.1: Outlook 2010, Outlook 2013, and Outlook 2016 do not read or write the PidTagViewDescriptorBinary property ([MS-OXPROPS] section 2.1045).

<17> Section 2.2.6.2: Outlook 2010, Outlook 2013, and Outlook 2016 do not read or write the PidTagViewDescriptorStrings property ([MS-OXPROPS] section 2.1047).

<18> Section 2.2.7.1.2: Exchange 2003 and Office Outlook 2003 do not support displaying the policy description.

<19> Section 2.2.8: Conversation actions are not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<20> Section 2.2.8.1: The PidLidConversationActionLastAppliedTime property is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<21> Section 2.2.8.2: The PidLidConversationActionMaxDeliveryTime property is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<22> Section 2.2.8.3: The PidLidConversationActionMoveFolderEid property is not supported Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<23> Section 2.2.8.4: The PidLidConversationActionMoveStoreEid property is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<24> Section 2.2.8.5: Exchange 2003, Exchange 2007, Office Outlook 2003, and Office Outlook 2007 do not set the PidLidConversationActionVersion property and ignore it if it is set.

<25> Section 2.2.8.7:  Exchange 2003, Exchange 2007, Office Outlook 2003, and Office Outlook 2007 do not set the PidNameKeywords property for conversation actions.

<26> Section 2.2.8.8:  Exchange 2003, Exchange 2007, Office Outlook 2003, and Office Outlook 2007 do not set the PidTagConversationIndex property for conversation actions.

<27> Section 2.2.8.9:  Exchange 2003, Exchange 2007, Office Outlook 2003, and Office Outlook 2007 do not set the PidTagMessageClass property to "IPM.ConversationAction".

<28> Section 2.2.8.10:  Exchange 2003, Exchange 2007, Office Outlook 2003, and Office Outlook 2007 do not set the PidTagSubject property for conversation actions.

<29> Section 2.2.9: Navigation shortcuts are not supported by Exchange 2003, Exchange 2007, or Office Outlook 2003.

<30> Section 2.2.9.16: The PidTagWlinkAddressBookEID property is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007. Outlook 2010, Outlook 2013, and Outlook 2016 set the PidTagWlinkAddressBookEID property on calendar shortcuts only.

<31> Section 2.2.9.17: The PidTagWlinkAddressBookStoreEID property is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007. Outlook 2010, Outlook 2013, and Outlook 2016 set the PidTagWlinkAddressBookStoreEID property on calendar shortcuts only.

<32> Section 2.2.9.18: The shortcut behavior is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<33> Section 2.2.9.19: The PidTagWlinkROGroupType property is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<34> Section 3.1.4.1.2: Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 use the default values of working from 8 A.M. to 5 P.M., Monday – Friday, in the user's current system time zone.

<35> Section 3.1.4.8: Performing conversation actions is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<36> Section 3.1.4.8:  Exchange 2003, Exchange 2007, Office Outlook 2003, and Office Outlook 2007 do not support finding matching E-mail objects related to a conversation. When connected to an online-mode server and performing an Ignore, Stop Ignoring, Move to Folder, or Stop Move conversation action, Outlook 2010, Outlook 2013, and Outlook 2016 will not attempt to locate matching E-mail objects. For all other scenarios, Outlook 2010, Outlook 2013, and Outlook 2016 will attempt to locate matching E-mail objects.

<37> Section 3.1.4.10.2: Setting the properties specified in this section is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007. Whether Outlook 2010, Outlook 2013, and Outlook 2016 set the PidTagWlinkCalendarColor property (section 2.2.9.15), the PidTagWlinkAddressBookEID property (section 2.2.9.16), the PidTagWlinkAddressBookStoreEID property (section 2.2.9.17), and the PidTagWlinkROGroupType property (section 2.2.9.19) depends upon configuration or administrative settings.

<38> Section 3.1.5.1: Performing conversation actions on incoming messages is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<39> Section 3.1.5.1.1: Duplicate detection on incoming E-mail objects is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<40> Section 3.1.5.1.1: Comparing the value of the PidTagSearchKey property ([MS-OXPROPS] section 2.988) on incoming E-mail objects is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007. Outlook 2010, Outlook 2013, and Outlook 2016 maintain a cache of all E-mail objects received in the past 15 minutes.

<41> Section 3.1.5.2: Performing additional processing on the copy of the E-mail object in the Sent Items special folder is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<42> Section 3.1.6.1: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 have the default duration of 336 hours (14 days).

<43> Section 3.1.6.1: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 implement conversation action expiration without timers. Instead, every time an algorithm calls for an FAI message to be located, Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 run the expiration logic before proceeding with the original algorithm.

<44> Section 3.2.4.1.2: Exchange 2007, Exchange 2010, Exchange 2013, and Exchange 2016 will stop reading the XML document beyond 512 kilobytes.

<45> Section 3.2.5.1: Processing in response to a client uploading changes to a conversation action FAI message is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<46> Section 3.2.5.2:  Exchange 2003, Exchange 2007, Office Outlook 2003, and Office Outlook 2007 do not support processing conversation actions on incoming E-mail objects.

<47> Section 3.2.5.3:  The additional processing on the copy of the E-mail object in the Sent Items special folder specified in this section is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

Show: