Export (0) Print
Expand All

How to Create Linked Connectors

 

Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007

Topic Last Modified: 2007-01-02

This topic explains how to use the Exchange Management Shell to create linked connectors on a computer that is running Microsoft Exchange Server 2007 and that has the Hub Transport server role or Edge Transport server role installed. A linked connector is a Receive connector that is linked to a Send connector. For linked connectors, the regular routing logic that is based on the destination domain is overridden. All messages that are received by the Receive connector are forwarded to the Send connector to which the Receive connector is linked. This scenario is useful when you want to send messages to a third-party anti-spam and antivirus service for processing, and then return the messages to the Exchange 2007 organization for delivery.

The following list describes the requirements that you must meet to create linked connectors:

  • Only one Receive connector can be linked to one Send connector.

  • The Receive connector must exist before it can be linked to a Send connector.

  • A linked Send connector must route messages to a smart host. You can use an IP address or the fully qualified domain name (FQDN) of the smart host to specify the smart host identity. The smart host identity can be the FQDN of a smart host server, a mail exchange (MX) record, or an address (A) record. If you configure an FQDN as the smart host identity, the source server for the Send connector must be able to use Domain Name System (DNS) name resolution to locate the smart host server.

You can use the Exchange Management Console or the Exchange Management Shell to create the Send connector or Receive connector. However, you can only link a Receive connector to an existing Send connector by using the LinkedReceiveConnector parameter in the Set-SendConnector cmdlet. If you want to create a new Send connector and link a Receive connector to it, you must use the New-SendConnector cmdlet with the LinkedReceiveConnector parameter.

To perform the following procedures, the account you use must be delegated the following:

  • Exchange Organization Administrator role

To perform the following procedures on a computer that has the Edge Transport server role installed, you must log on by using an account that is a member of the local Administrators group on that computer.

For more information about permissions, delegating roles, and the rights that are required to administer Exchange Server 2007, see Permission Considerations.

This section describes a typical linked connector scenario on an Edge Transport server. The following table describes the Send connectors and Receive connectors in that scenario.

Send connectors and Receive connectors in a typical linked connector scenario on an Edge Transport server

Connector name Linked status Connector description

ReceiveConnectorA

Linked to SendConnectorC

This connector receives all messages from the Internet.

ReceiveConnectorB

Not linked

This connector receives messages only from the third-party anti-spam and antivirus service.

SendConnectorC

Contains linked ReceiveConnectorA

This connector sends all messages to the third-party anti-spam and antivirus service smart host.

SendConnectorD

Not linked

This connector sends all messages into the Exchange organization.

In this scenario, all messages that are destined for the Exchange 2007 organization arrive at the Edge Transport server through ReceiveConnectorA. Because ReceiveConnectorA is linked to SendConnectorC, the messages are immediately redirected to the third-party anti-spam and antivirus service through SendConnectorC. After the third-party anti-spam and antivirus service has finished processing the messages, the messages are delivered back to the Edge Transport server through ReceiveConnectorB.

ReceiveConnectorB is an unlinked Receive connector. This connector is very important in this scenario. Without ReceiveConnectorB, the messages would return to the Edge Transport server through ReceiveConnectorA and would then be forwarded back to the third-party anti-spam and antivirus service. This process would continue indefinitely. However, because ReceiveConnectorB is not linked to a Send connector, the Edge Transport server is free to select the route into the Exchange organization. This would occur through SendConnectorD. The messages are then delivered to the original recipients in the Exchange organization through SendConnectorD.

Run the following command to link a Receive connector to a new Send connector.

  • Use the following command:

    New-SendConnector -Name <ConnectorName> -LinkedReceiveConnector <ReceiveConnectorID> -SmartHosts <SmarthostID> -SmartHostAuthMechanism <AuthMechanism> -DNSRoutingEnabled $False -MaxMessageSize unlimited
    

    In the following example, the command links a Receive connector to a new Send connector. The properties of the Send connector and Receive connector are described in the following list:

    • Send connector name: "To Hygiene Service"

    • Linked Receive connector identity: "Edge01\From Internet"

    • Smart host identity: hygiene.contoso.com

    • Smart host authentication mechanism: ExternalAuthoritative

    New-SendConnector -Name "To Hygiene Service" -LinkedReceiveConnector "Edge01\From Internet" -SmartHosts hygiene.contoso.com -SmartHostAuthMechanism ExternalAuthoritative -DNSRoutingEnabled $False -MaxMessageSize unlimited
    

For detailed syntax and parameter information, see New-SendConnector.

Run the following command to link a Receive connector to an existing Send connector.

  • Use the following command:

    Set-SendConnector <ConnectorID> -LinkedReceiveConnector <ReceiveConnectorID> -SmartHosts <SmarthostID> -SmartHostAuthMechanism <AuthMechanism> AddressSpaces $Null -DNSRoutingEnabled $False -MaxMessageSize unlimited
    

    In the following example, the command links a Receive connector to an existing Send connector. The Send connector and Receive connector properties are described in the following list:

    • Send connector identity: "To Hygiene Service"

    • Linked Receive connector identity: "Edge01\From Internet"

    • Smart host identity: hygiene.contoso.com

    • Smart host authentication mechanism: ExternalAuthoritative

    Set-SendConnector "To Hygiene Service" -LinkedReceiveConnector "Edge01\From Internet" -SmartHosts hygiene.contoso.com -SmartHostAuthMechanism ExternalAuthoritative AddressSpaces $Null -DNSRoutingEnabled $False -MaxMessageSize unlimited
    

For detailed syntax and parameter information, see Set-SendConnector.

After you have linked a Receive connector to a Send connector, you may want to break the link at some time. The following list describes the options for breaking the link:

  • Remove the Send connector to which the Receive connector is linked   You can remove the Send connector by using the Exchange Management Console or by using the Remove-SendConnector cmdlet in the Exchange Management Shell. After you remove the Send connector, you don't have to modify the configuration of the Receive connector.

  • Remove the Receive connector that is linked to the Send connector   You can remove the Receive connector by using the Exchange Management Console, or by using the Remove-ReceiveConnector cmdlet in the Exchange Management Shell. After you remove the Receive connector, you must modify the configuration of the Send connector. After the linked Receive connector is removed, the Send connector will have no address spaces configured. If you try to view or modify the Send connector, you will receive an error message that states that the Send connector is corrupted. To configure an address space for the Send connector, you can use the Exchange Management Console or the Set-SendConnector cmdlet in the Exchange Management Shell.

For detailed syntax and parameter information, see the following topics:

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft