Connector Properties > General Tab (RTM)

  • Article

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 General tab on the connector properties to manage a connector on a computer that has the Hub Transport server role or Edge Transport server role installed.

  • Connector status
    This field shows whether the connector is enabled or disabled. To change the setting, in the action pane, click Enable or Disable as appropriate.
  • Modified
    This field shows the last date that the connector settings were modified.

  • Protocol logging level
    Use this field to select the protocol logging level:

    • None   To turn off protocol logging, select this option.

    • Verbose   To turn on protocol logging, select this option.

  • Specify the FQDN this connector will provide in response to HELO or EHLO
    For Receive connectors, 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

    Note

    Don’t modify the FQDN value on the default Receive connector named “Default <Server Name>” that is automatically created on Hub Transport servers. If you have multiple Hub Transport servers in your Exchange organization and you change the FQDN value on the “Default <Server Name>” Receive connector, internal mail flow between Hub Transport servers will fail.

    For Send connectors, this field specifies the FQDN that is used as the source server for connected messaging servers that use the Send connector to receive outgoing messages. The value of this field is displayed to connected messaging servers whenever a source server name is required, as in the following examples:

    • In the EHLO/HELO command when the Send connector communicates with the next hop messaging server

    • In the most recent Received: header field of the message that is added to the message by the next hop messaging server after the message leaves the Hub Transport server or Edge Transport server

    • During TLS authentication

    Note

    If the Send connector is configured on a Hub Transport server that also has the Mailbox server role installed, any value that you specify for this field is not used. Instead, the FQDN of the server that is displayed by using the Get-ExchangeServer cmdlet is always used.
    For servers that have both the Hub Transport server role and the Mailbox server role installed, the only way to remove the server name from the Received: headers of the outgoing message is to use the Remove-ADPermission cmdlet to remove the Ms-Exch-Send-Headers-Routing permission from the security principals that use the connector. This action will remove all the Received: headers from the message as the message leaves the Hub Transport server. We recommend that you don't remove the Received: headers for internal messages, because the Received: headers are used for maximum hop count calculations. For more information about the Remove-ADPermission cmdlet and the Get-ExchangeServer cmdlet, see the following topics:
    • Remove-ADPermission (RTM)
    • Get-ExchangeServer (RTM)

For More Information

For more information about connectors, see the following topics:

For more information about protocol logging, see Managing Protocol Logging.