XCLN: X.400 One-Off Address in To Field Can Cause Error

Last reviewed: April 14, 1997
Article ID: Q147413
The information in this article applies to:
  • Microsoft Exchange Windows 95 client, version 4.0
  • Microsoft Exchange Windows 3.x client, version 4.0
  • Microsoft Exchange Windows NT client, version 4.0
  • Microsoft Exchange MS-DOS client, version 4.0

SYMPTOMS

The following error message occurs when you try to send a message to an X.400 One-Off address, such as "c=us;a= ;p=xyz;o=abc;s=userx" (without quotation marks):

   Microsoft Exchange does not recognize "c=us"

CAUSE

This error occurs because Exchange interprets semi-colons (;) in the address field as separator characters between two different addresses.

RESOLUTION

Put the X.400 One-Off address into the [x400: ] format to allow Exchange to interpret the semi-colons in the address as part of one X.400 address.

For example, put the "c=us;a= ;p=xyz;o=abc;s=userx" X.400 address in the following format in the To: field:

   [x400:c=us;a= ;p=xyz;o=abc;s=userx]


---------- 10/25/96 9:05 ----------

In addition, the X.400 address can be put into the X.400 new template to be resolved automatically. To do this:

  1. Choose the TO button.

  2. Choose NEW and choose X.400 address.

  3. Add the addressee information to the appropriate field and choose OK.


Additional query words:
Keywords : kbusage XCLN
Version : 4.0
Platform : WinNT


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