Creating Send Connector
To create a Send connector, you can use either Exchange Management Console or Exchange Management Shell.
To create a Send connector using Exchange Management Console
- Open the Exchange Management Console. Select Organization Configuration | Hub Transport.
- In the action pane, click New Send Сonnector. The New SMTP Send Сonnector wizard runs.
- When prompted, in the Name field, type a unique name for the connector, for example, "QMM Send Connector." From the Select the intended use for this Send connector drop-down list, select Custom, and then click Next.
- On the Address space page, click Add. In the dialog box displayed, specify the address space you want to use for mail redirection from source to target (target to source) organization (for example, *.target.local or *.source.local), select the Include all subdomains option, click OK and then click Next.
- On the Network settings page, select Use Domain Name System (DNS) "MX" records to route mail automatically. Select the Use the External DNS Lookup settings on the transport server option.
- Next, on the Source Server page, click Add. In the dialog box displayed, select one or more Hub Transport servers in your organization, click OK and then click Next.
- Finally, on the New Connector page, click New, and then on the Completion page, click Finish.
To create a Send connector using Exchange Management Shell
Run the following command for the source Exchange organization:
new-SendConnector -Name 'QMM Send Connector' -Usage 'Custom' -AddressSpaces 'SMTP:*.target.local;1' -IsScopedConnector $false -DNSRoutingEnabled $true -UseExternalDNSServersEnabled $true -SourceTransportServers 'ServerName'
where:
- *.target.local is the address space you want to use for mail redirection from source to target organization.
- ServerName is the Hub Transport server name.
Run the following command for the target Exchange organization:
new-SendConnector -Name 'QMM Send Connector' -Usage 'Custom' -AddressSpaces 'SMTP:*.source.local;1' -IsScopedConnector $false -DNSRoutingEnabled $true -UseExternalDNSServersEnabled $true -SourceTransportServers 'ServerName'
where:
- *.source.local is the address space you want to use for mail redirection from target to source organization.
- ServerName is the Hub Transport server name.
Modifying Default Receive Connector
To modify the default Receive connector for the source or target Exchange 2007/2010 organization to receive mail from the Internet, you can use either Exchange Management Console or Exchange Management Shell.
To modify the default Receive connector using Exchange Management Console
- Run Exchange Management Console. Select the Server Configuration | Hub Transport node.
- In the Hub Transport pane select the appropriate Hub Transport server.
- On the Receive Connectors tab, select the Default <Server Name> connector. In the Actions pane, click Properties for this connector.
- In Default <Server Name> Properties dialog box, open the Permission Groups tab.
- Select Anonymous Users to add anonymous permissions.
- Click OK to apply the settings.
To modify the default Receive connector using Exchange Management Shell
Run the following command:
Set-ReceiveConnector -PermissionGroups 'AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers' -Identity 'ServerName\Default ServerName'
Where ServerName is the Hub Transport server name.
Adding E-mail Domain Used for Redirection to the List of Accepted Domains on Hub Transport Server
To add a new Accepted domain on a computer that has the Hub Transport server role installed, you can use either Exchange Management Console or Exchange Management Shell.
To add a domain to Accepted Domains list using Exchange Management Console
- Run the Exchange Management Console and select the Organization Configuration | Hub Transport node.
- In the Actions pane, click New Accepted Domain. This will start the New Accepted Domain wizard.
- On the first page, provide the following information:
- Name—Specify the accepted domain in the user interface, such as source.local (target.local).
- Accepted Domain—Specify the SMTP namespace for which the Exchange organization will accept e-mail messages, such as *.source.local (*.target.local).
- Select the Authoritative Domain. E-mail is delivered to a recipient in this Exchange organization option for the accepted domain type.
- Click New.
- On the Completion page, click Finish.
To add a domain to Accepted Domains list using Exchange Management Shell
Run the following command for the source Exchange organization:
new-AcceptedDomain -Name 'source.local' -DomainName '*.source.local' -DomainType 'Authoritative'
where *.source.local is the address space you want to use for mail redirection from the target to the source organization.
Run the following command the target Exchange organization:
new-AcceptedDomain -Name 'target.local' -DomainName '*.target.local' -DomainType 'Authoritative'
where *.target.local is the address space you want to use for mail redirection from the source to the target organization.
Establishing Internet Mail Flow through a Subscribed Edge Transport Server
Establishing Internet Mail Flow through a Subscribed Edge Transport Server
The second option for establishing Internet mail flow between the target and the source Exchange organizations ( or between the source and the target Exchange organizations) is to subscribe the Edge Transport server to an Active Directory site. The connectors that establish mail flow to the Internet are created automatically when you subscribe an Edge Transport server to an Active Directory site by using the Edge Subscription process.
Before you begin this procedure, verify that the following prerequisites are met:
- Authoritative domains are configured on the Hub Transport server.
- E-mail address policies are configured on the Hub Transport server.
- Network communications over the secure LDAP port 50636/TCP are enabled through the firewall separating your perimeter network from the Exchange organization.
To establish mail flow to and from the Internet through a subscribed Edge Transport server, follow these steps:
- Export the Edge Subscription file from the Edge Transport server.
- Import the Edge Subscription file on the Hub Transport server.
- Force EdgeSync synchronization to begin on the Hub Transport server.
Each step is explained in further detail in the related subtopics.