Export (0) Print
Expand All Protocol-Specific Details

Using remote operations (ROPs)


Figure 30: Deleting a message by using ROPs

Note  The ROPs are sent via RPC or MAPI extensions for HTTP. Several ROPs can be batched into a single request, as described in [MS-OXCROPS].

  1. The client opens the specified folder per the use case described in section 2.5.9.

  2. The client issues a RopDeleteMessages ROP request ([MS-OXCROPS] section with the list of MIDs to be deleted.

  3. The Exchange server returns the success or failure of the operation.

Using Exchange ActiveSync


Figure 31: Deleting a message by using Exchange ActiveSync

  1. The client issues a Sync command request ([MS-ASCMD] section, with a Delete element, as described in [MS-ASCMD] section, to the server, where each item to be deleted is listed in the schematized XML request body.

  2. The Exchange server responds with HTTP status code 200 (OK) and returns a series of sync status codes, where each corresponds to the deletion status for a message in the deletion list.

Using Exchange Web Services


Figure 32: Deleting a message by using Exchange Web Services

  1. The client uses the HTTPS/SOAP DeleteItemSoapIn request WSDL message, as described in [MS-OXWSCORE] section, to delete items specified in the ItemIds element.

  2. The Exchange Client Access server responds with a DeleteItemSoapOut response WSDL message, as described in [MS-OXWSCORE] section, which includes a ResponseCode element for the deletion status of each item.

© 2014 Microsoft