Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
6 Appendix A: Product Behavior

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 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 Exchange 2003 and Exchange 2007 do not set the PidTagConversationTopic property (section

<3> Section Exchange 2003 uses only the PidTagDeferredDeliveryTime property. Exchange 2007, Exchange 2010, and Exchange 2013 use only the PidTagDeferredSendTime property (section

<4> Section Outlook 2010 and Outlook 2013 do not send a RopOptionsDataROP request ([MS-OXCROPS] section

<5> Section 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 Exchange 2013 SP1 and Outlook 2013 SP1.

<6> Section Office Outlook 2007 also uses the PidLidVerbStream property (section 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, Office Outlook 2007 SP1 ignores VoteOption structures with unknown VerbTypes.

<7> Section 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.

<8> Section Office Outlook 2003 and Office Outlook 2007 set the PidTagNextSendAcct property (section to a user-specified value before submitting the message by using the RopSubmitMessageROP ([MS-OXCROPS] section to inform the spooler of the desired mail transport to use.

<9> Section Office Outlook 2003 and Office Outlook 2007 examine the PidTagNextSendAcct property (section

<10> Section Exchange 2007 SP2 returns ecNone (0x00000000) instead of ecNullObject when an invalid object handle reference is passed to the RopGetAddressTypesROP ([MS-OXCROPS] section

<11> Section On Exchange 2003 and Exchange 2007, the RopGetTransportFolderROP ([MS-OXCROPS] section returns ecNone instead of ecNullObject when an invalid input handle is provided.

<12> Section Exchange 2010 and Exchange 2013 will return Success (0x00000000) for the RopSpoolerLockMessageROP ([MS-OXCROPS] section even if the message is not in the spooler queue.

<13> Section Exchange 2007 returns Success (0x00000000) for the RopOptionsDataROP ([MS-OXCROPS] section regardless of whether the call succeeds or fails.

© 2015 Microsoft