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

  • Microsoft Office Outlook 2007

  • Microsoft Outlook 2010

  • Microsoft Outlook 2013

  • Microsoft Outlook 2016

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: Exchange 2007 changes properties PidTagAccess and PidTagLastModificationTime. Exchange 2010, Exchange 2013, and Exchange 2016 change properties PidTagAccess, PidTagAccessLevel, PidTagChangeKey, PidTagCreationTime, PidTagLastModificationTime, PidTagLastModifierName, PidTagSearchKey, PidTagHasAttachments, PidTagMessageFlags, PidTagMessageSize, PidTagMessageStatus, and PidTagAttachSize.

<2> Section 2.2.1.1:  Exchange 2010, Exchange 2013, and Exchange 2016 do not support the PidTagObjectType property

<3> Section 2.2.1.1:  Exchange 2010, Exchange 2013, and Exchange 2016 do not support the PidTagRecordKey property.

<4> Section 2.2.1.6:  Exchange 2007 does not set the mfEverRead flag when the mfRead flag is set.

<5> Section 2.2.1.45: The PidTagTrustSender property (section 2.2.1.45) is not supported in Exchange 2010, Exchange 2013, and Exchange 2016.

<6> Section 2.2.1.56.2:  Exchange 2003 and Exchange 2007 do not support the PidTagNativeBody property.

<7> Section 2.2.1.58.6: Exchange 2003, Exchange 2007, and the initial release version of Exchange 2010 do not support the NeedsRescan flag.

<8> Section 2.2.1.58.6: Exchange 2003, Exchange 2007, and the initial release version of Exchange 2010 do not support the PendingRescan flag.

<9> Section 2.2.2.1:   Exchange 2010, Exchange 2013, and Exchange 2016 do not support the PidTagObjectType property.

<10> Section 2.2.2.20:  Office Outlook 2003 only correctly detects MacBinary I and MacBinary II.

<11> Section 2.2.3.1: Exchange 2010, Exchange 2013, and Exchange 2016 can output unexpected results when using the RopOpenMessage ROP ([MS-OXCROPS] section 2.2.6.1) when Client Access Services are deployed on an Exchange server that does not also have a mailbox message store installed.

<12> Section 2.2.3.1.1:  Exchange 2010, Exchange 2013, and Exchange 2016 return read/write messages when the user does not have write permissions.

<13> Section 2.2.3.3.1: Exchange 2010, Exchange 2013, and Exchange 2016 ignore the KeepOpenReadOnly flag.

<14> Section 2.2.3.3.1:  The value of ForceSave is 0x0C in Microsoft Exchange Server 2007 Service Pack 3 (SP3).

<15> Section 2.2.3.10.2:  Exchange 2010, Exchange 2013 and Exchange 2016 return a zero value.

<16> Section 2.2.3.15: Exchange 2010, Exchange 2013, and Exchange 2016 return a GeneralFailure error if pending changes include changes to read-only properties.

<17> Section 2.2.3.16.1:  Exchange 2010, Exchange 2013, and Exchange 2016 open the message for both reading and writing.

<18> Section 2.2.3.18:  Exchange 2010, Exchange 2013, and Exchange 2016 do not support the RopGetValidAttachments ROP ([MS-OXCROPS] section 2.2.6.18).

<19> Section 3.1.1.1:  Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release version of Outlook 2013 do not support the session context cookie. The session context cookie was introduced in Microsoft Outlook 2013 Service Pack 1 (SP1).

<20> Section 3.2.1.1:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release version of Exchange 2013 do not support the session context cookie. The session context cookie was introduced in Microsoft Exchange Server 2013 Service Pack 1 (SP1).

<21> Section 3.2.5.2: Exchange 2013 and Exchange 2016 do not initialize the following properties: PidTagCreatorName ([MS-OXPROPS] section 2.647), PidTagCreatorEntryId (section 2.2.1.31), PidTagLastModifierName ([MS-OXCPRPT] section 2.2.1.5), PidTagLastModifierEntryId (section 2.2.1.32), PidTagLastModificationTime (section 2.2.2.2), PidTagMessageLocaleId (section 2.2.1.5) and PidTagLocaleId ([MS-OXPROPS] section 2.765). Exchange 2016 does not initialize the following properties: PidTagDisplayBcc ([MS-OXOMSG] section 2.2.1.7), PidTagDisplayCc ([MS-OXOMSG] section 2.2.1.8) and PidTagDisplayTo ([MS-OXOMSG] section 2.2.1.9).

<22> Section 3.2.5.2: In Exchange 2007, the initial MUST be 0x00000009.

<23> Section 3.2.5.2: Exchange 2013 and Exchange 2016 initialize the PidTagAccess property ([MS-OXCPRPT] section 2.2.1.1) to 0x00000007.

<24> Section 3.2.5.2:  In Exchange 2007 and Exchange 2010, the error code is ecNoCreateRight with value 0x000004FF.

<25> Section 3.2.5.3: Exchange 2010, Exchange 2013, and Exchange 2016 return Success for RopSaveChangesMessage ROP requests ([MS-OXCROPS] section 2.2.6.3) when a previous request has already been committed against the Message object, even though the changes to the object are not actually committed to the server message store.

<26> Section 3.2.5.3: Exchange 2010, Exchange 2013, and Exchange 2016 return a GeneralFailure error if pending changes include changes to read-only properties PidTagMessageSize, PidTagAccess, PidTagAccessLevel, PidTagObjectType, PidTagRecordKey, PidTagMessageStatus, and PidTagHasAttachments.

<27> Section 3.2.5.3: Exchange 2010, Exchange 2013, and Exchange 2016 return this value. Exchange 2007 returns Success.

<28> Section 3.2.5.10: Exchange 2003, Exchange 2007, Exchange 2010, Office Outlook 2003, Office Outlook 2007, and Outlook 2010 do not support this behavior. Microsoft Exchange Server 2010 Service Pack 1 (SP1), Exchange 2013, Exchange 2016, Microsoft Outlook 2010 Service Pack 1 (SP1), Outlook 2013, and Outlook 2016 support this behavior.

<29> Section 3.2.5.10: Exchange 2003, Exchange 2007, Exchange 2010, Office Outlook 2003, Office Outlook 2007, and Outlook 2010 do not support this behavior. Exchange 2010 SP1, Exchange 2013, Exchange 2016, Outlook 2010 SP1, Outlook 2013, and Outlook 2016 support this behavior.

<30> Section 3.2.5.13: Exchange 2013 and Exchange 2016 set the PidTagAttachSize property (section 2.2.2.5) to 0x00000000.

<31> Section 3.2.5.13: Exchange 2013 and Exchange 2016 set the PidTagAccessLevel property ([MS-OXCPRPT] section 2.2.1.2) to 0x00000000.

<32> Section 3.2.5.13: Exchange 2013 and Exchange 2016 set the PidTagLastModificationTime property (section 2.2.2.2) to a value that is within 100 nanoseconds of the value of the PidTagCreationTime property (section 2.2.2.3).

Show: