Share via

3.3.5.8.11 Sending a RopSynchronizationImportReadStateChanges ROP Request

  • Article

Clients SHOULD expect this ROP to fail if any read state changes on the objects passed in the request buffer fail. The possibility of a failure is higher when the user has lower privileges to a mailbox; this is especially a consideration for delegate and public folder access. Clients that use this ROP SHOULD have a strategy to retry this operation, which can be a combination of the following steps:

  • Retry the ROP with the same arguments on a new synchronization upload context.

  • Retry the ROP, passing one ID at a time.

  • Retry the ROP by using online mode ROPs, such as the RopSetMessageReadFlag ROP ([MS-OXCROPS] section 2.2.6.11).

  • Perform the ICS download, resolving server changes against their own pending synchronization upload context.

  • Skip an object and undo the operation in the local replica.