PC Adm: Requestor Name of MSMAIL Appears Corrupt

Last reviewed: October 24, 1995
Article ID: Q113071
The information in this article applies to:
  • Microsoft Mail for PC Networks, version 3.2

SYMPTOMS

When you add requestors with version 3.2, 3.2.2, or 3.2.3 of the Mail Administrator program (ADMIN.EXE) and you select MSGATE, the name of the requestor will appear unreadable. This is not the expected behavior and was not true in earlier versions of the Administrator program.

CAUSE

The MSMAIL Macintosh gateway does not need to be defined as a requestor. Macintosh names and types can still be used and propagated through directory synchronization (Dir-Sync) without MSMAIL as a requestor. How propagation occurs depends on the version of Microsoft Mail Connection for PC and AppleTalk Networks in use.

MORE INFORMATION

With version 1.0b of the Mail Connection gateway, names could be placed manually into the Dir-Sync stream by using the IMPORT.EXE -E option. Requestors that requested MSMAIL addresses would then be sent these transactions during the Dir-Sync cycle.

With version 3.2 of the Mail Connection gateway, the proxy NET/PO name should be used for the MSMAIL requestor. The gateway uses this proxy name to communicate transactions to and from the Dir-Sync process.

REFERENCES

  • Page 189 of the version 3.2 Microsoft Mail for PC Networks "Administrator's Guide," "Specifying the Address Types"
  • Page 191 of the version 3.2 Microsoft Mail for PC Networks "Administrator's Guide," "Synchronizing Foreign Addresses"


Additional reference words: 3.20 admin dirsync dirsynch Mac
KBCategory: kbenv kbinterop kbtlc
KBSubcategory: MailPCAdm


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