X400: Doc Err: Customized Address Maps File

 Last reviewed: October 20, 1997
Article ID: Q135026
3.20 MS-DOS kb3rdparty kbdocerr

The information in this article applies to:

  • Microsoft Mail Gateway to X.400, version 3.2

SYMPTOMS

On page 128 in Appendix B of the Microsoft Mail Gateway to X.400 "Administrator's Guide," the following incorrect example appears: 

   MSM:<Contoso/WCG/Bill> X.400:<o=Contoso,_Ltd;s=Lee;g=Bill;o=E>
If you use this example to create the customized address maps input file and you enter the following command 

   X400cmap mailbox_name [-ppassword] [-ddrive] -finput_file_path
the following error will occur 

   line: n
   ERROR: line <n> - Invalid external nametype <x.400>
   ERROR: compilation unsuccessful
where n represents the line number in the input file in which the invalid entry appears. If there are multiple occurrences, only the first encounter is reported.

RESOLUTION

To correct the example, remove the period in "X.400," as follows: 

   MSM:<Contoso/WCG/Bill> X400:<o=Contoso,_Ltd;s=Lee;g=Bill;o=E>

REFERENCES

For additional information about X.400 customized address maps, please refer to pages 78-81 and 127-129 of the Microsoft Mail Gateway to X.400 "Administrator's Guide."

For additional information about slow message transfer resulting from a large (4000 or more names) custom address map, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q111946
   TITLE     : X400: Slow Message Transfer

Additional reference words: 3.20
KBCategory: kb3rdparty kbdocerr
KBSubcategory: MailGWX400

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