|
Article ID: 321721 - View products that this article applies to. This article was previously published under Q321721 On This PageINTRODUCTION This article describes how to configure Microsoft Exchange
Server 2003 or Microsoft Exchange 2000 Server to support a shared SMTP address
space. For more information about how to configure Exchange Server 5.5 to share Simple Mail Transfer Protocol (SMTP) domain name space, click the following article number to view the article in the Microsoft Knowledge Base: 258203
(http://support.microsoft.com/kb/258203/
)
How to configure Exchange to share SMTP domain name space
MORE INFORMATIONBusiness requirements may require that you share the same
SMTP address space between two or more different e-mail systems. For an
Exchange Server environment, this may mean that you have to share the SMTP
address space between Exchange Server and a UNIX-based e-mail system or between
Exchange environments that are configured in different Active Directory
forests. In this situation, users in each e-mail system have the same domain
suffix as part of their e-mail addresses. For the purposes of this article, the terms "address space" and "domain" are used interchangeably. This article is written from the perspective that the Exchange server is the incoming SMTP gateway from the Internet. When Exchange receives an incoming SMTP message from the Internet, Exchange first tries to resolve the e-mail addresses that are displayed in the recipient fields to objects in Active Directory. If the e-mail address resolves to an Exchange mailbox, Exchange routes the message to the mailbox. If the e-mail address does not resolve to an Exchange mailbox, Exchange routes the message to the e-mail system with which the SMTP address space is shared. The receiving e-mail system then delivers the message to a local mailbox, or it generates a non-delivery report (NDR) delivery status notification (DSN) message. The e-mail system with which the SMTP address space is shared cannot forward the unresolved recipients back to the Exchange incoming SMTP gateway. If you configure the last e-mail system that is in an e-mail system chain to forward unresolved recipients to the incoming e-mail gateway, you will have a messaging loop in which e-mail messages may continuously loop between e-mail servers. Method 1: Share the same SMTP address space with a different e-mail systemOnly one e-mail system can be authoritative for a particular SMTP address space. When an e-mail system is non-authoritative for an SMTP address space, the e-mail must eventually be routed to an e-mail system that is authoritative for the SMTP address space. This behavior occurs to make sure that a non-delivery report is generated if an e-mail message cannot be delivered to a recipient. An SMTP address space can be shared with any number of different e-mail systems. In this configuration, each e-mail system is a link in a chain of e-mail systems. The first e-mail system in the chain sends messages to the second e-mail system, and so on. This behavior continues until the message is delivered to a recipient or until the last e-mail system in the chain generates a non-delivery report for the message.Exchange must be authoritative for the primary SMTP address space that is specified in the default recipient policy. Exchange does not have to be authoritative for any other SMTP address space. In this situation, you only have to add the shared SMTP address space to another recipient policy, set that SMTP address space as the primary SMTP address space, and then click to clear the This Exchange Organization is responsible for all mail delivery to this address check box in the SMTP Address Properties dialog box. Important You cannot share an SMTP address space for which Exchange is authoritative. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 823158
(http://support.microsoft.com/kb/823158/
)
Authoritative and nonauthoritative domains in Exchange 2000 Server and in Exchange Server 2003
Recipient policies dictate the SMTP address spaces for which Exchange is authoritative. To determine whether Exchange is authoritative for a particular SMTP address space, follow these steps:
Step 1: Modify the primary SMTP address for the default recipient policyIf you want to share the SMTP address space that is specified as the primary SMTP address space in the default recipient policy, you must create a new SMTP address space to act as the primary SMTP address space in the default recipient policy. The new primary SMTP address space that you create does not have to be valid in the Internet DNS. You can use a private SMTP address space such as @localhost or @example.local. This address space is the SMTP address space that Exchange will use to route internal e-mail messages.To modify the primary SMTP address space that is specified in the default recipient policy, follow these steps. Note By default, the domain that you specify when you install Active Directory is the SMTP address space for which Exchange is authoritative. If this SMTP address space is not the SMTP address space that you want to share, skip steps a through g. Instead, go to "Step 2: Configure the shared SMTP address space." These steps only apply if Exchange is authoritative for the SMTP address space that you want to share.
Step 2: Configure the shared SMTP address spaceTo configure the shared SMTP address space, follow these steps:
Step 3: Modify the SMTP virtual server properties to remove message forwarding for unresolved recipientsTo do this, follow these steps:
Step 4: Configure an SMTP connector for the shared SMTP address spaceAfter you configure the shared SMTP address space, you must specify the means for Exchange to determine where to route messages that do not resolve to an object in Active Directory. To do this, create an SMTP connector that has the shared SMTP address space in the Add Address Space dialog box of the connector object. If you do not add the SMTP connector with the shared address space, any incoming e-mail that is destined to the shared SMTP address space is interpreted as an attempt to relay. In this situation, Exchange does not accept the incoming e-mail. Additionally, you must specify a server to which Exchange will forward unresolved e-mail. You can specify this destination server by using its host name or by using its IP address.To configure the SMTP connector, follow these steps:
Step 5: Restart the Routing and SMTP servicesTo do this, follow these steps:
Method 2: Share the SMTP address space by using contacts to redirect e-mail to a remote e-mail systemExchange can share a common SMTP address space with different e-mail systems by using contacts and SMTP connectors to determine the path for the e-mail messages. The domain part of the targetAddress attribute of a contact determines the destination e-mail system. The e-mail addresses that are displayed on the E-mail Addresses tab of the contact determines which e-mail addresses will resolve to the contact. From this information, Exchange can route the e-mail message to the correct targetAddress. The targetAddress corresponds to the e-mail address on the General tab of the contact. Also, the targetAddress is used as the primary SMTP address of the contact. The primary SMTP address is denoted by the "SMTP" acronym that appears in uppercase bold characters before the particular SMTP e-mail address.When an Exchange system receives an SMTP e-mail message, Exchange queries Active Directory to try to resolve the e-mail address that is listed in the recipient field of the message to the e-mail address of an object in Active Directory. If a match is found, Exchange routes the message to the e-mail address that is specified in the targetAddress attribute of the object. For the purposes of this article, this e-mail address is the e-mail address that is present in a remote e-mail system that has a unique SMTP domain. This routing feature lets Exchange act as a mail switch for any number of SMTP domains that are hosted by different e-mail systems. The contact has a primary SMTP address that corresponds to the remote messaging system and the contact has a secondary SMTP address that corresponds to the SMTP domain of the Exchange system. You use SMTP connectors that are configured to use address spaces that are specific to the remote e-mail system's domain to route e-mail to the remote e-mail systems. User accounts in the remote e-mail system must have a primary SMTP e-mail address that corresponds to the shared SMTP address space and a secondary SMTP e-mail address that corresponds to the primary SMTP e-mail address, also known as the targetAddress, of the contact in Active Directory. In this scenario, the following e-mail exchange occurs:
Step1: Configure recipient policies for use with contactsExchange accepts e-mail messages for any SMTP address space that is configured in a recipient policy. To add a remote SMTP domain to a recipient policy, follow these steps.Note This recipient policy uses a NULL filter rule. This rule is acceptable because you use the correct targetAddress value when you add the contacts to Active Directory. A NULL filter rule also prevents the Recipient Update Service from stamping Exchange objects with the SMTP address space of the remote e-mail system.
Step 2: Add contacts to Active Directory to represent remote usersYou can add contacts to Active Directory by using one or more of the following methods:
You can use the Csvde.exe tool to easily add many contacts to Active Directory. The Csvde.exe tool uses a comma-separated file format that uses the first line as a header. This header contains a comma-separated list of Active Directory attributes. The following example header file illustrates the minimum attribute set that is required to create a mail-enabled contact: objectClass,dn,name,cn,sn,givenName,displayName,proxyAddresses,targetAddress,mail,mailnickname Each set of comma-separated values for the header must be on a
single line in the Csvde.exe import file. And, each set of comma-separated
values for each contact must be on a single line in the Csvde.exe import
file.Important The mailnickname attribute is important. Without the mailnickname attribute, the E-mail Addresses tab is not displayed in the UserName Properties dialog box of the user in Active Directory Users and Computers. The following example demonstrates the use of the header together with example values for a SMTP contact: objectClass,dn,name,cn,sn,givenName,displayName,proxyAddresses,targetAddress,mail,mailnickname contact,"cn=Internet User,ou=internet users,dc=xo,dc=one",Internet User,Internet User,User,Internet,Internet User,SMTP:internetUser@remote.domain; smtp:internetuser@xo.one,SMTP:internetUser@remote.domain,internetUser@remote.domain,internetuser Note The DN attribute of the contact determines the organizational unit to which the contact is added. csvde –I –f importFileName.csv Step 3: Modify the SMTP virtual server properties to remove message forwarding for unresolved recipientsTo do this, follow these steps:
Step 4: Create an SMTP connector to route e-mail to the remote e-mail systemTo create an SMTP connector to route e-mail messages to a remote e-mail system, follow these steps:
Step 5: Restart the Routing and SMTP servicesTo do this, follow these steps:
PropertiesArticle ID: 321721 - Last Review: December 3, 2007 - Revision: 7.3 APPLIES TO
|
|
