Export (0) Print
Expand All

2.5.3.5 Protocol-Specific Details

The requests and responses below are separated to facilitate understanding conceptual communication flow and are for illustration purposes only. This same convention will be used for the use cases hereinafter.

Using remote operations (ROPs)

MS-OXPROTO_pictd3f97ea8-0a19-4024-98b7-f5280063ba8d.png

Figure 9: Creating 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 logs on to a mailbox per the use case described in section 2.5.2.

  2. The client issues a RopCreateMessage ROP request ([MS-OXCROPS] section 2.2.6.2) to the Exchange server referencing the folder.

  3. The Exchange server responds with a handle to the message.

  4. Using the message object handle returned by the server, as described in [MS-OXCROPS] section 2.2.6.2.2, the client issues a RopSaveChangesMessage ROP request ([MS-OXCROPS] section 2.2.6.3) to the server to persist the message to storage.

  5. The server returns the MID for the new message.

Using Exchange ActiveSync

MS-OXPROTO_pict403d54bd-f3a5-4f0e-92b9-e48bf3fc689a.png

Figure 10: Creating a message by using Exchange ActiveSync

  1. The client uses the Sync command request ([MS-ASCMD] section 2.2.2.20) with an Add element, as described in [MS-ASCMD] section 2.2.3.7.2, to upload/create new application data on the server. An ApplicationData element, as described in [MS-ASCMD] section 2.2.3.11, with class "E-mail" needs to contain the required XML schema elements, as described in [MS-ASEMAIL].

  2. The Exchange server responds with HTTP status code 200 (OK).

Using Exchange Web Services

MS-OXPROTO_pict65cf9bac-6258-48fd-99bd-856b9d180596.png

Figure 11: Creating a message by using Exchange Web Services

  1. The client uses the HTTPS/SOAP CreateItemSoapIn request WSDL message, as described in [MS-OXWSMSG] section 3.1.4.2, to create a new message item in the specified folder.

  2. The Client Access server responds with a CreateItemSoapOut response WSDL message, as described in [MS-OXWSMSG] section 3.1.4.2, which includes the ResponseCode element, indicating the status of the operation, and the ItemId element, whose value uniquely identifies the new message.

Show:
© 2015 Microsoft