Saturday, June 9, 2007

Set-Sendconnector

In my Exchange environment I have 2 SMTP Gateways. 1 Active 1 Passive.
I created 2 Send Connectors but I was unsure how to weight the 2.

Power Shell Command
The first command I used was :

set-sendconnector -id SMTPGT2 smtp:*;2


Which did not give me an error, and it did not change anything!

So I think the smtp:*;2 is considered a multi value string or something to that effect.
I put it in Quotes "" and it worked just fine.

set-sendconnector -id SMTPGT2 "smtp:*;2"

Here are the parameter for the AddressSpaces on a sendconnector.

This parameter is required unless this connector is linked to a Receive connector. If a linked Receive connector is specified by using the LinkedReceiveConnector parameter, the value of AddressSpaces must be $null. Otherwise, the AddressSpaces parameter specifies the domain names to which the Send connector sends messages. You may specify multiple address spaces by separating the address spaces with commas. The complete syntax for entering each address space is as follows:

<ConnectorScope>:<AddressSpaceType>:<AddressSpace>;<AddressSpaceCost>

  • ConnectorScope If you specify a value of Local, the connector can only be used by other Hub Transport servers that exist in the same Active Directory site as the source Hub Transport server on which you are running the New-SendConnector cmdlet. If you omit the ConnectorScope qualifier, the connector can be used by all Hub Transport servers that exist in the whole Exchange 2007 organization.
  • AddressSpaceType For SMTP address spaces, this value must be SMTP. For non-SMTP address spaces, this value may be any descriptive text string, such as "Lotus Notes".
  • AddressSpace For SMTP address spaces, the domain name system (DNS) wildcard character (*) as defined in RFC 1035 can be used. For example, you can use "*", "*.com.", or *.contoso.com". For non-SMTP address spaces, you can use wildcard characters (*) and other characters, such as "*contoso.com" or "@contoso".
  • AddressSpaceCost The valid input range for the cost is 1 to 100. A lower cost indicates a better route. This parameter is optional. If you omit the AddressSpaceCost qualifier when you enter an address space by using the complete syntax, a cost of 1 is assumed.

You only need to use the complete syntax for the AddressSpaces parameter for the following conditions:

  • Scoped connectors that have the Local qualifier
  • Non-SMTP address spaces
  • SMTP address spaces with a cost other than 1

If you enter a domain name or a comma separated list of domain names for the value of the AddressSpaces parameter, the address space type of SMTP and a cost of 1 is assumed for each domain name. Send connectors that are configured on Edge Transport servers only support SMTP address spaces. Send connectors that are configured on Hub Transport servers support SMTP and non-SMTP address spaces.

No comments: