Article ID: 313523
Article Last Modified on 9/23/2005
APPLIES TO
- Microsoft Outlook 2000 Standard Edition
This article was previously published under Q313523
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
Outlook 2000 sends any message that contains a custom form with Multipurpose Internet Mail Extensions (MIME) and Transport Neutral Encapsulation Format (TNEF). Outlook 2000 sends these types of messages even when the custom form has an IPM.Note message class.
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Office 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
276367 OFF2000: How to Obtain the Latest Office 2000 Service Pack
The English-language 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
-------------------------------------------------------
14-Jun-2000 13:11 1.0.3.27 41,472 Bjablr32.dll
14-Jun-2000 13:12 3.2.0.27 61,952 Bjlog32.dll
08-Jan-2001 17:37 1.0.3.28 98,304 Bjsrch32.dll
19-Jun-2000 14:49 5.5.2652.65 716,560 Cdo.dll
19-Jun-2000 14:12 5.5.2652.65 808,720 Cdo.dll_0004
01-Dec-2001 22:00 9.0.0.5930 127,027 Contab32.dll_0002
14-Jun-2000 13:14 1.0.3.27 183,808 Emablt32.dll
31-Aug-2000 15:43 5.5.3142.0 154,112 Emsabp32.dll_0005
05-Oct-2001 06:33 5.5.3165.0 594,192 Emsmdb32.dll_0005
01-Jun-2001 21:15 5.5.3159.0 131,344 Emsui32.dll_0005
02-Jun-2000 06:45 9.0.0.4201 86,067 Envelope.dll
18-Dec-2001 19:19 5.5.3167.0 540,944 Exsec32.dll_0005
05-Apr-2000 15:02 9.0.0.4005 192,561 Mimedir.dll
21-May-2001 14:20 5.5.3157.0 792,576 Msmapi32.dll_0001
21-May-2001 14:16 5.5.3157.0 623,104 Msmapi32.dll_0002
07-Jul-2000 23:07 5.5.3138.0 602,384 Mspst32.dll_0004
07-Jul-2000 23:03 5.5.3138.0 528,656 Mspst32.dll_0005
31-Jan-2000 21:26 9.0.0.3731 196,661 Oladd.fae
23-May-2000 11:20 150,690 Olexchng.aw
30-May-2000 14:53 26,643 Olsec9.chm
22-May-2000 19:35 170,617 Olxchng9.chm
08-Feb-2001 13:17 5.5.3153.0 454,144 Omi9.dll_0001
08-Feb-2001 13:21 5.5.3153.0 548,352 Omint.dll_0001
06-Jun-2001 13:05 129,024 Out2ksec.mst
13-Nov-2001 07:45 8.30.3165.0 782,608 Outex.dll
23-May-2000 19:19 554,068 Outlhlp.aw_0001
18-Jan-2002 05:32 9.0.0.6117 5,328,946 Outllib.dll
31-Aug-2001 20:02 9.0.0.5630 1,675,315 Outllibr.dll
13-Jul-2001 05:48 9.0.5512.0 368,691 Pstprx32.dll_0002
21-Jun-2001 18:01 9.0.0.5421 73,772 Rm.dll
02-Jun-2000 07:30 9.0.0.4201 65,586 Sendto9.dll
After the fix is installed, the following files will have the listed attributes or later:
Date Time Version Size File name
-------------------------------------------------------
14-Jun-2000 13:11 1.0.3.27 41,472 Bjablr32.dll
14-Jun-2000 13:12 3.2.0.27 61,952 Bjlog32.dll
08-Jan-2001 17:37 1.0.3.28 98,304 Bjsrch32.dll
19-Jun-2000 14:49 5.5.2652.65 716,560 Cdo.dll
19-Jun-2000 14:12 5.5.2652.65 808,720 Cdo.dll_0004
01-Dec-2001 22:00 9.0.0.5930 127,027 Contab32.dll_0002
14-Jun-2000 13:14 1.0.3.27 183,808 Emablt32.dll
31-Aug-2000 15:43 5.5.3142.0 154,112 Emsabp32.dll_0005
05-Oct-2001 06:33 5.5.3165.0 594,192 Emsmdb32.dll_0005
01-Jun-2001 21:15 5.5.3159.0 131,344 Emsui32.dll_0005
02-Jun-2000 06:45 9.0.0.4201 86,067 Envelope.dll
18-Dec-2001 19:19 5.5.3167.0 540,944 Exsec32.dll_0005
05-Apr-2000 15:02 9.0.0.4005 192,561 Mimedir.dll
21-May-2001 14:20 5.5.3157.0 792,576 Msmapi32.dll_0001
21-May-2001 14:16 5.5.3157.0 623,104 Msmapi32.dll_0002
07-Jul-2000 23:07 5.5.3138.0 602,384 Mspst32.dll_0004
07-Jul-2000 23:03 5.5.3138.0 528,656 Mspst32.dll_0005
31-Jan-2000 21:26 9.0.0.3731 196,661 Oladd.fae
23-May-2000 11:20 150,690 Olexchng.aw
30-May-2000 14:53 26,643 Olsec9.chm
22-May-2000 19:35 170,617 Olxchng9.chm
08-Feb-2001 13:17 5.5.3153.0 454,144 Omi9.dll_0001
08-Feb-2001 13:21 5.5.3153.0 548,352 Omint.dll_0001
06-Jun-2001 13:05 129,024 Out2ksec.mst
13-Nov-2001 07:45 8.30.3165.0 782,608 Outex.dll
23-May-2000 19:19 554,068 Outlhlp.aw_0001
18-Jan-2002 05:32 9.0.0.6117 5,328,946 Outllib.dll
31-Aug-2001 20:02 9.0.0.5630 1,675,315 Outllibr.dll
13-Jul-2001 05:48 9.0.5512.0 368,691 Pstprx32.dll_0002
21-Jun-2001 18:01 9.0.0.5421 73,772 Rm.dll
02-Jun-2000 07:30 9.0.0.4201 65,586 Sendto9.dll
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 Microsoft Office 2000 Service Pack 3 (SP-3).
MORE INFORMATION
To activate the fix, update the registry.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
- Start Registry Editor (Regedt32.exe).
- Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\9.0\Outlook\Options\Mail\
- On the Edit menu, click Add Value, and then add the following registry value:
Value name: DontEncodeCustomNote
Data type: REG_DWORD
Radix: Decimal
Value data: 1 - Quit Registry Editor.
The registry key controls whether or not Outlook 2000 automatically sends TNEF for a custom form even when the custom form has a message class of IPM.Note.
How the Value Controls When TNEF Is Sent for a Custom Form
- If the value is zero (or not present), you experience the following symptoms when you send a message:
- If you send a message by using the attached custom form, Outlook 2000 sends the message using TNEF. This occurs when you are using Outlook 2000 in the Internet Mail Only (IMO) mode.
- If you send a clear signed message by using the attached custom form, Outlook 2000 sends a binary large object (BLOB) signed message. This occurs when you are using Outlook 2000 in the Corporate or Workgroup (CW) mode.
NOTE: A clear signed message should have a message class of "IPM.Note.SMIME.MultipartSigned" (without quotation marks), and a MIME content-type of "multipart/signed" (without quotation marks). A BLOB signed message should have a message class of "IPM.Note.SMIME" (without quotation marks), and a MIME content-type of "application/pkcs7-mime" (without quotation marks).
- If the value is non-zero (or present), you experience the following symptoms when you send a message:
- If you send a message by using the attached custom form, Outlook 2000 sends the message without using the TNEF formatting. This occurs when you are using Outlook 2000 in the IMO mode.
- If you send a clear signed message by using the attached custom form, the message is sent as a clear signed message. This occurs when you are using Outlook 2000 in the CW mode.
- If the value is zero or non-zero, you experience the following symptoms when you send a message:
- If you send a message with a custom message class (for example, a message that does not match the IPM.Note class), it is always sent using the TNEF format. This occurs when you are using Outlook 2000 in the IMO mode.
- If you send a clear signed message that uses Outlook voting buttons, Outlook 2000 sends a BLOB signed message. This occurs when you are using Outlook 2000 in the CW mode.
Additional query words: dms tnef signed note blob
Keywords: kbbug kbfix kbqfe kboffice2000sp3fix kboffice2000presp3fix kbhotfixserver KB313523
