XADM: Spaces not Allowed in Some X400 Entry Fields

Last reviewed: April 21, 1997
Article ID: Q147113
The information in this article applies to:
  • Microsoft Exchange Server, version 4.0

SUMMARY

When creating a custom X.400 recipient, the following fields on the advanced property page of the X.400 addressing page allow only for numerals 0 - 9. No alphanumeric characters or spaces are allowed. The fields that are thus limited are as follows:

   User Agent numeric ID (n-id)
   X.121 (x.121)
   Terminal Type (t-ty)

MORE INFORMATION

The X.400 specification allows for spaces in the above types, however the Microsoft Exchange addressing scheme (address.dll) does not support spaces in those three fields.

This can become a problem when creating custom recipients to X.400 system recipients who follow this addressing scheme; it could result in a non- delivery report (NDR) to such a user.

WORKAOUND

Currently with Exchange 4.0 the only workaround is to remove the space from the desired user on the above fields so that they match the Exchange format.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange version 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: x400 bluebook redbook x121 1988 1984
Keywords : kbusage XADM
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 21, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.