Open the Exchange Management Console. Perform one of the following steps:

1. On a computer that has the Edge Transport server role installed, select Edge Transport, and then in the work pane, click the Send Connectors tab.
   
   
2. To create a Send connector on a Hub Transport server role, in the console tree, expand Organization Configuration, select Hub Transport, and then in the work pane, click the Send Connectors tab.
   
   

In the action pane, click New Send Connector. The New SMTP Send Connector wizard starts.

On the Introduction page, follow these steps:

1. In the Name: field, type a meaningful name for this connector. This name is used to identify the connector.
   
   
2. In the Select the intended use for this connector: field, select the usage type for the connector. The usage type determines the default permission sets that are assigned on the connector and grants those permissions to trusted security principals.
   
   Custom   Select this option to create a customized connector that will be used to connect with systems that are not Exchange servers.
   
   Internal   Internal Send connectors are used to send e-mail to servers in your Exchange organization. This connector will be configured 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. This connector will be configured to use Domain Name System (DNS) MX records to route e-mail.
   
   Partner   Partner Send connectors are used to send e-mail to partner domains. This connector will be configured to only allow connections to servers that authenticate with Transport Layer Security (TLS) certificates 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-TransportConfig command.
   
   For more information about the Send connector usage types, see Send Connectors. Click Next.
   
   

On the Address space page, do one of the following:

On a Hub Transport server or Edge Transport server, click Add. In the Add Address Space dialog box, enter the SMTP address space as follows, for example: contoso.com. You can include the wildcard character (*) in the address space as defined in RFC 1035. For example, "*", "*.com", and "*.contoso.com" are permitted, but "*contoso.com" is not permitted.

On the Network settings page, select how to send e-mail with the Send connector. The following options are available:

• Use domain name system (DNS) "MX" records to route mail automatically   This option is available only if you selected a usage type of Custom, Partner, or Internet in step 3. When you select this option, the Send connector uses the DNS client service on the sending server to query a DNS server and resolve the destination address.
  
  
• Route all mail through the following smart hosts   This option is available only if you selected a usage type of Custom, Internal, or Internet in step 3. When you select this option, follow these steps:
  
  

1. Click Add. In the Add Smart Host dialog box, select IP Address or Fully qualified domain name (FQDN) to specify how to locate the smart host. If you select IP Address, enter the IP address of the smart host. If you select Fully qualified domain name (FQDN), enter the FQDN of the smart host. The sending server must be able to resolve the FQDN. When you are finished, click OK.
   
   To add more smart hosts, click Add, and repeat this step.
   
   To edit the settings of a smart host, select the smart host, and then click Edit.
   
   To remove an existing smart host, select the smart host, and then click .
   
   When you are finished, click Next.
   
   
2. On the Smart host security settings page, select the method that is used to authenticate to the smart host. The available smart host authentication methods are None, Basic Authentication, Basic Authentication over TLS, Exchange Server Authentication, and Externally Secured. For more information about the security settings, see Send Connectors. Click Next.
   
   

The Source Server page only appears on Hub Transport servers. By default, the Hub Transport server that you are currently working on is listed as a source server. To add a source server, click Add. In the Select Hub Transport servers and Edge Subscriptions dialog box, select the Hub Transport servers or the subscribed Edge Transport servers that will be used as the source server for sending messages to the address space that you provided in step 5. The list of source servers can contain all Hub Transport servers or all subscribed Edge Transport servers, but not a mix of both. When you are finished adding additional source servers, click OK.

To add more source servers, click Add and repeat this step.

To remove an existing source server, select the source server, and then click .

When you are finished, click Next.

On the New connector page, review the configuration summary for the connector. If you want to modify the settings, click Back. To create the Send connector by using the settings in the configuration summary, click New.

On the Completion page, click Finish.

Open the Exchange Management Console. Perform one of the following steps:

1. On a computer that has the Edge Transport server role installed, select Edge Transport, and then in the work pane, click the Send Connectors tab.
   
   
2. To create a Send connector on a Hub Transport server role, in the console tree, expand Organization Configuration, select Hub Transport, and then in the work pane, click the Send Connectors tab.
   
   

In the action pane, click New Send Connector. The New SMTP Send Connector wizard starts.

On the Introduction page, follow these steps:

