RE: POP3 connector accounts and DNS

Hello Roman,

Thank you for posting in the SBS newsgroup.

According to your description, I understand that the E-mail to external
recipients with the same e-mail domain causes NDR. If I have misunderstood
your concern, please don't hesitate to let me know.

Based on my experience, 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.

WORKAROUND
==========
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" (without the quotation marks).

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

I am appreciated your time and cooperation. If anything is unclear, please
feel free to let me know. I am looking forward to hearing from you.

Best regards,

Nathan Liu (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>Thread-Topic: POP3 connector accounts and DNS
>thread-index: AcWiwiQsbTNEakKWRruync6w+Brf2A==
>X-WBNR-Posting-Host: 4.23.20.31
>From: "=?Utf-8?B?cmJvam9ycUB0bWMtYWN0LmNvbQ==?="
<rbojorqtmcactcom@xxxxxxxxxxxxxxxxxxxxxxxxx>
>Subject: POP3 connector accounts and DNS
>Date: Tue, 16 Aug 2005 17:25:16 -0700
>Lines: 12
>Message-ID: <5F53894B-32E5-416B-A74B-2D12931EE874@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:145033
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>We are running SBS2003 with exchange setup using the POP3 Connector to pop

>mail down from our ISP. I have users in another state on the same ISP Mail
>server. Now that I've setup my users on my SBS server they cannot send
email
>to the users on my ISP mail server. Both are on the same domain name. one
>user is on our sbs server and the other is not. I get and "undeliverable
>recipeint does not exist" error.
>
>How can I setup my server to pop the mail for my users here while still
>being able to send to other users on the same dominname outside our office?
>
>
>Roman
>

.

Relevant Pages

  • RE: POP3 connector accounts and DNS
    ... >> recipients with the same e-mail domain causes NDR. ... When Exchange is responsible for an e-mail domain, ... If a local recipient with that e-mail address does not ... >> recipients to the Internet service provider's mail server. ...
    (microsoft.public.windows.server.sbs)
  • RE: problem using pop3 in different organizations
    ... When Exchange is responsible for an e-mail domain, ... If a local recipient with that e-mail address does not exist, ... >> Then expand the administrative group that contains the mail server. ...
    (microsoft.public.windows.server.sbs)
  • RE: problem using pop3 in different organizations
    ... When Exchange is responsible for an e-mail domain, ... If a local recipient with that e-mail address does not exist, ... > recipients to the Internet service provider's mail server. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS SP1 With Exchange 2003
    ... Microsoft CSS Online Newsgroup Support ... When Exchange is responsible for an e-mail domain, ... If a local recipient with that e-mail address does not exist, ... >> Then expand the administrative group that contains the mail server. ...
    (microsoft.public.windows.server.sbs)
  • RE: POP3 connector accounts and DNS
    ... > recipients with the same e-mail domain causes NDR. ... When Exchange is responsible for an e-mail domain, ... If a local recipient with that e-mail address does not exist, ... > recipients to the Internet service provider's mail server. ...
    (microsoft.public.windows.server.sbs)