XADM: Distributing Gateway Addresses to Exchange Server

Last reviewed: September 23, 1997
Article ID: Q147607
The information in this article applies to:
  • Microsoft Exchange Server, version 4.0

SUMMARY

To provide the Microsoft Exchange clients access to Microsoft Mail for PC Networks 3.x gateway recipients, the gateway address lists from the Microsoft Mail postoffice must be propagated to the Microsoft Exchange Server Recipients container.

MORE INFORMATION

This article assumes that the Microsoft Mail Connector and directory synchronization (dirsync) are already correctly configured between the Microsoft PC Mail and the Microsoft Exchange Server environments.

  1. Install the Microsoft Mail for PC Networks Gateway Access Component on the Microsoft Exchange Server’s shadow postoffice, following the instructions provided with the Gateway Access Component documentation.

    NOTE: You can access the Microsoft Exchange Server’s shadow postoffice by connecting to the MAILDAT$ share on the Microsoft Exchange Server:

          net use * \\exserver\maildat$
    

  2. Configure any necessary options on the gateway postoffice to ensure that gateway messages are routed properly to the Microsoft Exchange Server’s shadow postoffice.

  3. If the Microsoft Exchange Server acts as a dirsync requestor, perform the following steps using the Microsoft Exchange Administrator program; otherwise, proceed with Step 4:

        - From the Container window, select the appropriate site’s
          Configuration, Connections container
        - Double-click the Exchange DirSync Requestor connector.
        - From the General Property page, ensure that the appropriate gateway
          types to be propagated are selected.
    

    This will allow the Microsoft Exchange Server’s Shadow Postoffice to accept addresses of this type.

  4. Create a file containing the gateway addresses by using IMPORT.EXE to extract the addresses from the Microsoft PC Mail postoffice. For example:

          import admin -ppassword -dm -gMHS -fextract.txt -x
    

    This example will create a text file called EXTRACT.TXT that contains all of the MHS gateway addresses on the postoffice on drive M.

  5. Re-import the addresses using the import command with the -e parameter:

          import admin -ppassword -dm -fextract.txt -e
    

    This example will import all of the addresses in the file called EXTRACT.TXT into the directory synchronization (dirsync) process on the postoffice on drive M.

    NOTE: The use of the IMPORT.EXE utility with the -E option will populate the REQTRANS.GLB on the postoffice with all of the gateway addresses listed in the import-format text file. The dirsync server must have the gateway access component installed for these addresses to be accepted and propagated.

  6. The dirsync process will now distribute these addresses on its next cycle.

REFERENCES

For additional instructions on configuring Microsoft Exchange Directory Synchronization, please refer to Chapter 14 of the Microsoft Exchange Server Administrator’s Guide.

For additional information on how to distribute gateway addresses using directory synchronization, please see the following article in the Microsoft Knowledge Base:

  ARTICLE-ID: Q123856
  TITLE :     How to Distribute Gateway Addresses with Dir-Sync


Additional query words: faq dir-sync dirsynch
Keywords : XADM kbenv kbusage
Version : 4.0 5.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: September 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.