1. In the Name: field, type a meaningful name for this connector. This name is used to identify the connector.
   
   
2. In the Select the intended use for this connector: field, select the usage type for the connector. The usage type determines the default permission sets that are assigned on the connector and grants those permissions to trusted security principals.
   
   Custom   Select this option to create a customized connector that will be used to connect with systems that are not Exchange servers.
   
   Internal   Internal Send connectors are used to send e-mail to servers in your Exchange organization. This connector will be configured 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. This connector will be configured to use Domain Name System (DNS) MX records to route e-mail.
   
   Partner   Partner Send connectors are used to send e-mail to partner domains. This connector will be configured to only allow connections to servers that authenticate with Transport Layer Security (TLS) certificates 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-TransportConfig command.
   
   For more information about the Send connector usage types, see Send Connectors. Click Next.
   
   

On the Address space page, do one of the following:

1. On a Hub Transport server or Edge Transport server, click Add or the drop-down arrow located next to Add and select SMTP Address Space. Enter the following information in the SMTP Address Space dialog box:
   
   • Address   Enter the SMTP address space as follows, for example: contoso.com. You can include the wildcard character (*) in the address space as defined in RFC 1035. For example, "*", "*.com", and "*.contoso.com" are permitted, but "*contoso.com" is not permitted.
   
   To also use this connector to route mail to all subdomains of the specified address space, select Include all subdomains. If you entered an address space that contains the wildcard character, Include all subdomains is automatically selected.
   
   • Cost   Use the address space cost to set the selection priority when more than one Send connector is configured for the same address space. During routing resolution, when the connector selection is made, the least cost routing path to the destination address space is selected. The default cost is set to 1. The valid input range is 1 to 100.
   
   
2. On a Hub Transport server, click the drop-down arrow located next to Add and select Custom Address Space. Enter the following information in the Custom Address Space dialog box:
   
   • Type   This field describes the address space that you enter in the Address field. If you enter SMTP or X400 in the Type field, Exchange 2007 monitors the syntax of the address space that you enter in the Address field. If you enter any other text string in the Type field, the Address field becomes free-form text.
   
   • Address   If you specified SMTP in the Type field, the address space that you enter must be RFC 1035-compliant. For example, "*", "*.com", and "*.contoso.com" are permitted, but "*contoso.com" is not permitted. If you entered X400 in the Type field, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. If you enter any other text string in the Type field, you can enter any text for the address space.
   
   • Cost   Use the address space cost to set the selection priority when more than one Send connector is configured for the same address space. During routing resolution, when the connector selection is made, the least cost routing path to the destination address space is selected. The valid input range is 1 to 100.
   
   

   Note:

   Although you can configure non-SMTP address spaces on a Send connector on a Hub Transport server, the Send connector uses SMTP as the transport mechanism to send messages to other messaging servers. Foreign connectors on Hub Transport servers are used to send messages to local messaging servers, such as third-party fax gateway servers, which don't use SMTP as their primary transport mechanism. For more information, see Foreign Connectors.

   To add more address spaces to this connector, repeat this step.
   
   To modify an existing address space in the address space list, select the address space, and then click Edit.
   
   To remove an existing address space, select the address space, and then click .
   
   To allow all the Hub Transport servers in the Exchange organization to use this Send connector, don't select Scoped Send connector. To limit the scope of this Send connector so that it can be used only by other Hub Transport servers that exist in the same Active Directory site, select Scoped Send connector.
   
   When you are finished, click Next.
   
   

On the Network settings page, select how to send e-mail with the Send connector. The following options are available:

• Use domain name system (DNS) "MX" records to route mail automatically   This option is available only if you selected a usage type of Custom, Partner, or Internet in step 3. When you select this option, the Send connector uses the DNS client service on the sending server to query a DNS server and resolve the destination address.
  
  
• Route all mail through the following smart hosts   This option is available only if you selected a usage type of Custom, Internal, or Internet in step 3. When you select this option, follow these steps:
  
  

1. Click Add. In the Add Smart Host dialog box, select IP Address or Fully qualified domain name (FQDN) to specify how to locate the smart host. If you select IP Address, enter the IP address of the smart host. If you select Fully qualified domain name (FQDN), enter the FQDN of the smart host. The sending server must be able to resolve the FQDN. When you are finished, click OK.
   
   To add more smart hosts, click Add, and repeat this step.
   
   To edit the settings of a smart host, select the smart host, and then click Edit.
   
   To remove an existing smart host, select the smart host, and then click .
   
   When you are finished, click Next.
   
   
