Export (0) Print
Expand All

How to Configure Exchange 2007 to Route Messages for a Shared Address Space

 

Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007

Topic Last Modified: 2007-07-24

This topic explains how to use the Exchange Management Console or the Exchange Management Shell to configure a Microsoft Exchange Server 2007 Hub Transport server to route messages for a shared address space.

An organization may have to share the same Simple Mail Transfer Protocol (SMTP) address space between two or more different e-mail systems. For example, you may have to share the SMTP address space between Microsoft Exchange and a third-party e-mail system, or between Exchange environments that are configured in different Active Directory forests. In these scenarios, users in each e-mail system have the same domain suffix as part of their e-mail addresses.

To support these scenarios, you must create an accepted domain that is configured as an internal relay domain. You must also add a Send connector that is sourced on a Hub Transport server and configured to send e-mail to the shared address space. If an accepted domain is configured as authoritative and a recipient is not found in the Active Directory directory service, a non-delivery report (NDR) is returned to the sender. The accepted domain that is configured as an internal relay domain first tries to deliver to a recipient in the Exchange organization. If the recipient is not found, the message is routed to the Send connector that has the closest address space match. The receiving e-mail system is considered authoritative for the address space. It will deliver messages to all recipients in its directory and generate an NDR for invalid recipients.

To achieve the correct routing behavior, you must specify a Hub Transport server as the source server for the Send connector. If the Edge Transport server is specified as the source server for the Send connector, a routing loop will occur.

noteNote:
If Exchange 2007 coexists in an organization that is running Exchange Server 2003 or Exchange 2000 Server, you must configure the legacy recipient policy setting separately from the accepted domains configuration object. To configure an address space as shared on a server that is running Exchange 2003 or Exchange 2000, in Exchange System Manager, clear the This Exchange Organization is responsible for all mail delivery to this address check box in the SMTP Address Properties dialog box.

To perform the following procedures, the account you use must be delegated the following:

  • Exchange Organization Administrator role

For more information about permissions, delegating roles, and the rights that are required to administer Exchange 2007, see Permission Considerations.

The following procedures explain how to create the accepted domain that is configured as an internal relay domain and how to configure a Send connector to relay e-mail from Exchange 2007 to the e-mail system that shares the address space. The Send connector is configured to use a smart host. The smart host can be the IP address or fully qualified domain name (FQDN) of an e-mail server in the system that is sharing the address space or of the SMTP backbone. The SMTP backbone is the network connection between the two e-mail systems.

noteNote:
If you have configured an Edge Subscription, the accepted domain configuration is automatically replicated from the Exchange organization to the Edge Transport server. If you do not have an Edge Subscription, you must configure the Internal Relay accepted domain on both the Hub Transport server and the Edge Transport server. For more information, see Subscribing the Edge Transport Server to the Exchange Organization.

  1. Open the Exchange Management Console. In the console tree, expand Organization Configuration, select Hub Transport, and then in the work pane, click the Accepted Domains tab.

  2. In the action pane, click New Accepted Domain…. The New Accepted Domain wizard appears.

  3. On the New Accepted Domain page, complete the following fields:

    Name   Use this field to identify the accepted domain in the user interface. You can type any name that you want. We recommend that you select a meaningful name that helps you easily identify the purpose of this accepted domain. For example, you may want to use a name that identifies this as a subsidiary domain or as a hosted domain. You must use a unique name for each accepted domain.

    Accepted Domain   Use this field to identify the SMTP namespace for which the Exchange organization will accept e-mail messages. You can use a wildcard character to accept messages for a domain and all its subdomains. For example, you can type *.contoso.com to set Contoso.com and all its subdomains as accepted domains.

  4. After you complete these fields on the New Accepted Domain page, select the following option: Internal Relay Domain. E-mail is relayed to an e-mail server in another Active Directory forest in the organization.

  5. Click New.

  6. On the Completion page, click Finish.

  • Run the following command:

    New-AcceptedDomain -Name "Contoso" -DomainName Contoso.com -DomainType InternalRelay
    

