Export (0) Print
Expand All

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 Office Outlook 2003

  • Microsoft Office Outlook 2007

  • Microsoft Outlook 2010

  • Microsoft Outlook 2013

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.1.1.1: Exchange 2013 ignores the OpenSoftDeleted bit and always opens an existing folder. Exchange 2013 does not provide access to soft-deleted folders.

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

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

<4> Section 2.2.1.8: Exchange 2013 does not support the RopCopyFolderROP ([MS-OXCROPS] section 2.2.4.8) for public folders.

<5> Section 2.2.1.9: Exchange 2013 does not support the RopEmptyFolderROP ([MS-OXCROPS] section 2.2.4.9) for public folders.

<6> Section 2.2.1.10: Exchange 2013 does not support the RopHardDeleteMessagesAndSubfoldersROP ([MS-OXCROPS] section 2.2.4.10) for public folders.

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

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

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

<10> Section 3.2.5.2: Exchange 2007 and Exchange 2013 return ecAccessdenied. Exchange 2010 returns ecNoCreateSubfolderRight.

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

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

<13> 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 RopSetSearchCriteriaROP request and will use the preserved values instead of the default values.

<14> Section 3.2.5.4: Exchange 2003, Exchange 2007, and Exchange 2010 do not fail the RopSetSearchCriteriaROP when the search folder (2) is included in its own search scope.

<15> Section 3.2.5.4: Exchange 2007 silently ignores invalid bits and does not return the ecInvalidParam error code.

<16> Section 3.2.5.9: Exchange 2003, Exchange 2007, the initial release version of Exchange 2010, and Exchange 2010 SP1 do not return ecNotSupported (0x80040102) when the RopEmptyFolderROP ([MS-OXCROPS] section 2.2.4.9) is called on the Root folder. Update Rollup 4 for Exchange 2010 SP2 and Exchange 2013 return ecNotSupported when the RopEmptyFolderROP is called on the Root folder.

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

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

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

Show:
© 2014 Microsoft