Export (0) Print
Expand All

4.3.1 Client Request Buffer

The client request buffer for the RopDeleteMessagesROP ([MS-OXCROPS] section 2.2.4.11) example consists of a 23-byte sequence, formatted as follows.

0000: 1E 00 00 00 01 02 00 01-00 00 00 0E 8E F1 48 01
0010: 00 00 00 0E 8E C3 02

The first five bytes refer to the RopId and LogonID fields, as specified in [MS-OXCROPS] section 2.2.4.11.1, and the InputHandleIndex, WantAsynchronous, and NotifyNonRead fields of the RopDeleteMessages ROP format, as specified in section 2.2.1.11.1.

0000: 1E 00 00 00 01

RopId: 0x1E (RopDeleteMessages ROP)

LogonID: 0x00

InputHandleIndex: 0x00. The location where the handle for the messages' parent folder is stored.

WantAsynchronous: 0x00 (FALSE). The ROP is executed synchronously.

NotifyNonRead: 0x01 (TRUE). The client wants a notification if a message was deleted before it was read.

The remaining bytes in the buffer consist of the list of messages to delete.

0005: 02 00 01 00 00 00 0E 8E-F1 48 01 00 00 00 0E 8E
0015: C3 02

MessageIdCount: 0x0002. This value indicates how many messages are listed for deletion in the MessageIds field.

MessageIds:

0001-00000Ee8EF148. MID ([MS-OXCDATA] section 2.2.1.2) of a message to be deleted.

0001-00000E8EC302. MID of a message to be deleted.

Show:
© 2014 Microsoft