This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 56.00000000000001%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Hello,
I'm using a 3rd party SDK to read ost/olm files, no problem using it, just have a question about the general structure of such ole2 storages?
My 1st question: Found that there are IPF folders in addition to IPM inside PST file:
Should I behave IPF items exactly like IPM counterparts?
ie, save using the same method for both IPM.CONTACT and IPF.CONTACT as contact file?
or IPM.NOTE and IPF.NOTE as message? the same?
My 2nd question would be that according to MS, IPM.Document is for DocumentItem, which can be ANY kind of file, even executable etc
Didn't find its IPF counterpart, but found IPF.DocumentLibrary / IPF.ShortcutFolder which I don't know what's that for? The same as IPM.Document?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 52%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
Hi SSoft-5594,
Thank you for your request. One of our team members will review this and follow-up with you soon.
Regards,
Kristian S
Support Escalation Engineer
Microsoft Open Spec Protocols
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 81%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETJ%3C/text%3E%3C/svg%3E)
Hi @S-Soft ,
I'll look into your questions about IPM vs IPF and IPM.NOTE, CONTACT, Document, etc... wrt MS-OXOSFLD.
Are you implementing the code behind the questions or using the 3rd party SDK implementation only?
Best regards,
Tom Jebo
Microsoft Open Specifications Support
Hello,
Using 3rd party SDK implementation only, but however, to detect the item type, I just can get the MapiItemType (string) and have to compare it against known types as string to detect the real item type
ie if Mapi Item Type String StartsWith "IPM.NOTE"...
But what if it StartsWith "IPF.NOTE"... etc
To clarify, IPM.* is a message object class (e.g. an individual message or contact) and IPF.* is a container class (i.e. folder). So IPM.Note would be the class used for message objects, IPM.Contact for a contact, etc... IPF.Note is the container class for folders (such as Deleted Items, Sent Items, Inbox, etc...) that can contain message objects.
The behavior differences between IPM and IPF class objects is described in MS-OXCFOLD/MS-OXOSFLD and MS-OXCMSG/MS-OXOMSG. However, these documents are targeting implementers using the ROP (Remote Operations) interfaces that Exchange servers support. Since you are using a 3rd party SDK, it might interpret the objects and represent them differently.
Does this help?
Tom
Hello and thank you very much for the info, very helpful, just do you have any idea if a folder is IPF.Note for example, possible to have different class objects in it? ie, IPM.Document inside a IPF.Note/IPF.Post etc or IPM.Note inside IPF.Post
@S-Soft ,
The IPM.POST class is for objects that extend the message object class. So they can be stored in IPF.NOTE folders, however...
In MS-OXOPOST 3.1.1, we specifiy:
and for IPM.Document, MS-OXODOC 3.1.1 states similarly:
I hope this helps,
Tom
@S-Soft ,
I also want to make clear that the answers I've given here are related only to the Open Specifications documents (e.g. MS-OXOSFLD) and implementing code based on these documents. I am not addressing the use of the 3rd party library or its supportability. Perhaps one of the folks supporting the Outlook and Exchange products (and related tags here) can elaborate on that topic.
Tom
@S-Soft ,
And another clarification, I'm not specifically addressing the OST/OLM files that you mentioned in your opening sentence. Although there are similarities to PST, those file are not in scope for the Open Specifications and are cache files direct access to which is not described in our Open Specifications. Again, I'll let others from Outlook and Exchange product and dev support comment further on product supportability of those.
Tom