XCON: MTA: Invalid Originator Address When Sending to X.400

 Last reviewed: July 15, 1997
Article ID: Q146032

The information in this article applies to:

  • Microsoft Exchange Server, version 5.0

SYMPTOMS

When you send a message from Microsoft Mail through Microsoft Exchange Server 5.0 to someone on an X.400 messaging system, a reply to this message may not be possible. This occurs if you (the Microsoft Mail user) are not a Custom Recipient on Microsoft Exchange Server, which can happen if, for example, directory synchronization is not yet finished.

CAUSE

The message will arrive at the remote X.400 system with an invalid X.400 originator address in the P1 header fields. The X.400 address will only contain a DDA Type and a DDA Value, which contains the Microsoft Mail Address. For example: 

   DDA Type=MS;DDA Value=Net/PO/User
This address is invalid because mandatory parts are missing. A valid address would look like this: 

   C=Country;A=Admin;P=Private;O=Org;DDA Type=MS;DDA Value=Net/PO/User

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem was corrected in the latest Microsoft Exchange 5.0 Server U.S. 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

Keywords : kbbug5.00 kbfix5.00.sp1 kbusage XCLN buglist
Version : 5.0
Platform : WINDOWS
Issue type : kbbug

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: July 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.