How to Configure the Necessary SMTP E-mail Addresses for Your Users

Use the following procedure to ensure that each user's e-mail address is correctly configured on a recipient policy. Remember that Microsoft® Exchange Server only accepts mail for addresses that are configured correctly in a recipient policy. These addresses are stored in Microsoft Active Directory® directory service and the IIS metabase where the message categorizer checks for address and configuration information.

Before You Begin

Before you perform the procedure in this topic, read Connecting Exchange to the Internet.

The following permissions are required to perform this procedure:

• Member of the local administrators group and a member of a group that has had the Exchange Administrators role applied at the organizational group level

Procedure

To configure the necessary SMTP e-mail addresses for your users

1. In Exchange System Manager, in the console tree, expand Recipients, and then click Recipient Policies.

2. In the details pane, right-click the recipient policy that you want to modify, and then click Properties.

3. On the E-Mail Addresses (Policy) tab, click New.

4. In New E-mail Address, click SMTP Address, and then click OK.

In SMTP Address Properties, in the Address box, type the information required by the address type you selected. For example, to route mail to Example Corporation, type @example.com as shown in the following figure.

The SMTP Address Properties dialog box

1. Ensure that the This Exchange Organization is responsible for all mail delivery to this address check box is selected, and then click OK.

   Note

   The This Exchange Organization is responsible for all mail delivery to this address check box determines whether or not Exchange is authoritative over the selected domain. If Exchange is authoritative for a domain, it accepts all mail for the domain; if it does not locate a valid recipient in Active Directory, Exchange returns an NDR for the message.

2. To keep track of information about the recipient policy you modified, in the recipient policy properties, click the Details tab. Under Administrative note, type information about the address that you added to the recipient policy.

3. On the E-Mail Addresses (Policy) tab, under Generation rules, select the address you added, and then click Apply.

   Important

   When you click Apply, Exchange may prompt you to update all corresponding recipient e-mail addresses to match the changes you made. If you click Yes, the changes that are made to the recipient policy are applied to the recipients that are defined for the policy on the next cycle of Recipient Update Service. E-mail addresses that were previously configured for these recipients are demoted to secondary addresses.

   If you want this e-mail address to apply only to a subset of users, create a new recipient policy with a filter that selects the subset of recipients you specify. If the filter is too complex or only a small number of users require the additional address, you can design a filter that creates e-mail addresses that apply only to individual recipients.

   Warning

   All SMTP mail domains for which Exchange Server accepts mail should have a recipient policy configured for them; however, that recipient policy need not apply to every user. You can add new SMTP e-mail addresses, but it is imperative that the SMTP e-mail addresses do not match the FQDN of any Exchange server in your organization. If an SMTP e-mail address matches a server's FQDN, remote and local e-mail will stop flowing.

For More Information

For more information about how to configure recipient policies, see Microsoft Knowledge Base article 260973, "XCON: Setting Up SMTP Domains for Inbound and Relay E-Mail in Exchange 2000 Server and Exchange Server 2003." Although this article is written for Exchange 2000, the same principles apply to Exchange 2003.

For more information about how to correct problems with SMTP proxy addresses, see Microsoft Knowledge Base article 140933, "XFOR: SMTP Proxy Address Generated Incorrectly." Although this article is written for Exchange 2000, the same principles apply to Exchange 2003.