Revision Summary Date Revision History Revision Class Comments 4/4/2008 0.1 Major Initial Availability. 4/25/2008 0.2 Minor Revised and updated property names and other technical content. 6/27/2008 1.0 Major Initial Release. 8/6/2008 1.0.1 Editorial Revised and edited technical content. 9/3/2008 1.0.2 Editorial Revised and edited technical content. 12/3/2008 1.0.3 Editorial Revised and edited technical content. 4/10/2009 2.0 Updated technical content for new product releases. 7/15/2009 3.0 Major Revised and edited for technical content. 11/4/2009 3.1.0 Minor Updated the technical content. 2/10/2010 3.2.0 Updated the technical content. 5/5/2010 3.3.0 Minor Updated the technical content. 8/4/2010 3.4 Minor Clarified the meaning of the
2/11/2013 6.1 Minor Clarified the meaning of the technical content. 7/26/2013 7.0 Major Significantly changed the technical content. 11/18/2013 8.0 Significantly changed the technical content. 2/10/2014 8.0 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 8.1 Minor Clarified the meaning of the technical content. 7/31/2014 8.2 Minor Clarified the meaning of the technical content. 10/30/2014 8.3 Minor Clarified the meaning of the technical content. 3/16/2015 9.0 Major Significantly changed the technical content. 5/26/2015 10.0 Major Significantly changed the technical content. 9/14/2015 10.0 None No changes to the meaning, language,
or formatting of the technical content. 6/13/2016 10.0 None No changes to the meaning, language, or formatting of the technical content. 9/14/2016 10.0 None No changes to the meaning, language, or formatting of the technical content.
MUST NOT use it. r3 (3 bytes): Reserved. The application can set these flags to any value when writing the subproperty. The application MUST ignore these flags when reading the subproperty, but it MUST preserve preexisting values if it rewrites the subproperty. SearchFolderID If the Id field is set to SearchFolderID, the value of the Data field is a 16-byte field. When the application creates a persistent , as specified in section 2.2.1, it MUST set this field on the folder to the same value as the PidTagSearchFolderId property ([MS-OXOSRCH] section 2.2.1.2.1) on the message. ToDoFolderVersion If the Id field is set to ToDoFolderVersion, the value of the Data field is a 4-byte field. When the application creates the To-Do Search folder as specified in section 3.1.4.1.2, it MUST be a bitmask that indicates which stream properties exist on the message. The stream types, and thus the flags, are not mutually exclusive, which corresponds to the little-endian integer value of 0x000C0000. 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Conversation Actions Conversation actions are a limited set of that a user applies to all E-mail objects, currently in the or delivered in the future, that share the same value of the PidTagConversationId property ( section 2.2.1.2) and thus are part of the same conversation. Unlike , as specified in , at most one conversation action applies to any given E-mail object, and conversation actions can be automatically deleted after a period of disuse. A conversation action is a combination of any of the following actions: Ignore Stop Ignoring Move to Folder Move to Store Stop Move Add Category Remove Category Clear All Categories
A Abstract data model 63 75 15 B 18 C 15 100 Client 63 63 75 63 Client - higher layer triggered events 69 69 63 68 71 67 65 69 72 67 Client - message processing 73 74 Client - sequencing 73 74 75 Configuration data 18 22 Configuration data example 80 80 80 18 Configuration data properties 16 17 17 16 91 54 55 55 55 55 56 56 56 56 57 57 D Data - abstract 63 75 18 E Examples - configuration data 80 80 80 91 Examples – navigation shortcut 92 93 Examples – view definitions 82 82 90 F 15 52 52 G 8 H Higher layer triggered events - client 69 69 63 68 71 67 65 69 72 67 Higher layer triggered events - server 77 75 76 76 76 76 I 95 95 13 Initialization 63