Share via

6 Appendix A: Product Behavior

  • Article

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.2.1.1.1: Exchange 2013, Exchange 2016, and Exchange 2019 ignore the OpenSoftDeleted bit and open an existing folder. Exchange 2013, Exchange 2016, and Exchange 2019 do not provide access to soft-deleted folders.

<2> Section 2.2.1.1.2: Exchange 2003, Exchange 2007, Exchange 2016, and Exchange 2019 return zero (FALSE) in the HasRules field, even when there are rules on the Inbox folder.

<3> Section 2.2.1.2.2: Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 return zero (FALSE) in the IsExistingFolder field regardless of the existence of the named public folder.

<4> Section 2.2.1.8: Exchange 2013, Exchange 2016, and Exchange 2019 do not support the RopCopyFolder ROP ([MS-OXCROPS] section 2.2.4.8) for public folders.

<5> Section 2.2.1.8.2:  Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 return a zero value for PartialCompletion if the ROP fails for a subset of targets.

<6> Section 2.2.1.9: Exchange 2013, Exchange 2016, and Exchange 2019 do not support the RopEmptyFolder ROP ([MS-OXCROPS] section 2.2.4.9) for public folders.

<7> Section 2.2.1.10: Exchange 2013, Exchange 2016, and Exchange 2019 do not support the RopHardDeleteMessagesAndSubfolders ROP ([MS-OXCROPS] section 2.2.4.10) for public folders.

<8> Section 2.2.1.14.1:  Exchange 2003 and Exchange 2007 do not support the ConversationMembers bit.

<9> Section 2.2.2.2.1.4:  Exchange 2013 and later do not support the PidTagAddressBookEntryId property.

<10> Section 2.2.2.2.2.9: Outlook 2010 and later do not use the PidTagAccessControlListData property ([MS-OXCPERM] section 2.2.3).

<11> Section 3.2.5.1:  If the specified folder has been hard deleted, Exchange 2007 does not fail the RopOpenFolder ROP ([MS-OXCROPS] section 2.2.4.1), but no folder is opened.

<12> Section 3.2.5.2: Exchange 2007, Exchange 2013 and later return ecAccessdenied. Exchange 2010 returns ecNoCreateSubfolderRight.

<13> Section 3.2.5.2:  Exchange 2010 returns ecError if the client attempted to create a search folder on a public folders message store.

<14> Section 3.2.5.3:  Exchange 2010 and later ignore invalid bits instead of failing the ROP.

<15> Section 3.2.5.4:  A content-indexed search is static on the initial release version of Exchange 2010 and Exchange 2007 regardless of the value of the STATIC_SEARCH bit in the RopSetSearchCriteria request.

<16> Section 3.2.5.4:  Exchange 2003, Exchange 2007, and Exchange 2010 preserve the values of the STOP_SEARCH, RESTART_SEARCH, RECURSIVE_SEARCH, and SHALLOW_SEARCH bits from the previous RopSetSearchCriteria ROP request and will use the preserved values instead of the default values.

<17> Section 3.2.5.4:  Exchange 2003, Exchange 2007, and Exchange 2010 do not fail the RopSetSearchCriteria ROP when the search folder is included in its own search scope.

<18> Section 3.2.5.4: Exchange 2007 silently ignores invalid bits and does not return the ecInvalidParam error code. Exchange 2019 returns a ecNotSupported error code.

<19> Section 3.2.5.9: Exchange 2003, Exchange 2007, the initial release version of Exchange 2010, and Microsoft Exchange Server 2010 Service Pack 1 (SP1) do not return ecNotSupported (0x80040102) when the RopEmptyFolder ROP ([MS-OXCROPS] section 2.2.4.9) is called on the Root folder. Update Rollup 4 for Exchange Server 2010 Service Pack 2 (SP2) and later return ecNotSupported when the RopEmptyFolder ROP is called on the Root folder.

<20> Section 3.2.5.13:  Exchange 2007 ignores invalid bits instead of failing the ROP.

<21> Section 3.2.5.14:  Exchange 2003 fails the ROP with an error code of ecInvalidParam. Exchange 2007 ignores the ConversationMembers bit.

<22> Section 3.2.5.14:  Exchange 2007 ignores invalid bits instead of failing the ROP.