Article ID: 816477
Article Last Modified on 4/7/2006
APPLIES TO
- Microsoft Outlook 2002 Standard Edition
SYMPTOMS
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.
CAUSE
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.
RESOLUTION
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:
307841 OFFXP: How to Obtain the Latest Office XP Service Pack
Hotfix Information
A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Office XP service pack that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix should have the following file attributes or later:
Date Time Size File name -------------------------------------------- 24-Mar-2003 14:26 6,985,728 Outlookff.msp 24-Mar-2003 11:23 3,226,844 Outlookop.msp
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.
Date Time Version Size File name -------------------------------------------------------- 19-Sep-2002 21:23 10.0.4517.0 105,032 Envelope.dll 09-Jan-2003 22:31 10.0.4907.0 346,696 Exsec32.dll 09-Aug-2002 03:22 10.0.4406.0 137,800 Impmail.dll 28-Feb-2003 01:56 10.0.5025.0 543,304 Outlcm.dll 14-Mar-2003 07:55 10.0.5112.0 100,936 Outlctl.dll 22-Mar-2003 03:06 10.0.5119.0 6,318,664 Outllib.dll 11-Oct-2002 22:14 10.0.4608.0 92,744 Outlmime.dll 22-Mar-2003 03:06 10.0.5119.0 47,688 Outlook.exe 22-Mar-2003 03:06 10.0.5119.0 121,416 Outlph.dll 25-Nov-2002 18:50 10.0.4721.0 47,688 Recall.dll
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:
325671 OFFXP: Overview of the Office XP Service Pack 2
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:
330537 OFFXP: Office XP Updates and Patches Released After September 2002 May Require Windows Installer 2.0
STATUS
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.
MORE INFORMATION
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
#ifndef PR_MSG_EDITOR_FORMAT #define PR_MSG_EDITOR_FORMAT PROP_TAG( PT_LONG, 0x5909 ) #define EDITOR_FORMAT_DONTKNOW ((ULONG)0) #define EDITOR_FORMAT_PLAINTEXT ((ULONG)1) #define EDITOR_FORMAT_HTML ((ULONG)2) #define EDITOR_FORMAT_RTF ((ULONG)3) #endif
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.
Additional query words: kb2HR1 FIX
Keywords: kbbug kbfix kbqfe kbenv kbemail kbofficexppresp3fix kbattachments kbhotfixserver KB816477
