Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

3.2 Client Details

Before using this protocol, the client SHOULD use the OAB Retrieval Protocol. as specified in [MS-OXWOAB], if it is available.<9>

Clients get the entry ID of their OAB folder (the one that contains OAB version 2 and OAB version 4 subfolders) during the RopLogon call ([MS-OXCSTOR] section 2.2.1.1) when they connect to the public foldermessage store. This folder is the OAB data folder of the local site, as described in the public folder IDs of the RopLogon request and response syntax. The client SHOULD use the OAB data folder of the local site as the Root folder to start finding its OAB messages. Note that the client SHOULD first check for the existence of the subfolder "OAB version 4" and use OAB version 4 if that subfolder exists. If it does not exist, the client SHOULD then check for the existence of the subfolder "OAB version 2" and use OAB version 2 if that subfolder exists. The client SHOULD ignore any other subfolders. The client relies on an understanding of the ROPs in [MS-OXCFOLD] to open the folder and retrieve the hierarchy or contents table, the ROPs in [MS-OXCTABL] to perform table operations on the hierarchy or contents table to find the subfolders with the hard-coded names, and the ROPs in [MS-OXCMSG] to retrieve the messages in each of these folders.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.