Note
If an Edge Subscription is made with an Edge Transport server, a Send connector with an address space of “*” is configured automatically on the Hub Transport so that the Hub will send outgoing messages to the Edge Transport, which will send it to the Internet.
The Send connectors are configured at the Organization level, whereas the Receive connectors are configured on the Server level within the Navigation pane of your EMC. When you create these connectors, they are stored within the Active Directory.
Hub Transport servers can communicate between each other automatically because of implicit connectors that exist based upon the AD site topology. So, the primary focus of your Send and Receive connectors is to structure what happens when an email needs to come into your organization from an external source (either the Internet or an Edge Transport server) or when email needs to be sent out of your organization. When an email goes through a Hub Transport server and it sees that the SMTP address is not for any of the domains within the organization, it will route the message to a Send connector source server or servers (you can configure multiple source servers).
One of the interesting aspects of the default Receive connectors is that although they exist, they are not configured to allow you to receive email from anonymous users. Persons who attempt to send you email will most likely receive the message NDR with the error “530 5.7.1 Client was not authenticated.” You must alter the configuration of the Receive connector to allow anonymous users.
To create a Send connector, perform the following:
After the Send connector is created, you can go into the properties of the connector and make changes to any of the settings.
To create a Receive connector, perform the following:
Having mail come into your organization through a Receive connector allows you a modicum of control over the security involved and authentication allowed for that mail. After you have the Receive connector created, you can return to the Properties of the connector and make adjustments. Two tabs available to you that were not part of the creation process are the Authentication tab and the Permission Groups tab.
Under the Authentication tab, shown in Figure 1 , you can specify which security mechanisms are available for incoming connections, including the following:
Transport Layer Security (TLS)
Enable Domain Security (Mutual Auth TLS)
Basic Authentication
Offer Basic Authentication Only After Starting TLS
Exchange Server Authentication
Integrated Windows Authentication
Externally Secured (for example, with IPsec)
Permission Groups options include the following:
Anonymous Users
Exchange Users
Exchange Servers
Legacy Exchange Servers
Partners