XFOR: NDR on Message Sent from Eastern European Outlook via Microsoft Mail Connector

ID: Q224987

The information in this article applies to:

SYMPTOMS

An Outlook 8.0x or Outlook 8.5 client running on Windows NT 4.0 Workstation or Windows 95/98 with language settings set to an East European language gets a non-delivery report (NDR) similar to that below, when sending from a Microsoft Mail postoffice to Exchange Server:

Your Message

To: User
Subject: Subject

Was not delivered for the following reasons:

Delivery failed to MS:NETWORK/PO/USER
Reason: 0 (transfer failed)
diagnostic: -1 (no diagnostic).
MSEXCH:MSExchangeMTA:

Original message body follows...
The Outlook client is connected to a Microsoft Mail postoffice, and the postoffice is connected to Exchange Server using the Microsoft Mail Connector, as follows:
Outlook -> Postoffice -> Microsoft Mail Connector -> Exchange Server 5.0
The following messages are written to the Windows NT Application Event log:
Event ID: 2025 (IS Priv)
Description: The delivery of a message failed due to error 80004005. A non-delivery report is being sent to the message's originator.
-and-
Event ID: 270 (MTA)
Description: A permanent error has occurred with Entity /O=org/OU=orgunit/CN=CONFIGURATION/CN=SERVERS/CN=user/CN=MICROSOFT PRIVATE MDB. Entity is a Message Object is a Normal Priority Message. Object: 06000046. Message ID: C=country;A=admd ;P=prmd;L=organisation-site-000000AF Content length: 1281, External Trace information (first 100 bytes) = 3080638061801302555300006280130120000013094D6963726F736F66740000318080113 938313230383135313430302D303530308201008302060000000000, PDU dump reference 1 [MTA SUBMIT 16 74] (14)
-and-
Event ID: 290 (MTA)
Description: A non-delivery report (reason code transfer-failure and diagnostic code Omit any diagnostic code) is being generated for message C=country;A=admd ;P=prmd;L=organisation-site-000000AF. It was originally destined for DN:/o=org/ou=orgunit/cn=Recipients/cn=user1 (recipient number 1), and was to be redirected to. [MTA DISP:RESULT 18 136] (12)


CAUSE

This problem occurs when the Microsoft Exchange Server information store receives a message from the message transfer agent (MTA) and detects that there are two MAPI properties for strings within the message that have conflicting code page IDs. The information store sends an NDR on the message because the discrepancy was encountered.

This problem does not occur if an Eastern European Exchange client is used instead of the Eastern European Outlook client. This is because the Eastern European Outlook client includes four additional MAPI properties for the TNEF portion of the message, one of which is an additional string property containing a code page ID.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.0 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 on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

Component: Microsoft Mail Connector Interchange

File name Version
Address.dll 5.0.1461.88
Mt.exe 5.0.1461.88
Mtmsg.dll 5.0.1461.88


NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0.

Additional query words: MSMI 


Keywords          : 
Version           : WINDOWS:8.0,8.01,8.02,8.03,8.5; winnt:5.0
Platform          : WINDOWS winnt 
Issue type        : kbbug

Last Reviewed: June 28, 1999