Re: Exchange Name
- From: "Frank McCallister SBS MVP" <anonymous>
- Date: Mon, 19 Sep 2005 22:26:11 -0500
Hi Jerry
This behavior occurs when Exchange is configured
to be responsible for the e-mail domain that the external POP3 mail server
is hosting. When Exchange is responsible for an e-mail domain, it always
tries to deliver mail that is addressed to that domain to a local
recipient. If a local recipient with that e-mail address does not exist,
Exchange generates the NDR message 5.1.1.
To work around this behavior, use either of the following methods.
Method 1
Configure the SMTP virtual server in Exchange to send mail with unresolved
recipients to the Internet service provider's (ISP's) mail server. To do
this, follow these steps:
1. Click Start, point to Programs or to All Programs, point to Microsoft
Exchange, and then click System Manager.
2. Expand Servers, expand Servername, expand Protocols, and then expand
SMTP.
Note If Exchange System Manager is configured to display the administrative
groups, you must expand Administrative Groups before you expand Servers.
Then expand the administrative group that contains the mail server.
3. Right-click the SMTP virtual server, and then click Properties.
4. Click the Messages tab, type the name or the IP address of the ISP's
mail server under Forward all mail with unresolved recipients to host, and
then click OK.
The SMTP mail server that you specify must be the ISP mail server that
receives messages for the POP3 accounts. This may be different from the
POP3 server that you connect to when you download messages from the ISP.
5. Right-click the SMTP virtual server, and then click Stop.
6. Right-click the SMTP virtual server, and then click Start.
Note In this case, any e-mail that local users send to recipients that do
not exist on your server will be forwarded to the ISP's mail server.
Method 2
Configure the Default Policy in the Exchange recipient policy to use the
local e-mail domain as the primary address, and then add an additional
recipient policy to apply the POP3 e-mail domain to the local user
accounts. This way, the e-mail domain for the local users will match the
e-mail domain that the POP3 mail server is hosting, but Exchange will not
be the responsible mail server for this e-mail domain.
Be aware that the user accounts must be configured to be updated by
recipient policies. This option is available under the properties for each
user on the Email-Addresses tab.
To configure the recipient policies in Exchange, follow these steps:
1. Click Start, point to Programs or to All Programs, point to Microsoft
Exchange, and then click System Manager.
2. Expand Recipients, and then click Recipient Policies in the left pane.
In the right pane, the Default Policy is listed.
3. Double-click Default Policy, and then click the E-Mail Addresses tab.
4. By default, an SMTP e-mail address that matches your internal domain
name appears in the list of addresses. For example, if your internal domain
name is mycompany.local, the address @mycompany.local will appear in the
list. If the internal domain address is not listed, follow these steps to
add it:
a. Click New.
b. Click to select SMTP Address, and then click OK.
c. In the Address box, type the internal domain address, and then click
OK. For example, type @mycompany.local.
5. Click to select the internal domain address, and then click Set as
Primary.
6. Click to select the POP3 domain address, and then click Edit.
7. Clear the box that says This Exchange Organization is responsible for
all mail delivery to this address, and then click OK.
8. Click OK to apply the changes.
9. Click Yes or OK two times to update all corresponding recipient e-mail
addresses.
10. Right-click Recipient Policies in the left pane, point to New, and
then click Recipient Policy.
Note If you have Exchange Server 2000 Service Pack 1 (SP1) or later, a
dialog box appears that prompts you to select the type of recipient policy
that you want to create. In this case, click to select the E-Mail Addresses
check box, and then click OK.
11. Type a name for the recipient policy, and then click Modify.
12. In the Find Exchange Recipients dialog box, click to select Users with
Exchange mailbox, and clear all the other check boxes.
13. Click OK, and then click OK on the warning message that you receive.
14. Click the E-Mail Addresses tab.
15. Click to select the POP3 domain address, and then click Set as
Primary.
16. Click OK to apply the changes.
17. Click Yes or OK two times to update all corresponding recipient e-mail
addresses.
Note Every time that you run the Internet Connection Wizard or the
Configure E-mail and Internet Connection Wizard and set it to modify the
Exchange settings, the wizard will set the e-mail domain address that you
enter in the wizard as the primary address on each recipient policy. After
the wizard is completed, you must repeat the steps that are mentioned in
this article to modify the recipient policy.
To get additional detailed information, you may refer to the RESOLUTION of
the following KB article:
300681 E-mail to external recipients with the same e-mail domain causes NDR
http://support.microsoft.com/?id=300681
--
Frank McCallister SBS MVP
COMPUMAC
"Jerry Patterson" <Jerry Patterson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:9BA51253-3846-48AB-B60A-248C416CBC15@xxxxxxxxxxxxxxxx
> I've set up a new SBS 2003 with a clean install. This machine has no data
> to
> be concerned with loss at this time. My question is I named the exchange
> local server the same as my domain name. abc.local and abc.com for
> example.
> We will be using exchange for local interoffice email and SMTP outside to
> an
> hosted email sever. Everything works fine for now except when I email to
> someone through SMTP with the same domain name it tries to send it to
> local
> exchange which doesn't have a user for that name and returns a user not
> found
> message. I did find an option to tell exchange to use SMTP when name not
> found on local exchange. This fix is ok for now but will I run into any
> other problems? By the way we will be using POP3 connector.
> I am debating on just starting over from scratch because this is a clean
> install and haven't moved any data over yet from a peer to peer system.
> Thanks in advance.
>
.
- Prev by Date: RE: Cannot change password through OWA...
- Next by Date: RE: MrxSmb
- Previous by thread: Re: Exchange Name
- Next by thread: RE: DNS Server needs restart
- Index(es):
Relevant Pages
|
Loading
