RE: NDR in SBS 2003 Standard using Exchange

Tech-Archive recommends: Fix windows errors by optimizing your registry


Hi Dave,

Thanks you for posting in SBS newsgroup.

>From your description, I understand you have two mail accounts in one
profile and you cannot send internet E-mail. If I have misunderstood your
concern, please let me know. Based on my research, when you have two mail
accounts in one profile, the outlook 2003 will always use the default
account to deliver emails. If you configured the POP3 account as the
default email account, it will be always used even though you send emails
to your local users. Since the remote POP3 server cannot recognize your
local accounts (user@xxxxxxxxxxxx), it will generate Non-delivery reports
to you.

According to my experience, I would provide the following steps for your
reference:

1. Enabled your Exchange to send internet email. As following:

1) Open the Server Management console. Go to Standard Management\To Do List.
2) Click the "Connect to the Internet" link.
3) Click Next. Go through the wizard (you can choose "Do not change this
setting") until the "Internet E-mail" page.
4) Choose "Enable Internet e-mail" and click Next.
5) Choose to use DNS for email if you have a broadband connection and your
ISP does not block SMTP port 25. You can also forward emails to your ISP's
email servers if they require you to do so. Click Next.
6) Choose the correct method to receive emails (SMTP or POP3 Connector).
Click Next.
7) On the "E-mail Domain Name" page, type your public Internet email domain
name (we can use the local domain name, for example, yourdomain.local as
the e-mail domain name if you do not have a public domain name). This is
very important here. Click Next.
8) Go through the remaining steps.

2. You may also use the local account for internal mail traffic and the
external email addresses when emailing with the external recipients. You
may let the ISP add a MX record for you to point to SBS and then create 2
recipient policy in Exchange and set the .local as the primary. For
detailed information, please refer to the following KB article:

How to Configure Exchange to Forward Messages to a Foreign Messaging System
That Shares the Same SMTP Domain Name Space
http://support.microsoft.com/default.aspx?scid=kb;en-us;319759

If the issue still exists, please check the following settings:

1. Are you sending external e-mail through a smart host or DNS resolution?

1) On Exchange 2003 server, open Exchange System Manager.
2) Expand Servers -> <servername> -> Protocols -> SMTP.
3) Right click on Default SMTP virtual server, and click properties.
4) On the Delivery tab, click Advanced button.
5) Does he specify a smart host in Smart Host field?
6) If the Smart Host field is blank, click Configure button. Does he
specify any external DNS servers?

2. Have you defined any SMTP connectors to external domains?

1) On Exchange 2003 server, open Exchange System Manager.
2) Expand Connectors. Does he see SMTP connectors in the right pane?

3. Are you using DNS resolution to send external, use nslookup utility to
verify if the message is sent to the correct server?

1) On the Exchange server 2003, open the command prompt. Type
"nslookup" (without the quotation marks) and press ENTER.
2) If he is using an external DNS server, which is configured in the
SMTP virtual server. Type the following command at the prompt:

server external-dns-ip-address

3) Type the following command to find the MX record of the problematic
domain name.

ls -t MX domain-name.com

4) Type "exit" to quit.

Also, please check with the ISP hosting your DNS to see if a valid record
exists for the remote domain from the Internet. At the same time, I would
like to recommend you to bypass DNS name resolution to test Simple Mail
Transfer Protocol (SMTP) mail flow to the particular remote domain. For the
detailed information, see the following KB articles:

How to Bypass DNS Name Resolution to Test SMTP Mail Flow to Remote Domains
http://support.microsoft.com/?id=285863

4. Then let us use telnet utility to simulate the sending mail process.
Basically, we can use telnet command to identify the problem, if he you can
send the message via telnet command, the problem may be located in your
side, otherwise, this issue is most likely located at the remote server
side. To do it as following:

1) At the command prompt, type "telnet" (without the quotation marks),
and press ENTER.
2) At the Microsoft Telnet command prompt, type "set LOCAL_ECHO"
(without the quotation marks), and then press ENTER.
3) Type "open <server_name > 25" (without the quotation marks), and
then press ENTER.

NOTE: The server_name is the SMTP server's server name or IP address
you got in step 3, if you are using DNS to send mail. If you are using
a smart host, the server_name is the smart host''s server name or IP
address.

4) Begin communication by typing the following command:

HELO

5) Type the following command to tell the SMTP server whom the message
is from:

MAIL FROM:<username@xxxxxxxxxxxxxxxx>

NOTE: You should replace the sender's e-mail address with the your
e-mail address.

6) Type the following command to tell the SMTP server whom the message
is to.

RCPT TO:<recipient@xxxxxxxxxxxxxxx>

NOTE: You should replace the recipient's e-mail address with the one you
fail to send.

7) Type the following command to tell the SMTP server that you are
ready to send data:

DATA

8) Type the message body.

This is just a test mail!

9) Type a period at the next blank line, and then press the ENTER key
to indicate the end of the message.

10) Close the connection by typing the following command:

QUIT

For detailed steps, please refer to the following article for the
test:

XFOR: Telnet to Port 25 of IMC to Test IMC Communication
http://support.microsoft.com/?id=153119

The following KB article for your reference:

834866 You receive a non-delivery report when you try to send an e-mail
message to a recipient that is located in your Exchange organization in
Outlook 2003
http://support.microsoft.com/?id=834866

Thanks for your time and I look forward to hearing from you.

Best regards,

Crina Li (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: NDR in SBS 2003 Standard using Exchange
| t| From: "=?Utf-8?B?RGF2ZUI=?=" <DaveB@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: NDR in SBS 2003 Standard using Exchange
| Date: Wed, 11 May 2005 16:58:01 -0700
| | Newsgroups: microsoft.public.windows.server.sbs
||
| This seems to be a common problem but its hard to make sense of some of
the
| solutions. Please help......
|
| I have configured a server with exchange and Local workststion POP3
Accounts
| in Outlook. I can not send Internet email! I get error:
| Your message did not reach some or all of the intended recipients.
|
| Subject: test
| Sent: 5/11/2005 7:39 PM
|
| The following recipient(s) could not be reached:
|
| COMPUTER RESOURCE (dave@xxxxxxxxxx) on 5/11/2005 7:40 PM
| The e-mail address could not be found. Perhaps the recipient moved to a
| different e-mail organization, or there was a mistake in the address.
Check
| the address and try again.
| <elmserver.Elmstreet.local #5.1.8 smtp;553 5.1.8
| <Kathy@xxxxxxxxxxxxxxx>... Domain of sender address Kathy@xxxxxxxxxxxxxxx
| does not exist>
|
| I also get NDR when sending internal - But Intermittently.:
|
| Your message did not reach some or all of the intended recipients.
|
|
| Subject:
| Sent: 5/11/2005 3:00 PM
|
| The following recipient(s) could not be reached:
|
| dave@xxxxxxxxxx on 5/11/2005 3:00 PM
| The e-mail address could not be found. Perhaps the recipient
| moved to a different e-mail organization, or there was a mistake in the
| address. Check the address and try again.
| <elmserver.Elmstreet.local #5.1.8 smtp;553 5.1.8
| <Paula@xxxxxxxxxxxxxxx>... Domain of sender address Paula@xxxxxxxxxxxxxxx
| does not exist>
|
| I Believe it is a DNS error but it is hard to make sense of.......Please
| help me......
|
|

.

Quantcast