2.5.7.5 Protocol-Specific Details

Using remote operations (ROPs)

Sending a message by using ROPs

Figure 22: Sending 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 creates a message per the use case described in section 2.5.3.

  2. The client resolves a recipient per the use case described in section 2.5.6.

  3. The client issues a RopModifyRecipients ROP request ([MS-OXCROPS] section 2.2.6.5) to add the recipient to the recipient table for the message.

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

  5. The client issues a RopSaveChangesMessage ROP request ([MS-OXCROPS] section 2.2.6.3) to save the new recipient table.

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

  7. The client issues a RopSubmitMessage ROP request ([MS-OXCROPS] section 2.2.7.1) to submit the message for delivery.

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

Using Exchange Web Services

Sending a message by using Exchange Web Services

Figure 23: Sending a message by using Exchange Web Services

  1. The client uses the HTTPS/SOAP SendItemSoapIn request WSDL message, as described in [MS-OXWSCORE] section 3.1.4.8.1.1, to specify a list of messages in the ItemIds element. It is assumed that that each item specified in the ItemIds element already contains the necessary sender and recipient information.

  2. The Exchange Client Access server responds with a SendItemSoapOut response WSDL message, as described in [MS-OXWSCORE] section 3.1.4.8.1.2, which includes the ResponseCode element specifying the status of the operation.

Show: