Solved

Exchange 2003 NDR 5.1.1 on some domains

Posted on 2006-07-06
1
263 Views
Last Modified: 2008-02-01
Hi, I´m sorry for my english, but i hope you can understand.

I work a a small company, that has 3 servers, 2 DC (one windows 2000 and the other windows 2003) and one Mail server with Exchange 2003 (on top of windows 2003 R2).
We had only one domain registered, domainA.com, but then my boss wanted to have two domains domainA and domainB. We had to change the mail server, so we transfered the mailboxs to another server and configured it to receive from the two domains. We asked our ISP to create one mx record of the domainB equal to the older domainA.

Now we receive mail from the two domains (ex. usara receives mail from usara@domainA.com and usara@domainB.com), but only send from the new domain (domainB).

The problem is that after these changes in our network, we noticided that a few domains could receive our mails but could not send back (reply or new message), but could send to the older domainB.

The message that these domains receive is this:

usara@domainB.com on Mon, 26 Jun 2006 12:25:41 +0100
    The e-mail account does not exist at the organization this message was sent to.  Check the e-mail address, or contact the recipient directly to find out the correct address.
    <asp-ndr.asp-telepac.local #5.1.1>

Aparently this is a NDR not sent from our server, but from our ISP.

This only occurs in 3 or 4 from 100 domain that we receive and send mails...

I tried a few tips that i have found here, but in vain... i don´t have the skills to resolve this problem alone.

Please help me and again sorry for my lousy english.
0
Comment
Question by:x-flood
1 Comment
 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
ID: 17052538
That message means what it says - the server that the message was delivered to, doesn't recognise the email address.

The usual cause is either misconfigured DNS records, or stale DNS records.
As this is sending you email, your options are very limited - as the server doing the sending needs to carry out the diagnostics.

The sender need to do an nslookup on your MX records from their server to see if they are using old information.

Carry out an MX record lookup on the Exchange server.

For example... microsoft.com:

C:\>nslookup
Default Server:  server.domain.co.uk
Address:  192.168.1.1

> set type=mx
> microsoft.com
Server:  server.domain.co.uk
Address:  192.168.1.1

Non-authoritative answer:

microsoft.com   MX preference = 10, mail exchanger = mailc.microsoft.com
microsoft.com   MX preference = 10, mail exchanger = maila.microsoft.com
microsoft.com   MX preference = 10, mail exchanger = mailb.microsoft.com

maila.microsoft.com     internet address = 131.107.1.7
maila.microsoft.com     internet address = 131.107.1.6
mailb.microsoft.com     internet address = 131.107.3.123
mailb.microsoft.com     internet address = 205.248.102.77
mailc.microsoft.com     internet address = 205.248.102.78
mailc.microsoft.com     internet address = 205.248.102.79
>

Once they have the information, it needs to be compared with your public information. It should be identical.
If it isn't, then they are using stale information.
Flushing the DNS cache should fix the problem - again on their server.

As the recipient of the message there is very little you can do, particularly if it is a small number of senders who have the problem.

Simon.
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Utilizing an array to gracefully append to a list of EmailAddresses
We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

911 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

24 Experts available now in Live!

Get 1:1 Help Now