2.1.3.2.2 Content Class

MIME writers SHOULD generate the following values for a Content-Class header, based on the value of the PidTagMessageClass property ([MS-OXCMSG] section 2.2.1.3).<23>

PidTagMessageClass property value

Content-class header value

"IPM.Note.Microsoft.Fax"

"fax".

"IPM.Note.Microsoft.Fax.CA"

"fax-ca". A MIME writer MAY<24> write a value of "fax".

"IPM.Note.Microsoft.Missed.Voice"

"missedcall".

"IPM.Note.Microsoft.Conversation.Voice"

"voice-uc".

"IPM.Note.Microsoft.Voicemail.UM.CA"

"voice-ca". A MIME writer MAY<25> write a value of "voice".

"IPM.Note.Microsoft.Voicemail.UM"

"voice".

PidTagMessageClass property prefix

Content-class header value

"IPM.Note.Custom."

"urn:content-class:custom.", followed by the value of the PidTagMessageClass property with the "IPM.Note.Custom." prefix removed.

"IPM.InfoPathForm."

If the PidLidInfoPathFormName property ([MS-OXPROPS] section 2.149) has some value, the Content-class header SHOULD be generated with the value of "InfoPathForm.", followed by a string, which is generated as follows:

MIME writers SHOULD take the value of the PidTagMessageClass property and remove the "IPM.InfoPathForm." prefix.

If the remaining string contains a '.' symbol, the value SHOULD be truncated before the period '.'.

The value of the PidLidInfoPathFormName property SHOULD be appended to this string, preceded by a '.' character.

If the MIME writer was unable to find a mapping between the value of the PidTagMessageClass property and a value of the Content-class header, it SHOULD look up the value of the PidNameContentClass property ([MS-OXCMSG] section 2.2.1.48). If this property has a value, that value SHOULD be used as the value of the Content-class header; otherwise, a header SHOULD NOT be generated.