How to View the Configuration of a Send Connector
Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007
Topic Last Modified: 2007-06-15
This topic explains how to use the Exchange Management Console or the Exchange Management Shell to view the configuration of an existing Send connector for a computer that has the Microsoft Exchange Server 2007 Edge Transport server role or the Hub Transport server role installed.
In Exchange 2007, Send connectors are responsible for outbound transmission of e-mail messages. Multiple Send connectors can exist for an organization to support the need for specific configurations. For example, some e-mail systems may require that messages be sent to a smart host, and messages that are sent to some destinations may require authentication.
Use the procedures in this topic to view the configuration of existing Send connectors.
To perform the following procedures, the account you use must be delegated the following:
Exchange View-Only Administrator role
To perform the following procedures on a computer that has the Edge Transport server role installed, you must log on by using an account that is a member of the local Administrators group on that computer.
For more information about permissions, delegating roles, and the rights that are required to administer Exchange Server 2007, see Permission Considerations.
Open the Exchange Management Console. Perform one of the following steps:
To view the configuration of an existing Send connector on an Edge Transport server, in the console tree, select Edge Transport, and then in the work pane, click the Send Connectors tab.
To view the configuration of an existing Send connector on a Hub Transport server, in the console tree, expand Organization Configuration, and select Hub Transport.
In the work pane, click the Send Connectors tab, select a Send connector, and then in the action pane, click Properties to open the Properties page.
Click the General tab to view information about the connector status, protocol logging level, and the fully qualified domain name (FQDN) that is advertised in the Simple Mail Transfer Protocol (SMTP) EHLO verb.
Note: In Microsoft Exchange Server 2007 Service Pack 1 (SP1), you can also use the General tab to view the maximum message size that is allowed on the connector.
Click the Address Space tab to view the address spaces that are defined on the connector. For more information about address spaces, see Send Connectors.
Note: In Exchange 2007 SP1, you can also use the Address Space tab to view the scope of the connector. Scoped connectors can only be used by other Hub Transport servers that exist in the same Active Directory site. Non-scoped connectors can be used by all Hub Transport servers in the Exchange organization.
To see whether the connector is using DNS to resolve which server to send messages to or is forwarding all messages to a smart host, click the Network tab.
To view the Hub Transport servers and Edge Subscriptions that are associated with this connector, click the Source Server tab. The Source Server tab is available only on Hub Transport servers.
To view the configuration for a single Send connector when you use the Exchange Management Shell, you specify an identity. The identity of a connector is either its GUID or the friendly name that was assigned to the connector when the connector was created. If you do not specify an identity, the command returns the configuration information for all Send connectors.
To view a summary list of all Send connectors, run the following command:
To view the detailed configuration for a single Send connector, run the following command:
Get-SendConnector <Connector Identity> | Format-List
For example, to view the detailed configuration for a Send connector named "Contoso.com Send Connector", run the following command:
Get-SendConnector "Contoso.com Send Connector" | Format-List
For detailed syntax and parameter information, see Get-SendConnector.
For more information about pipelining, see Pipelining.
For more information about working with the information that a command returns, see Working with Command Output.