Applies to: Exchange Server 2007 SP3, Exchange Server
2007 SP2, Exchange Server 2007 SP1
Topic Last Modified: 2007-11-08
Use the General tab on the Send connector properties to manage a Send connector on a computer that has the Hub Transport server role or Edge Transport server role installed.
- Connector name
To rename the connector, type a new name in the connector name field, and then click Apply.
- 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.
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.
- None To turn off protocol logging, select this option.
- 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 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 Transport Layer Security (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 the FQDN 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-Routingpermission 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:
- In the EHLO/HELO command when the Send connector communicates with the next hop messaging server
- Maximum message size (KB)
To set a maximum message size for messages that can pass through this connector, select the check box next to Maximum message size (KB) and enter a value in kilobytes. The valid input range is 0 to 2147483647 kilobytes. To remove any restriction on the maximum message size, clear the check box next to Maximum message size (KB).