Export (0) Print
Expand All

2.5.11.5 Protocol-Specific Details

Using remote operations (ROPs)

Ee157113.20cada4d-d79d-4858-a42b-72f96eaa51ea(en-us,EXCHG.80).jpg

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 2.2.4.11) with the list of MIDs to be deleted.

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

Using Exchange ActiveSync

Ee157113.365d4908-736c-43f3-a492-cce9c15fb291(en-us,EXCHG.80).jpg

Figure 31: Deleting a message by using Exchange ActiveSync

  1. The client issues a Sync command request ([MS-ASCMD] section 2.2.2.20), with a Delete element, as described in [MS-ASCMD] section 2.2.3.42.2, 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

Ee157113.91d2f974-d69f-44a1-addd-0c7c1a9d7245(en-us,EXCHG.80).jpg

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 3.1.4.3.1.1, 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 3.1.4.3.1.2, which includes a ResponseCode element for the deletion status of each item.

Show:
© 2014 Microsoft