2.11.1.2 String Property Values

Clients SHOULD use string properties in Unicode format. When using strings in Unicode format, string data MUST be encoded as UTF-16LE format, and property data types MUST be specified as 0x001F (PtypString) or 0x101F (PtypMultipleString).

Clients can use PtypString8 and PtypMultipleString8 properties in a specific 8-bit or MBCS code page. If they do, property data types MUST be specified as 0x001E (PtypString8) or 0x101E (PtypMultipleString8).

In requests sent to a message store server, the code page of strings MUST match the code page sent to the server in an EcDoConnectEx method call, as specified in [MS-OXCRPC] section 3.1.4.1, or sent to the server using the Connect request type<7>, as specified in [MS-OXCMAPIHTTP] section 2.2.4.1. Address book server-side rules for working with PtypString8 properties are somewhat more involved and are specified in [MS-NSPI].

If the message store is protected with Windows Information Protection, the string type property will look like binary if it is encrypted. The encrypted value has a four-byte prefix and MUST be decrypted properly to get the clear string value. The four-byte prefix SHOULD be used to identify if a property is protected: 0x12, 0x34, 0x56, 0x78.

Show: