XCON: Latin-1 X.400 Bodypart Encoding Causes NDR (151417)
The information in this article applies to:
- Microsoft Exchange Server 4.0
- Microsoft Exchange Server 5.0
This article was previously published under Q151417 SYMPTOMS
The use of ISO 8859-1 (Latin-1) as X.400 bodypart for the X.400 message
text sent by Microsoft Exchange Server may result in this bodypart not
being recognized by MTAs such as Digital's MAILbus 400. Therefore, no
further processing, such as conversion can occur on this message. On the
MAILbus 400 side this may result in error message similar to the following:
Event:Converter Unavailable
(Please see the More Information section for the complete error log).
Eventually, a non-delivery report (NDR) will be sent back to Microsoft
Exchange Server.
CAUSE
The encoding used by Microsoft Exchange Server for the ISO 8859-1 (Latin-1)
bodypart lacks the escape sequence needed to invoke the G0 subset of the
ISO Latin 1 character set.
WORKAROUND
Do not use the ISO 8859-1 (Latin-1) bodypart if the remote message transfer
agent (MTA) is not able to decode the message without errors as sent by
Microsoft Exchange Server.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange Server
version 4.0. This problem has been corrected in the latest U.S. Service
Pack for Microsoft Exchange Server version 4.0. For information on
obtaining the Service Pack, query on the following word in the Microsoft
Knowledge Base (without the spaces):
Microsoft has confirmed this to be a problem in Microsoft Exchange Server
version 5.0. This problem has been corrected in the latest U.S. Service
Pack for Microsoft Exchange Server version 5.0. For information on
obtaining the Service Pack, query on the following word in the Microsoft
Knowledge Base (without the spaces):
Modification Type: | Minor | Last Reviewed: | 4/28/2005 |
---|
Keywords: | kbbug kbfix kbusage KB151417 |
---|
|