18.104.22.168 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)
Figure 9: Creating a message by using ROPs
The client issues a RopCreateMessage ROP request ([MS-OXCROPS] section 22.214.171.124) to the Exchange server referencing the folder.
The Exchange server responds with a handle to the message.
Using the message object handle returned by the server, as described in [MS-OXCROPS] section 126.96.36.199.2, the client issues a RopSaveChangesMessage ROP request ([MS-OXCROPS] section 188.8.131.52) to the server to persist the message to storage.
The server returns the MID for the new message.
Using Exchange ActiveSync
Figure 10: Creating a message by using Exchange ActiveSync
The client uses the Sync command request ([MS-ASCMD] section 184.108.40.206) with an Add element, as described in [MS-ASCMD] section 220.127.116.11.2, to upload/create new application data on the server. An ApplicationData element, as described in [MS-ASCMD] section 18.104.22.168, with class "E-mail" needs to contain the required XML schema elements, as described in [MS-ASEMAIL].
The Exchange server responds with HTTP status code 200 (OK).
Using Exchange Web Services
Figure 11: Creating a message by using Exchange Web Services
The Client Access server responds with a CreateItemSoapOut response WSDL message, as described in [MS-OXWSMSG] section 22.214.171.124, which includes the ResponseCode element, indicating the status of the operation, and the ItemId element, whose value uniquely identifies the new message.