PidTagMessageEditorFormat Canonical Property
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
Specifies the format for an editor to use to display a message.
Associated properties: |
PR_MSG_EDITOR_FORMAT |
Identifier: |
0x5909 |
Data type: |
PT_LONG |
Area: |
Miscellaneous |
Remarks
The possible values for PR_MSG_EDITOR_FORMAT can be one of the following:
Value |
Description |
|---|---|
EDITOR_FORMAT_DONTKNOW |
The format for the editor to use is unknown. |
EDITOR_FORMAT_PLAINTEXT |
The editor should display the message in plain text format. |
EDITOR_FORMAT_HTML |
The editor should display the message in HTML format. |
EDITOR_FORMAT_RTF |
The editor should display the message in Rich Text Format. |
By default, mail messages (with the message class IPM.Note or with a custom message class derived from IPM.Note) sent from a POP3/SMTP mail account are sent in the Transport Neutral Encapsulation Format (TNEF). The PR_MSG_EDITOR_FORMAT property can be used to enforce only plain text, and not TNEF, when sending a message. If PR_MSG_EDITOR_FORMAT is set to EDITOR_FORMAT_PLAINTEXT, the message is sent as plain text without TNEF. If PR_MSG_EDITOR_FORMAT is set to EDITOR_FORMAT_RTF, TNEF encoding is implicitly enabled, and the message is sent by using the default Internet format that is specified in the Outlook client.
There are two other ways to enforce the use of TNEF when sending a message.
Setting the dispidUseTNEF (PidLidUseTnef) named property to True on a message indicates TNEF should be included when converting the message from MAPI to MIME/SMTP. Note that dispidUseTNEF only applies when the message is sent from a POP3/SMTP mail account, and does not apply when the message is sent by other providers, such as Microsoft Exchange Server. dispidUseTNEF overrides the setting in PR_MSG_EDITOR_FORMAT.
Using the CCSF_USE_TNEF flag when calling IConverterSession::MAPIToMIMEStm to convert an outgoing MAPI message to a MIME stream can also enforce TNEF. This applies even if dispidUseTNEF is not set.
Related Resources
Protocol Specifications
[MS-OXPROPS]
Provides references to related Exchange Server protocol specifications.[MS-OXCFXICS]
Defines the basic data structures that are used in remote operations.[MS-OXOMSG]
Specifies the properties and operations that are permissible for e-mail message objects.
Header Files
Mapidefs.h
Provides data type definitions.Mapitags.h
Contains definitions of properties listed as alternate names.