Revision Summary Date Revision History Revision Class Comments 4/4/2008 0.1.0 Initial Availability. 4/25/2008 0.2.0 Minor Revised and updated property names and other technical content. 6/27/2008 1.0.0 Major Initial Release. 8/6/2008 1.01 Editorial Revised and edited technical content. 9/3/2008 1.02 Editorial Revised and edited technical content. 12/3/2008 1.03 Editorial Revised and edited technical content. 4/10/2009 2.0.0 Major Updated technical content and applicable product releases. 7/15/2009 3.0.0 Major Revised and edited for technical content. 11/4/2009 3.1.0 Minor Updated the technical content. 2/10/2010 4.0.0 Updated and revised the technical content. 5/5/2010 4.1.0 Minor Updated the technical content. 8/4/2010 5.0 Major Significantly changed
the technical content. 11/3/2010 5.1 Minor Clarified the meaning of the technical content. 3/18/2011 5.2 Minor Clarified the meaning of the technical content. 8/5/2011 6.0 Major Significantly changed the technical content. 10/7/2011 7.0 Major Significantly changed the technical content. 1/20/2012 8.0 Major Significantly changed the technical content. 4/27/2012 8.0 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 9.0 Major Significantly changed the technical content. 10/8/2012 9.1 Minor Clarified the meaning of the technical content. 2/11/2013 9.2 Minor Clarified the meaning of the technical content.
7/26/2013 10.0 Major Significantly changed the technical content. 11/18/2013 11.0 Major Significantly changed the technical content. 2/10/2014 11.0 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 11.0 None No changes to the meaning, language, or formatting of the technical content. 7/31/2014 12.0 Major Significantly changed the technical content. 10/30/2014 12.1 Minor Clarified the meaning of the technical content. 3/16/2015 13.0 Significantly changed the technical content. 5/26/2015 13.0 None No changes to the meaning, language, or formatting of the technical content. 9/14/2015 13.0 None No changes to the
meaning, language, or formatting of the technical content. 6/13/2016 13.0 None No changes to the meaning, language, or formatting of the technical content. 9/14/2016 13.0 None No changes to the meaning, language, or formatting of the technical content. 5/9/2017 13.1 Clarified the meaning of the technical content. 6/20/2017 13.1 None No changes to the meaning, language, or formatting of the technical content.
property or column is not the type expected by the server. (MAPI_E_UNEXPECTED_TYPE, ecPropType) TooBig Indicates that the result set of the operation is too big for the server to return. (MAPI_E_TOO_BIG, ecTooBig) 0x80040305, %x05.03.04.80 DeclineCopy On a copy operation, indicates that the server cannot copy the object, possibly because the source and destination are on different types of servers, and the server will delegate the copying to client code. (MAPI_E_DECLINE_COPY) 0x80040306, %x06.03.04.80 UnexpectedId On get or set, indicates that the server does not support in this range, usually the ID range (from 0x8000 through 0xFFFF). (MAPI_E_UNEXPECTED_ID) 0x80040307, %x07.03.04.80 Warning Warning codes indicate that while the operation as a whole was processed successfully by the server, individual items or properties were not processed successfully. For example, if three properties are requested from a in a RopGetPropertiesSpecific ( section 2.2.8.3) and one of the three properties does not exist on the Message object, then in the response buffer: The returns an ErrorsReturned warning, as specified in the following table. The type in the of the missing property is PtypErrorCode (section ). The property value of the missing property is NotFound, as specified in section . Warning codes are presented in the following table. Warning code name Description (alternate names) Numeric value (hex) ErrorsReturned A request involving multiple properties failed for one or more individual properties, while succeeding overall. (MAPI_W_ERRORS_RETURNED, ecWarnWithErrors) 0x00040380, %x80.03.04.00 PositionChanged A table operation succeeded, but the bookmark specified is no longer set at the same row as when it was last used. (MAPI_W_POSITION_CHANGED, ecWarnPositionChanged) 0x00040481, %x81.04.04.00
element is interpreted as a number, limited by the operating system limits, which can optionally contain a leading sign, fractional digits, and an exponent. Example: <element... d:dt="number">-123.456E+10</element> PtypTime dateTime The Unicode value of the element is interpreted as a date and time value expressed in the format specified in with no time zone specified. As specified in [ISO-8601] Example: <element... PtypTime dateTime.tz The Unicode value of the element is interpreted as a date and time value expressed in the format specified in [ISO-8601] with an optional time zone identifier. As specified in [ISO-8601] Example: <element... <element... PtypTime The Unicode value of the element is interpreted as a date and time value expressed in the format As specified in [RFC1123] Example: <element... d:dt="datetime.rfc1123">Mon, 15 Feb 1999 13:05:29-0700</element>
specified in . PtypTime Date The Unicode value of the element is interpreted as a date value that is expressed in the format specified in [ISO-8601] with no time or time zone specified. As specified in [ISO-8601] Example: <element... d:dt="date">2008-09-18</element> PtypTime time The Unicode value of the element is interpreted as a time value expressed in the format specified in [ISO-8601] with no date or time zone specified. As specified in [ISO-8601] Example: <element... d:dt="time">19T18:53:47.060</element> PtypTime time.tz The Unicode value of the element is interpreted as a time value expressed in the format specified in [ISO-8601] with an optional time zone identifier. As specified in [ISO-8601] Example: <element... d:dt="time.tz">19T18:53:47.060Z</element> <element... PtypString uri The Unicode value of the element is interpreted as a as specified in . As specified in [RFC3986] Example: <element... d:dt="uri">http://www.example.com/</element> PtypGuid uuid The Unicode value of the As specified in [RFC4122]
00 00 Pad Zero 04 RestrictType PropertyRestriction 05 RelOp RelationalOperatorNotEqual 20 10 09 0E PropTag PidTagParentEntryId TaggedValue PtypBinary 0E 02 COUNT 46 Interpreted as Folder EntryID 00 00 00 00 Flags Zero EE C1 BD 78 61 11 D0 11 91 7B 00 00 00 00 00 01 Provider UID UID for mailbox 01 00 FolderType eitLTPrivateFolder (16-byte GUID specific to database) DatabaseGuid UID identifies database where folder was originally created (6 bytes identifying Conflicts folder) GlobalCounter UID identifies specific folder within database 00 00 Pad Zero 04 RestrictType PropertyRestriction 05 RelOp RelationalOperatorNotEqual 20 10 09 0E PropTag PidTagParentEntryId TaggedValue PtypBinary 0E 02 46 Bytes Interpreted as Folder EntryID 00 00 00 00 Zero EE C1 BD 78 61 11 D0 11 91 7B 00 00 Provider UID UID for mailbox
6F 00 00 00 0A Flag for the FlaggedPropertyValue structure The for this property was not returned. The RopOpenStream ROP ([MS-OXCROPS] section 2.2.8.6) can be used to obtain the property value. 0E 00 07 80 32-bit SCODE NotEnoughMemory error, as described in section .
Index A 26 15 15 15 105 105 105 14 B 115 115 115 C 134 119 113 113 114 27 107 107 109 120 E 15 29 29 31 35 74 75 123 129 123 117 117 118 F 14 83 102 102 78 30 30 79 79 20 16 G 18 17 7 I 131 131 13 7 L 14 17 M 21 16 19 N 18 12 107 107 107 O 24 106 106 106 13 P 131 28 132 89 74 79 110 88 100 89 80 80 81 110 112 129 82 83 84 83 84 88
88 89 100 101 R 24 85 RecipientRow structure ( 84, 86) 12 13 12 14 123 103 S Security 131 131 116 116 117 120 121 82 22 Structures 26 15 15 15 105 105 105 115 115 115 119 113 113 114 27 107 107 109 120 15 29 117 117 118 83 102 102 78 30 30 79 79 20 16 18 17 17 21 16 19 18 107 107 107 24 106 106 106 28 79 110 88 100 80 80 81 110 112 82 83 84 83 84 88 88 89 100 101 24 85 RecipientRow structure ( 84, 86) 103 116 116 117 120 121 82 22 118 118 119 120 101 101 103 118 118 119 T 120 101 134 101 103 V