Export (0) Print
Expand All

3.2 PropertyRow Example

In this example, the client sends the RopGetPropertiesSpecificROP ([MS-OXCROPS] section 2.2.8.3) to the server requesting the properties from an open Message object.

Hexadecimal value

Property ID

Property type

0E070003

PidTagMessageFlags ([MS-OXCMSG] section 2.2.1.6)

PtypInteger32

00370001

PidTagSubject ([MS-OXCMSG] section 2.2.1.46)

PtypUnspecified

1000001F

PidTagBody ([MS-OXCMSG] section 2.2.1.56.1)

PtypString

For this example, it is also assumed that:

  • This message had been sent to this mailbox from a different user.

  • The message contained an attachment.

  • The message had already been read by the user but had not been modified.

  • The subject of this message is "Hello".

  • The body of the message is so large that the server requires the client to stream the body to the client.

Under these conditions, the data returned from the server for the PropertyRow structure, as described in section 2.8, would use the FlaggedPropertyRow structure variant, as described in section 2.11.5, to return the data from the RopGetPropertiesSpecific ROP with the data shown in the following table.

Bytes

Field

Meaning

01

Flag for the PropertyRow structure

Either there were errors retrieving values or some values were not returned.

00

Flag for the FlaggedPropertyValue structure, as described in section 2.11.5

The value for this property is returned.

13 00 00 00

PtypInteger32 PropertyValue

MSGFLAG_READ

|MSGFLAG_UMODIFIED

|MSGFLAG_HASATTACH

1F 00

PropertyType for the FlaggedPropertyValueWithType structure, as described in section 2.11.6

PtypString

00

Flag for the FlaggedPropertyValueWithType structure

PropertyRestriction

48 00 65 00 6C 00 6C 00 6F 00 00 00

String PropertyValue

"Hello"

0A

Flag for the FlaggedPropertyValue structure

The value 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 2.4.

Show:
© 2014 Microsoft