2. Send Connectors
Although receive connectors are configured for each
server, send connectors are organizational connectors that you can
assign to a number of different Hub Transport servers. Each server also
has an implicit send connector, but that connector is used only for
transferring mail to other Hub Transport servers. The implicit send
connector does not show up either in the Exchange Management Console
(EMC) or when you use the Exchange Management Shell (EMS), and there
are no properties that can be set for the implicit send connector. In
fact, that connector does not exist unless it is needed. It is created
in memory whenever a message needs to be sent between Hub Transport
servers. The implicit send connector cannot be used to deliver messages
to the Internet or to an external host directly.
Send connectors are managed in the EMC under the Hub Transport subcontainer of the Organization Configuration work center. Figure 3 shows the Source Server properties for a connector called From Exchange 2010 to the World.
The Source Server properties page is where you
designate which Hub Transport servers will deliver messages for this
particular send connector. When you assign more than one Hub Transport
server as a source server, the outbound messaging load will be
load-balanced among the source servers. You can view the properties of
this send connector also using the EMS cmdlet Get-SendConnector; here is an example:
Get-SendConnector "From Exchange 2010 to the World" | FL
AddressSpaces : {SMTP:*;1}
AuthenticationCredential :
Comment :
ConnectedDomains : {}
ConnectionInactivityTimeOut : 00:10:00
DNSRoutingEnabled : True
DomainSecureEnabled : False
Enabled : True
ForceHELO : False
Fqdn :
HomeMTA : Microsoft MTA
HomeMtaServerId : EX2010
Identity : From Exchange 2010 to the World
IgnoreSTARTTLS : False
IsScopedConnector : False
IsSmtpConnector : True
LinkedReceiveConnector :
MaxMessageSize : 10 MB (10,485,760 bytes)
Name : From Exchange 2010 to the World
Port : 25
ProtocolLoggingLevel : None
RequireTLS : False
SmartHostAuthMechanism : None
SmartHosts : {}
SmartHostsString :
SmtpMaxMessagesPerConnection : 20
SourceIPAddress : 0.0.0.0
SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers : {EX2010}
UseExternalDNSServersEnabled : False
Because Exchange Server 2010 does not have a default
SMTP connector for outbound mail, you will need to create at least one
send connector. Most organizations will need to create only a single
send connector; this connector will be used to send mail to the
Internet, to an Edge Transport server, or to an SMTP smart host system
that will deliver mail to the Internet on behalf of the Exchange server.
2.1. Creating a Send Connector
This section goes through an example of creating a
send connector that will be responsible for sending mail to the
Internet. In the Hub Transport subcontainer of the Organization
Configuration work center, make sure the Send Connectors tab is
highlighted, and then click the New Send Connector task in the Actions
pane. This launches the New SMTP Send Connector wizard shown in Figure 4. On the Introduction page, you must provide the name of the connector and specify the intended use of the connector.
The wizard will allow you to create four types
(intended use options) of send connectors, but these are just
predefined configurations and you can always change the properties of
the connector you create later. The four types of send connectors you
can create are as follows:
The Custom Send connector type allows you to
manually configure all the configuration settings at some point after
the connector is created.
The
Internal Send connector type allows you to configure a connector that
connects to Edge Transport servers in your organization or servers in
another organization. Because all internal mail routing is automatic,
you will usually not need to create an internal send connector to
another Hub Transport server in your organization.
The Internet Send connector type is used to send mail to the Internet using DNS MX records.
The
Partner Send connector type creates a connector that will be used to
send mail to specific Internet domains and will use certificate
authentication and TLS encryption.
On the Address Space page of the wizard, you can
specify the SMTP domains to which this send connector will deliver
email. Because this connector is going to send mail to the Internet,
use an address space of * for this example. The * address space
represents all SMTP addresses that are not explicitly defined on
another connector.
On the Network Settings properties page, you can
configure Smart Host if you want mail to be delivered to another SMTP
host for external delivery, such as with an Edge Transport server, or
you can select Use Domain Name System (DNS) "MX" Records To Route Mail
Automatically. If you use DNS for mail delivery, this send connector
will be responsible for all outbound mail delivery.
The Source Server page allows you to specify the Hub
Transport servers that will deliver mail for this send connector. If
you have more than one Hub Transport server, we recommend you use
additional Hub Transport servers for redundancy.
Once you click the New button on the New Connector
page, the EMC will execute the command necessary to create the new send
connector. The following is the EMS command that executes:
New-SendConnector -Name 'Internet Connector' -Usage 'Internet'
-AddressSpaces 'smtp:*;1' -DNSRoutingEnabled $true
-UseExternalDNSServersEnabled $false -SourceTransportServers 'EX2010'
Once you have created the connector, you should make
one additional configuration option. On the General properties page of
the send connector, enter the public name of the FQDN for this server,
such as MAIL.NETLOGON.COM.
This is the name that the send connector uses in the EHLO or HELO
command when it connects to a remote SMTP system. If you don't specify
an FQDN for the connector to use, the connector will use the default
FQDN for the server. Often this is an internal name that is not
recognized on the Internet. Some Internet hosts will reject a
connection if the name cannot be resolved.
