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.
<4> Section 188.8.131.52: Office Outlook 2003 does provide a way for the user to set the value of the PidTagReplyRequested ([MS-OXOMSG] section 184.108.40.206) and PidTagResponseRequested ([MS-OXOMSG] section 220.127.116.11) properties on a Task object.
<5> Section 18.104.22.168: In Office Outlook 2007, when swapping the contents of the primary flag storage location and secondary flag storage location, the PidTagReplyRequested ([MS-OXOMSG] section 22.214.171.124) and PidTagResponseRequested ([MS-OXOMSG] section 126.96.36.199) properties do not get updated to the correct value according to the new flagging state of the primary flag storage location.
<8> Section 188.8.131.52: Office Outlook 2007 substitutes the concatenated values of PidTagSubjectPrefix ([MS-OXCMSG] section 184.108.40.206) and PidTagNormalizedSubject ([MS-OXCMSG] section 220.127.116.11) when displaying a Message object without a value in the PidLidToDoTitle property.
<9> Section 18.104.22.168: Exchange 2003 and Office Outlook 2003 do not read or write the PidLidToDoOrdinalDate property.
<13> Section 22.214.171.124: The default Outlook user interface does not permit users to flag Appointment objects, Journal objects, or Note objects, but it is possible to manipulate the UI in nonstandard ways in order to set flag-related properties on such objects. Flagging Appointment objects, Journal objects, or Note objects will result in undefined behavior.
<17> Section 126.96.36.199.4: In addition to the exceptions as noted for individual properties, Exchange 2003 and Office Outlook 2003 do not set the following properties when marking a Message object complete: PidTagToDoItemFlags (section 188.8.131.52), PidLidToDoTitle (section 184.108.40.206), PidLidToDoOrdinalDate (section 220.127.116.11), PidLidToDoSubOrdinal (section 18.104.22.168), PidLidTaskDateCompleted ([MS-OXOTASK] section 22.214.171.124.9), PidLidTaskComplete ([MS-OXOTASK] section 126.96.36.199.20), PidLidTaskStatus ([MS-OXOTASK] section 188.8.131.52.2), and PidLidPercentComplete (section 184.108.40.206). Becuase Exchange 2003 and Office Outlook 2003 also do not set the PidTagFlagStatus property (section 220.127.116.11) for a meeting-related object, Exchange 2003 and Office Outlook 2003 do not support complete flags for a meeting-related object.
<18> Section 18.104.22.168.6: Office Outlook 2003 does not support sender flags. Only recipient flags can be set in Office Outlook 2003.
<19> Section 22.214.171.124: Exchange 2003 and Office Outlook 2003 do not support sender flags, and thus do not support post-transmit processing of a flagged message.