3.2.5.1 Processing RopGetPropertiesSpecific

When the server receives a RopGetPropertiesSpecific ROP request buffer ([MS-OXCROPS] section 2.2.8.3) from the client, the server parses the buffer. The server responds with a RopGetPropertiesSpecific ROP response buffer. For details about how the server parses buffers and processes ROPs, see [MS-OXCROPS] section 3.2.5.1. For details about how the server formats buffers for the response, see [MS-OXCROPS] section 3.2.5.2.

The server MUST return the values for the explicitly requested properties on the object, including those set by any client, those set by any server, and computed properties. The properties to be returned are specified in the PropertyTags field of the ROP request buffer. The server MUST order properties in the PropertyValues field of the ROP response buffer in the same order in which properties are specified in the PropertyTags field.

If the WantUnicode field is set to a nonzero value, the server MUST return string properties that are requested without a specified type (PtypUnspecified) in Unicode format. If the WantUnicode field is set to zero, the server MUST return string properties that are requested without a specified type (PtypUnspecified) in MBCS format. Properties requested with a specific string type MUST be returned using that type.

For properties on Message objects, the code page used for strings in MBCS format MUST be the code page that was set on the Message object when it was opened. If no code page was set on the Message object, the code page of the Logon object MUST be used. For properties on Attachment objects, the code page used for strings in MBCS format MUST be the code page that was set on the parent Message object when it was opened. If no code page was set on the parent Message object, the code page of the Logon object MUST be used. For all other objects, the code page used for strings in MBCS format MUST be the code page of the Logon object.

The server SHOULD<4> ignore the PropertySizeLimit field of the ROP request buffer.