2. On the Smart host security settings page, select the method that is used to authenticate to the smart host. The available smart host authentication methods are None, Basic Authentication, Basic Authentication over TLS, Exchange Server Authentication, and Externally Secured. For more information about the security settings, see Send Connectors. Click Next.
   
   

The Source Server page only appears on Hub Transport servers. By default, the Hub Transport server that you are currently working on is listed as a source server. To add a source server, click Add. In the Select Hub Transport servers and Edge Subscriptions dialog box, select the Hub Transport servers or the subscribed Edge Transport servers that will be used as the source server for sending messages to the address space that you provided in step 5. The list of source servers can contain all Hub Transport servers or all subscribed Edge Transport servers, but not a mix of both. When you are finished adding additional source servers, click OK.

To add more source servers, click Add and repeat this step.

To remove an existing source server, select the source server, and then click .

When you are finished, click Next.

On the New connector page, review the configuration summary for the connector. If you want to modify the settings, click Back. To create the Send connector by using the settings in the configuration summary, click New.

On the Completion page, click Finish.

At the Exchange Management Shell command prompt, type New-SendConnector and then press ENTER.

At the Address Spaces[0]: prompt, type the address space to which this connector will send messages. The complete syntax for entering each address space is as follows:

	Copy Code
<Connector Scope>:<Address Space Type>:<Address Space>;<Address Space Cost>

The connector scope controls the availability of the connector to other Hub Transport server in the organization. If you specify a value of Local, the connector can only be used by other Hub Transport servers in the same Active Directory site. If you omit the connector scope qualifier, the connector can be used by all Hub Transport servers in the Exchange 2007 organization.

On an Edge Transport server, the address space type must be SMTP. On a Hub Transport server, the address space type may be SMTP, X400, or any other text string. If you use a non-SMTP address space type, you must use a smart host to route e-mail. If you omit the address space type, an SMTP address space type is assumed. If you omit the address space cost, a cost of 1 is used. For example, the following address space entries are equivalent:

• SMTP:contoso.com;1
  
  
• contoso.com;1
  
  
• SMTP:contoso.com
  
  
• contoso.com
  
  

For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, *, *.com, and *.contoso.com are permitted, but *contoso.com is not permitted. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of address type, you can enter any text for the address space. If you enter a non-SMTP address space that contains the semicolon character ( ; ), you must specify the address space cost.

When you are finished entering the address space, press Enter.

At the Address Spaces[1] prompt, do one of the following:

1. If you want to configure additional address spaces for this connector, enter another address space and press Enter. Repeat this step for each additional address space that you want to configure for this connector.
   
   
2. If you are finished entering address spaces, don't enter an address space at the Address Spaces[1] prompt. Press Enter to continue.
   
   

At the Name: prompt, type a name for this connector. Press Enter to create the connector and display the connector summary.

At the Exchange Management Shell command prompt, type New-SendConnector and then press ENTER.

At the Address Spaces[0]: prompt, type the address space to which this connector will send messages. The complete syntax for entering each address space is as follows:

	Copy Code
<Address Space Type>:<Address Space>;<Address Space Cost>

On an Edge Transport server, the address space type must be SMTP. On a Hub Transport server, the address space type may be SMTP, X400, or any other text string. If you use a non-SMTP address space type, you must use a smart host to route e-mail. If you omit the address space type, an SMTP address space type is assumed. If you omit the address space cost, a cost of 1 is used. For example, the following address space entries are equivalent:

• SMTP:contoso.com;1
  
  
• contoso.com;1
  
  
• SMTP:contoso.com
  
  
• contoso.com
  
  

For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, *, *.com, and *.contoso.com are permitted, but *contoso.com is not permitted. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of address type, you can enter any text for the address space. If you enter a non-SMTP address space that contains the semicolon character ( ; ), you must specify the address space cost.

When you are finished entering the address space, press Enter.

At the Address Spaces[1] prompt, do one of the following:

1. If you want to configure additional address spaces for this connector, enter another address space and press Enter. Repeat this step for each additional address space that you want to configure for this connector.
   
   
2. If you are finished entering address spaces, don't enter an address space at the Address Spaces[1] prompt. Press Enter to continue.
   
   

At the Name: prompt, type a name for this connector. Press Enter to create the connector and display the connector summary.