Share via

3.2.5.8.1.3 Receiving a RopFastTransferSourceCopyMessages ROP Request

  • Article

When the client sends the server a RopFastTransferSourceCopyMessages ROP (section 2.2.3.1.1.3) request, the server MUST parse the request, as specified in [MS-OXCROPS] section 2.2.12.6.1 and section 2.2.3.1.1.3 of this specification. The server MUST respond with a RopFastTransferSourceCopyMessages ROP response, as specified in [MS-OXCROPS] section 2.2.12.6.2 and section 2.2.3.1.1.3 of this specification.

If the Move flag of the CopyFlags field is set for a download operation, the server SHOULD NOT output any objects in a FastTransfer stream that the client does not have permissions to delete.

If the BestBody flag of the CopyFlags field is set, the server SHOULD output the message body, and the body of the Embedded Message object, in their original format. The original format of the message is determined by using the best body algorithm, as specified in [MS-OXBBODY] section 2.1.3.1.

If the BestBody flag of the CopyFlags field is not set, the server MAY<36> output message bodies in the compressed RTF.

If the SendEntryId flag of the CopyFlags field is set, the server does not remove message and change identification information from the output.

If the SendEntryId flag of the CopyFlags field is not set, the server removes message and change identification information from the output.

For details about server behavior related to the Unicode, ForceUnicode, and UseCpid flags of the SendOptions field, see section 3.2.5.8.1.1.

Servers SHOULD fail the ROP if any unknown flags in the SendOptions field are set.