Knowledge Base

Text in the message body is truncated when the message is received by a MAPI client and was sent by a POP3 client in an Exchange 2000 environment

Article ID: 828716

Article Last Modified on 10/26/2006

APPLIES TO

Microsoft Exchange 2000 Server Standard Edition
Microsoft Exchange 2000 Enterprise Server

SYMPTOMS

When a message recipient who uses a MAPI client, such as Microsoft Outlook, opens and views a message, the text in the message body may be truncated. This problem occurs when the message sender uses a POP3 client, such as Microsoft Outlook Express, in a Microsoft Exchange 2000 Server environment.

CAUSE

This problem may occur if all the following conditions are true:

The message is sent as a plain text format message that uses MIME format. For example, the mail sending format in Outlook Express is set to Plain Text, the message format is set to MIME, and the Encode text using setting is set to None.
The message body contains the word "begin" (without the quotation marks) followed by 4 spaces.

In this situation, when Exchange 2000 converts the content from MIME format to MAPI format, Exchange incorrectly detects the part of the message body that starts with "begin" (without the quotation marks) as a uuencode attachment.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Exchange 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;[LN;CNTACTMS]

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.

Prerequisites

Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For more information, click the following article number to view the article in the Microsoft Knowledge Base:

301378 How to obtain the latest Exchange 2000 Server service pack

File information

The English version of this hotfix has the file attributes (or later file attributes) 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
--------------------------------------------------------
15-Oct-2003  13:31  6.0.6521.0   3,915,776  Cdoex.dll        
15-Oct-2003  13:25  6.0.6521.0     851,968  Davex.dll        
15-Oct-2003  13:25  6.0.6521.0      53,248  Davexpc.dll      
15-Oct-2003  13:22  6.0.6521.0     131,072  Drviis.dll       
15-Oct-2003  13:22  6.0.6521.0     577,536  Dsaccess.dll     
15-Oct-2003  12:33  6.0.6521.0     184,320  Dscmsg.dll       
15-Oct-2003  12:33  6.0.6521.0     962,560  Emsmdb32.dll     
15-Oct-2003  13:25  6.0.6521.0   2,179,072  Ese.dll          
15-Oct-2003  13:25  6.0.6521.0      40,960  Eseperf.dll      
15-Oct-2003  13:31  6.0.6521.0   3,575,808  Excdo.dll        
15-Oct-2003  13:22  6.0.6521.0     262,144  Exmime.dll       
15-Oct-2003  13:25  6.0.6521.0     143,360  Exodbesh.dll     
15-Oct-2003  13:25  6.0.6521.0      57,344  Exodbpc.dll      
15-Oct-2003  13:25  6.0.6521.0     200,704  Exodbprx.dll     
15-Oct-2003  13:25  6.0.6521.0   2,179,072  Exoledb.dll      
15-Oct-2003  13:20  6.0.6521.0      81,920  Exosal.dll       
15-Oct-2003  13:25  6.0.6521.0     307,200  Exprox.dll       
15-Oct-2003  13:25  6.0.6521.0     315,392  Exsmtp.dll       
15-Oct-2003  12:38  6.0.6521.0     675,840  Exwform.dll      
15-Oct-2003  13:23  6.0.6521.0      40,960  Jcb.dll          
15-Oct-2003  12:13  6.0.6521.0      49,152  Mdbevent.dll     
15-Oct-2003  12:30  6.0.6521.0   2,285,568  Mdbmsg.dll       
15-Oct-2003  12:15  6.0.6521.0      32,768  Mdbrole.dll      
15-Oct-2003  13:23  6.0.6521.0      576  Mdbtask.dll      
15-Oct-2003  13:19  6.0.6521.0      94,208  Peexch50.dll     
15-Oct-2003  13:20  6.0.6521.0     397,312  Phatcat.dll      
15-Oct-2003  13:23  6.0.6521.0     532,480  Reapi.dll        
15-Oct-2003  13:25  6.0.6521.0     311,296  Resvc.dll        
15-Oct-2003  12:38  6.0.6521.0   3,735,552  Wmtemplates.dll  
15-Oct-2003  12:36  6.0.6521.0     143,360  Exschema.exe     
15-Oct-2003  13:21  6.0.6521.0   4,657,152  Store.exe        
08-Sep-2003  16:18                   6,991  Eseperf.hxx
15-Oct-2003  13:25                 391,634  Eseperf.ini

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

For more information about naming schema for Exchange Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

817903 New naming schema for Exchange Server software update packages

Keywords: kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB828716

Microsoft KB Archive/828716

Contents