XCON: NDR Is Not Always Sent When a Message That Has DBCS Characters in an SMTP Address Cannot Be Delivered

View products that this article applies to.

Symptoms

When you create a new message in Microsoft Outlook and you use double-byte character set (DBCS) characters in the Simple Mail Transfer Protocol (SMTP) address that is in the To field, the message can be sent by Outlook. However, the message cannot be delivered by Microsoft Exchange 2000 Server. Sometimes you receive a non-delivery receipt (NDR) and sometimes you do not receive an NDR.

↑ Back to the top

Cause

This problem occurs because DBCS characters cannot be used in an SMTP address. However, Outlook does not stop you from typing DBCS characters in the SMTP address, and Exchange does not test to see if there are DBCS characters in the SMTP address. As a result, Exchange 2000 interprets the DBCS characters as ASCII characters.

↑ Back to the top

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, we recommend that you wait for the next Microsoft Exchange 2000 Server 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 telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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

Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional 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) 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
--------------------------------------------------------------
05-Aug-2003  20:37  6.0.6495.0      3,915,776  Cdoex.dll        
05-Aug-2003  20:31  6.0.6495.0        851,968  Davex.dll        
05-Aug-2003  20:31  6.0.6495.0         53,248  Davexpc.dll      
05-Aug-2003  19:00  6.0.6495.0        131,072  Drviis.dll       
05-Aug-2003  19:00  6.0.6495.0        577,536  Dsaccess.dll     
05-Aug-2003  17:47  6.0.6495.0        184,320  Dscmsg.dll       
05-Aug-2003  18:04  6.0.6495.0        958,464  Emsmdb32.dll     
05-Aug-2003  20:37  6.0.6495.0      3,575,808  Excdo.dll        
05-Aug-2003  19:00  6.0.6495.0        258,048  Exmime.dll       
05-Aug-2003  20:31  6.0.6495.0        143,360  Exodbesh.dll     
05-Aug-2003  20:31  6.0.6495.0         57,344  Exodbpc.dll      
05-Aug-2003  20:31  6.0.6495.0        200,704  Exodbprx.dll     
05-Aug-2003  20:31  6.0.6495.0      2,174,976  Exoledb.dll      
05-Aug-2003  18:59  6.0.6495.0         81,920  Exosal.dll       
05-Aug-2003  20:31  6.0.6495.0        307,200  Exprox.dll       
05-Aug-2003  17:49  6.0.6495.0        143,360  Exschema.exe     
05-Aug-2003  20:40  6.0.6495.0        315,392  Exsmtp.dll       
05-Aug-2003  17:51  6.0.6495.0        675,840  Exwform.dll      
05-Aug-2003  17:39  6.0.6495.0         49,152  Mdbevent.dll     
05-Aug-2003  18:01  6.0.6495.0      2,285,568  Mdbmsg.dll       
05-Aug-2003  17:41  6.0.6495.0         32,768  Mdbrole.dll      
05-Aug-2003  19:00  6.0.6495.0         24,576  Mdbtask.dll      
05-Aug-2003  18:58  6.0.6495.0         94,208  Peexch50.dll     
05-Aug-2003  18:59  6.0.6495.0        397,312  Phatcat.dll      
05-Aug-2003  19:00  6.0.6495.0        528,384  Reapi.dll        
05-Aug-2003  20:40  6.0.6495.0        311,296  Resvc.dll        
05-Aug-2003  19:00  6.0.6495.0      4,657,152  Store.exe

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

↑ Back to the top

More information

After you install the hotfix that is described in this article, you receive the following error message when you try to send a message that contains a DBCS SMTP address:

The client operation failed

↑ Back to the top