For detailed syntax and parameter information, see New-AcceptedDomain.

  1. Open the Exchange Management Console. In the console tree, expand Organization Configuration, select Hub Transport, and then in the work pane, click the Send Connectors tab.

  2. In the action pane, click New Send Connector. The New SMTP Send Connector wizard starts.

  3. On the Introduction page, follow these steps:

    • In the Name: field, type a meaningful name for this connector. This name is used to identify the connector.
    • In the Select the intended use for this connector: field, select one of the following usage types for the connector. The usage type determines the default permission sets that are assigned on the connector and grants those permissions to trusted security principals.
      Internal   Select this usage type if the e-mail system with which Exchange 2007 shares an address space is another Exchange 2007 organization.
      Internet   Select this usage type if the e-mail system with which Exchange 2007 shares an address space is a third-party e-mail system.
      For more information about the Send connector usage types, see Send Connectors.
  4. Click Next.

  5. On the Address space page, click Add. In the Add Address Space dialog box, enter the domain name to which this connector will send mail, for example: contoso.com or *.contoso.com. You may select the Include all subdomains check box to use this connector to send e-mail to all subdomains of the address space. When you are finished, click OK. Click Next.

  6. On the Network settings page, select Route all mail through the following smart hosts. Click Add.

  7. In the Add Smart Host dialog box, select IP Address or Fully qualified domain name (FQDN) to specify how to locate the smart host. If you select IP Address, enter the IP address of the smart host. If you select Fully qualified domain name (FQDN), enter the FQDN of the smart host. The sending server must be able to resolve the FQDN. When you are finished, click OK. To add more smart hosts, click Add, and repeat this step. When you are finished, click Next.

  8. On the Smart host security settings page, select the method that is used to authenticate to the smart host. The following smart host authentication methods are available:

    • None
    • Basic Authentication
    • Basic Authentication over TLS
    • Exchange Server Authentication
    • Externally Secured
      For more information about the security settings, see Send Connectors.
  9. Click Next.

  10. On the Source Server page, click Add to add a source server. By default, the Hub Transport server that you are currently working on is listed as a source server. In the Select Hub Transport servers and Edge Subscriptions dialog box, select the Hub Transport servers that will be used as the source server for sending messages to the shared address space. When you finish adding source servers, click OK. Click Next.

  11. On the New Connector page, review the configuration summary for the connector. If you want to modify the settings, click Back. To create the Send connector by using the settings in the configuration summary, click New.

  12. On the Completion page, click Finish.

This section contains the Exchange Management Shell procedure that applies to the release to manufacturing (RTM) version of Exchange 2007.

  • Run the following command to create a Send connector that routes to a smart host, specifies the smart host by IP address, uses Externally Secured as the authentication mechanism, and sets a maximum message size limit of 20 MB. Use the Internal usage type if you share an address space with another Exchange organization. Use the Internet usage type if you share an address space with a third-party e-mail system:

    New-SendConnector -Name "Contoso.com Send Connector" -Usage <Internal | Internet> -AddressSpace Contoso.com -DnsRoutingEnabled $false -SmartHosts smarthost.domain.com -SmartHostAuthMechanism ExternalAuthoritative -MaxMessageSize 20MB
    

For detailed syntax and parameter information, see New-SendConnector (RTM).

This section contains the Exchange Management Shell procedure that applies to Exchange 2007 Service Pack 1 (SP1).

  • Run the following command to create a Send connector that routes to a smart host, specifies the smart host by IP address, uses Externally Secured as the authentication mechanism, and sets a maximum message size limit of 20 MB. Use the Internal usage type if you share an address space with another Exchange organization. Use the Internet usage type if you share an address space with a third-party e-mail system:

    New-SendConnector -Name "Contoso.com Send Connector" -<Internal | Internet> -AddressSpace Contoso.com -DnsRoutingEnabled $false -SmartHosts smarthost.domain.com -SmartHostAuthMechanism ExternalAuthoritative -MaxMessageSize 20MB
    

For detailed syntax and parameter information, see New-SendConnector.

To ensure that you are reading the most up-to-date information and to find additional Exchange Server 2007 documentation, visit the Exchange Server TechCenter.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft