Export (0) Print
Expand All

5 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.2: Exchange 2007 and Exchange 2010 do not support the NNTP Newsgroup Folder EntryID structure.

<2> Section 2.2.4: The value for the MappedPublicFolder Store object type is neither read nor written to by the server. Only Office Outlook 2003, Office Outlook 2007, and Outlook 2010 use this object type.

<3> Section 2.2.4: The value for the MappedPublicMessage Store object type is neither read nor written to by the server. Only Office Outlook 2003, Office Outlook 2007, and Outlook 2010 use this object type.

<4> Section 2.2.5.3: Office Outlook 2003 and Office Outlook 2007 can leave 3 extra bytes not filled at the end of the Contact Address EntryID structure; in other words, the sum of all fields specified in this protocol can be 3 bytes less than the count of bytes of the entire EntryID. The value of the extra 3 bytes has no meaning to either the server or the client.

<5> Section 2.2.5.4: Office Outlook 2003 and Office Outlook 2007 can leave 3 extra bytes not filled at the end of the Personal distribution list EntryID structure; in other words, the sum of all fields specified in this protocol can be 3 bytes less than the count of bytes of the entire EntryID. The value of the extra 3 bytes has no meaning to either the server or the client.

<6> Section 2.8.3.1: Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Connect request type. The Connect request type was introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<7> Section 2.11.1.2: Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Connect request type. The Connect request type was introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<8> Section 2.12.5.1: Exchange 2003, Exchange 2007, Office Outlook 2003, Office Outlook 2007, and Outlook 2010 support the RelationalOperatorEqual and RelationalOperatorNotEqual operators when the value of the PropTag field is single-valued and the value of the TaggedValue field is multivalued. The value of the property PropTag field is compared with each value of the TaggedValue field. If there are any matches, the RelationalOperatorEqual operator is satisfied. If there are no matches, the RelationalOperatorNotEqual operator is satisfied.

Show:
© 2014 Microsoft