You cannot send plain text only messages by using Extended MAPI

When you try to send a plain text e-mail message by using Extended MAPI with a POP3/SMTP mail account, the message may be sent with a Winmail.dat Transport Neutral Encapsulation Format (TNEF) attachment.

This problem occurs because there is no mechanism in Outlook 2002 to specify that a non IPM.Note message be sent as plain text instead of the default rich text message type that uses TNEF.

Service Pack Information

This problem is corrected in Office XP Service Pack 3. To resolve this problem, obtain the latest service pack for Microsoft Office XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix should have the following file attributes or later: After the hotfix is installed, the English version of this fix will have the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. This fix is a post-Office XP Service Pack 2 (SP-2) fix. To install the fix, you must have Office XP SP-2 installed. For additional information about Office XP SP-2, click the following article number to see the article in the Microsoft Knowledge Base: Additionally, you may have to install Windows Installer 2.0 to install this fix. For additional information about the Windows Installer requirement for post-Office XP SP-2 fixes, click the following article number to see the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Office XP Service Pack 3.

Before this fix, the PR_MSG_EDITOR_FORMAT property might be used to enforce plain text and no TNEF with IPM.Note messages. However, if the message had a custom message class, this property was ignored. This fix makes it possible for this property to be accepted with all message classes that inherit from IPM.Note.

Definition of the Property and Valid Values

The only values that are accepted for content conversion are EDITOR_FORMAT_PLAINTEXT and EDITOR_FORMAT_RTF. For a message of class IPM.Note.* if this property is set to EDITOR_FORMAT_PLAINTEXT, the message is sent as plain text without TNEF. If it is set to EDITOR_FORMAT_RTF, the message is sent by using the default Internet Format that is specified in the Outlook client. Any other setting is not accepted.

Additionally, under certain circumstances, such as when voting buttons have been enabled or an OLE embedded object has been attached to a message, Outlook can set a named property to force the use of TNEF. This named property will override the setting in PR_MSG_EDITOR_FORMAT. Therefore, an Outlook add-in that wants to force plain text on outgoing messages should also look for this named property and reset it to FALSE. Additionally, the add-in must remove the message features that required TNEF to avoid unusable attachments on the message that is finally sent. The named property is ulKind: MNID_ID lID: 0x8582 lpguid: {00062008 - 0000 - 0000 - C000000000000046} Type: PT_BOOLEAN. In order to set or check this property from MAPI, GetIDsFromNames is used to obtain a property ID, which is then combined with the type to from the property tag. For additional information on named properties, consult the MSDN.