X400: Err Msg: ERROR 4 (Converting X.400 Delivery Report)...Last reviewed: March 9, 1998Article ID: Q129693 |
3.20
MS-DOS
kb3rdparty kbfile kbbug3.20 kbfix3.20 kbfix
The information in this article applies to:
SYMPTOMSMicrosoft Mail Gateway to X.400 may display the following error: 18:00:40 ERROR 4 (converting X.400 delivery report): Decoding X.400 Message 18:00:41 ERROR 4 (transmitting message to local message store): Translate to local form failed on message: 00000F7D
CAUSEWhen a message is sent to an invalid address via the X.400 gateway (connected to a certain types of X.400 service providers), the nondelivery report is not returned to the originator, but instead is rejected and placed into the BAD directory. The X.400 gateway routine that is responsible for Delivery reports incorrectly counts the number of bytes already decoded. This occurs when an element with a definite length includes elements of indefinite length.
STATUSMicrosoft has confirmed this to be a problem in version 3.2 of Microsoft Mail Gateway to X.400. This problem is corrected in X400GATE.EXE version 3.2.17. If you do not have version 3.2.17, you can download X400GA.EXE, a self-extracting file, on the following services:
ARTICLE-ID: Q119591 TITLE : How to Obtain Microsoft Support Files from Online Services MORE INFORMATIONThe following is a sample log from an X.400 gateway that is experiencing this problem: 18:00:40 Transmitting message to local message store: 00000F7D 18:00:40 ERROR 4 (converting X.400 delivery report): Decoding X.400 Message 18:00:41 ERROR 4 (transmitting message to local message store): Translate to local form failed on message: 00000F7D Copying to 'bad' directory: W:x400/outgoing/LSAMTA/00000F7D 18:00:42 WARNING 4 (transmitting message): Failed transmitting message; MTA: LSAMTA pointer count: 513; byte count: 13944
|
Additional reference words: 3.20
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |