Share via


New SMTP Receive Connector Wizard > Local Network Settings Page (RTM)

Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

 

Applies to: Exchange Server 2007, Exchange Server 2007 SP1

Use the Local Network Settings page of the New SMTP Receive Connector wizard to specify the local IP addresses for which the Receive connector will receive e-mail messages. The Local network settings page appears only if you selected a usage type of Custom, Partner, or Internet on the Introduction page.

  • Add
    To add one or more IP addresses, click Add. You can use all available IP addresses or specify a single IP address.

    Note

    You must specify a local IP address that is valid for the Hub Transport server or Edge Transport server on which the Receive connector is located. If you specify an invalid local IP address, the Microsoft Exchange Transport service may fail to start when the service is restarted. To specify all IP addresses that are configured on all network adapters, you can select Use all IP addresses available on this server.

  • Edit
    To change an existing IP address, select the IP address, and then click Edit.
  • Remove
    To remove an IP address from the list of local IP addresses, select the IP address, and then click Remove icon.
  • Specify the (FQDN) this connector will provide in response to HELO or EHLO
    This field specifies the fully qualified domain name (FQDN) that is used as the destination server for connected messaging servers that use the Receive connector to send incoming messages. The value of this field is displayed to connected messaging servers whenever a destination server name is required, as in the following examples:

    • In the default SMTP banner of the Receive connector

    • In the EHLO/HELO response of the Receive connector

    • In the most recent Received: header field in the incoming message when the message enters the Hub Transport server or Edge Transport server

    • During Transport Layer Security (TLS) authentication

For More Information

For more information, see the following topics: