XFOR: MS Mail X.400 Gateways and Exchange X.121 Addresses

Last reviewed: April 15, 1997
Article ID: Q156725

The information in this article applies to:

Microsoft Exchange Server, version 4.0

SYMPTOMS

If your Microsoft Exchange Server sends a message indirectly via a Shared File System (SFS) X.400 gateway, and part of the X.400 O/R address contains:

   X.121=

and there is a period between the X and the 1, the X.400 gateway will fail to process the message. The following error will appear on the X.400 gateway if it is running with the -lvd command line option:

   15:46:15 Extracting message from local message store: 00000020
   15:46:15 DEBUG (Converting PC Mail message to X400): Translating to
            X400
   15:46:15 ERROR 3 (Creating P1 Recipient address): Malformed address:
            type <16>

CAUSE

The SFS X.400 gateway will only process X.121 addresses when there is no period between the X and the 1. The period will be present when an X.400 address is imported from Microsoft Mail to Microsoft Exchange Server using Directory Synchronization (DirSync) and the address is of the format c=gb;a=admd;p=prmd;x.121=1234567890. This is a valid address, but not an address that the SFS X.400 gateway will be able to process.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem was corrected in the latest Microsoft Exchange Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

Additional query words:
Keywords : kbbug4.00 kbfix4.00.sp3 kbusage XFOR
Version : 4.0
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.