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 22.214.171.124: The computation of the value of the PidTagConversationId property is not supported by Exchange 2003, Exchange 2007, Office Outlook 2003, and Office Outlook 2007.
<2> Section 126.96.36.199: Exchange 2007, Exchange 2010, Office Outlook 2007, Outlook 2010, Outlook 2013 and Outlook 2016 compute the PidTagConverationIndex property for messages using a different algorithm. When computing the Current FILETIME field, the 24 low bits of the high part and the 16 high bits of the low part of the FILETIME are included in Current FILETIME high part and Current FILETIME low part, as shown in the following table.
Eight most significant bits
16 least significant bits
<3> Section 188.8.131.52: Exchange 2013 and Exchange 2016 set the Delta Code field to 1 and do not calculate the Time Delta field based on TimeDiff.
<5> Section 184.108.40.206: Exchange 2003 uses only the PidTagDeferredDeliveryTime property. Exchange 2007, Exchange 2010, Exchange 2013, and Exchange 2016 use only the PidTagDeferredSendTime property (section 220.127.116.11).
<7> Section 18.104.22.168: Exchange 2003, Exchange 2007, Exchange 2010, the initial release version of Exchange 2013, 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 Exchange Server 2013 Service Pack 1 (SP1) and Microsoft Outlook 2013 Service Pack 1 (SP1).
<8> Section 22.214.171.124.2: Office Outlook 2007 also uses the PidLidVerbStream property (section 126.96.36.199) for actions unrelated to voting that are not covered by this protocol. Each of these actions has a specific VerbType associated with it. The format of the VoteOption structure is identical for these actions that are unrelated to voting; however, the internal values that are specific in the structure will vary. Future versions of Outlook might further define additional VerbTypes; it is therefore advised that clients ignore VoteOption structures that do not specify VerbTypes that they understand. Likewise, Microsoft Office Outlook 2007 Service Pack 1 ignores VoteOption structures with unknown VerbTypes.
<9> Section 188.8.131.52.4: Office Outlook 2007 uses a system similar to meeting responses in order to track voting options. When it receives a voting response, it finds the initial voting message in the Sent Items folder. It then updates the recipient table for the recipient (2) who sent the response to store the index of their response. If the user opens a voting message from the Sent Items folder, it then sums the total of each response received thus far from the recipient table and displays it to the user.
<10> Section 184.108.40.206: Office Outlook 2003 and Office Outlook 2007 set the PidTagNextSendAcct property (section 220.127.116.11) to a user-specified value before submitting the message by using the RopSubmitMessage ROP ([MS-OXCROPS] section 18.104.22.168) to inform the spooler of the desired mail transport to use.
<11> Section 22.214.171.124: Office Outlook 2003 and Office Outlook 2007 examine the PidTagNextSendAcct property (section 126.96.36.199).
<12> Section 188.8.131.52: Microsoft Exchange Server 2007 Service Pack 2 (SP2) returns ecNone (0x00000000) instead of ecNullObject when an invalid object handle reference is passed to the RopGetAddressTypes ROP ([MS-OXCROPS] section 184.108.40.206).
<14> Section 220.127.116.11: Exchange 2010, Exchange 2013, and Exchange 2016 will return Success (0x00000000) for the RopSpoolerLockMessage ROP ([MS-OXCROPS] section 18.104.22.168) even if the message is not in the spooler queue.
<15> Section 22.214.171.124: Exchange 2007 returns Success (0x00000000) for the RopOptionsData ROP ([MS-OXCROPS] section 126.96.36.199) regardless of whether the call succeeds or fails.