XFOR: Exchange PC MTA Will Not Connect to Indirect Downstream PO

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

SUMMARY

You cannot configure an instance of the Microsoft Mail Connector (PC) message transfer agent (MTA) to deliver mail to indirect downstream postoffices (POs). This functionality is designed into Microsoft Exchange.

MORE INFORMATION

Exchange needs to know the connection path to any Microsoft Mail postoffices in order to be able to deliver mail to them. Once you defined a connection to any one postoffice, a direct routing path is defined for the connector.

For example: 

   Connector PO (A) ---- Hub PO (B) ---- Downstream PO (C)
An instance of the Microsoft Mail Connector (PC) MTA can be configured to move mail between A and B, but not between A, B, and C if you want to go indirect via B.

You can create an instance of PC MTA to move mail between A, B, and C, but mail from A to C and C to A will go direct. This is because the PC MTA needs to have connection information to be able to connect to any PO. Since it is possible to have a direct connection, then there is no need for an indirect route to this PO.

Additional query words: external
Keywords : kbinterop XFOR
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: April 3, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.