Exxhange SQL And IIS- P74 docx

The reason behind this is that implicit, and invisible, Send connectors are automatically computed based on the Active Directory site topology, and based on the topology internal messag

connector is not created by default, this doesn’t mean that internal Hub Transport servers cannot deliver a

message to another internal Hub Transport server The reason behind this is that implicit, and invisible, Send

connectors are automatically computed based on the Active Directory site topology, and based on the topology internal messages they are then routed between the Hub Transport servers in the organization Send connectors are stored in Active Directory, and when such a connector is created, their scope

is global, not local like receive connectors

If you don’t have an Edge Transport server deployed in your organization’s perimeter network, or

if no Edge Subscription has been confi gured (which creates a Send connector automatically), you cannot send mail to other e-mail servers outside your organization In this case, you must create a Send connector manually To do so, perform the following steps:

1 Click the Send Connectors tab shown back in Figure 6.2

2 Select New Send Connector in the Action pane

3 The New SMTP Send Connector page will appear On this Introduction page, enter

a descriptive name (such as To ISP or To Internet) for the connector, and then select the type

Figure 6.20 A Test Journal Report Message

of Send connector you want to create, as in the drop-down box shown in Figure 6.21

As you can see, you can choose between four different types of Send connectors:

■ Custom Select Custom in order to create a customized connector used to connect with other systems that are not Exchange servers

■ Internal Internal Send connectors are used to send e-mail to servers in your

Exchange organization When selected, the connector will be confi gured to route

e-mail to your internal Exchange servers as smart hosts

■ Internet Internet Send connectors are used to send e-mail to the Internet When

selected, the connector will be confi gured to use Domain Name System (DNS) MX

records to route e-mail

Figure 6.21 Selecting the Required Send Connector Type

■ Partner Partner Send connectors are used to send e-mail to partner domains When selected, this connector will be confi gured to only allow connections to servers that authenticate with Transport Layer Security (TLS) certifi cates for Simple Mail Transfer Protocol (SMTP) domains that are included in the list of domain-secured domains

You can add domains to this list by using the -TLSSendDomainSecureList parameter in the Set-TransportConfi g command.

4 On the Address space page shown in Figure 6.22, enter the domain or domains to which the Send connector should route mail If the connector should be used to route outbound

mail to the Internet simply add an asterisk (*) When ready click Next.

Figure 6.22 Specifying the Address Space

5 On the Network Settings page shown in Figure 6.23, specify how you want to send mail with the connector Here, you can choose to use Domain Name System (DNS) “MX”

records to route the mail automatically, or you can choose to have all mail routed to a

specifi ed smart host

Figure 6.23 Confi guring Network Settings

If you’re a small shop using a cheap ISP that doesn’t allow outbound traffi c on

port 25 from your DSL, you typically need to route outbound mail through a smart

host located at your ISP

6 If you elected to use a smart host in the previous step, you now need to confi gure the authentication method used to properly authenticate with the specifi ed smart host If this is

a smart host located at your ISP, you typically don’t need to authenticate, and can safely

select None, as shown in Figure 6.24 Click Next.

7 Now it’s time to associate the connector with a Hub Transport server in the organization (Figure 6.25) The wizard will try to do this for you, but you can change the selection if

required Click Next.

Figure 6.24 Confi guring the Smart Host Authentication Settings