Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

4.4.1 Client Request Buffer

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

0000: 33 00 00 01 01 00 01 00-00 00 0E 8E EC 5D 00 00

The first four bytes refer to the RopId and LogonID fields, as described in [MS-OXCROPS] section 2.2.4.6.1, and the SourceHandleIndex and DestHandleIndex fields of the RopMoveCopyMessages ROP format, as described in section 2.2.1.6.1.

0000: 33 00 00 01

RopId: 0x33 (RopMoveCopyMessages ROP)

LogonID: 0x00

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

DestHandleIndex: 0x01. The location where the handle for the destination folder is stored.

The following 10 bytes consist of the list of messages to move.

0004: 01 00 01 00 00 00 0E 8E-EC 5D

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

MessageIds: 0001-00000E8EEC5D. MID ([MS-OXCDATA] section 2.2.1.2) of the message to be moved.

The final two bytes in the buffer contain the WantAsynchronous and WantCopy fields, as described in section 2.2.1.6.1.

000E: 00 00

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

WantCopy: 0x00 (FALSE). The operation is a move rather than a copy.

Show:
© 2015 Microsoft