PST名称-ID映射的详细信息 [英] PST name-id-map specifics

问题描述

pst的规范提到名称-id-map每pst个一个. 该映射可能包含其规范 MS-OXPROPS ，但从外观上看，大多数这些pidlid属性似乎都是特定于消息的. 如何在此name-id-map中存储/管理每封邮件的属性?

The spec for pst mentions that the name-id-map is one per pst. This map may contain several pidlid properties as defined in their spec MS-OXPROPS, but from the looks of it most of these pidlid properties appear to be message specific. How are properties for each message stored/managed in this name-id-map ?

推荐答案

否，消息存储4字节的属性标签.例如. PR_SUBJECT_A(这不是命名属性，因此不需要进行映射)为0x0037001E.

No, the messages store the 4 byte property tags. E.g. PR_SUBJECT_A (which is not a named property and hence does not need to be mapped) is 0x0037001E.

仅当客户端调用IMAPIProp :: GetIDsFromNames和IMAPIProp :: GetNamesFromIDs时才需要该地图.在前一种情况下，您获得了GUID和ID(字符串或整数)，并且需要查找与该GUID/id组合相对应的4个字节(或者由于较低的2个字节是prop类型，所以查找2个字节)prop标签. .如果是GetNamesFromIDs，则进行反向查找-给定prop标签，返回GUID/id.

The map is needed only if a client calls IMAPIProp::GetIDsFromNames and IMAPIProp::GetNamesFromIDs. In the former case, you get the GUID and the id (either string or an int) and you need to lookup the 4 byte (or rather 2 bytes since the lower 2 bytes are prop type) prop tag corresponding to that GUID/id combination. In case of GetNamesFromIDs, you do reverse lookup - given the prop tag, return the GUID/id.

这篇关于PST名称-ID映射的详细信息的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！