3.3.5.8.7 Sending a RopSynchronizationImportMessageChange ROP Request

When uploading new messages, clients SHOULD add their Message ID structures ([MS-OXCDATA] section 2.2.1.2) to the MetaTagIdsetGiven property (section 2.2.1.1.1) value upon successful completion of this ROP.

Note that because a server returns an empty message from the RopSynchronizationImportMessageChange ROP ([MS-OXCROPS] section 2.2.13.2), even when uploading changes to an existing message, this ROP can only be used to perform upload of full message changes or new messages. In order for the client to upload partial message changes, it SHOULD take them outside the synchronization upload operation, by initiating an upload by using the RopOpenMessage ROP ([MS-OXCROPS] section 2.2.6.1) followed by other ROPs discussed in [MS-OXCMSG], such as the RopSetProperties ROP ([MS-OXCROPS] section 2.2.8.6) and the RopModifyRecipients ROP ([MS-OXCROPS] section 2.2.6.5). However, these ROPs do not let the client set values to any of the properties that the RopSynchronizationImportMessageChange ROP accepts.

The RopSynchronizationImportMessageChange ROP returns the handle of a Message object, which the client MUST populate with the contents of the message. The client populates the Message object by sending the ROPSetProperties ROP, the ROPCreateAttachment ROP ([MS-OXCROPS] section 2.2.6.13), and other ROPs required to populate the message contents, as specified in [MS-OXCMSG] section 3.1.4, followed by the ROPSaveChangesMessage ROP ([MS-OXCROPS] section 2.2.6.3).

For details about the client behavior when receiving a response to this ROP, see section 3.3.5.9.