Outlook 2003 not getting NDR

Hi Guys,

This is my first question in here. Please help. One of my user is not getting NDR form an External wrong email address. I test that email address from a different account and getting NDR says incorrect email address. So the remote server is sending NDR and my server is getting that. It is happening last 4-5 weeks. Affected user is not getting any NDN. I checked the user outlook settings no rule is configured.

Outlook 2003
Exchange 2003.

Any help will be much appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

have you checked the exchange tracking logs to see what happens to the sent message or if an NDR was sent through your system?

we need to know what your server says in the logs when it tries to send this message.
sicorpmelAuthor Commented:
Sorry for the delay. Was sick actually. But here is the details:

User msg goes from server A - brigdehead - mailfilter - internet. Tracking log says deliverd from server to BH - mailfilter. Mailfilter log says failure.

Test using different account with

server B - BH - Mailfilter - internet. Only the mail server is different rest BH-Mailfilter-internet same path for both the server. Traking log says same thing and this user getting NDR incorrect email address.

One more thing it is happening with 2 more users in Server A.

Please let me know if you need more info.

Dont really have enough info for specfic details. The error shown in the tracking log or a log of the NDR would be helpful to show which server created the NDR.

if this happens to specific users only, get them to type the full address in and DO NOT LET THEM USE THE ONE STORED IN THE CACHE. stand over them to make sure if necessary. If the address in the cache is wrong then it will fail.

If this happens to everyone, you need to trace the message and see at which point it is being turned down.
once you know which server has the issue you can check the logs and post them here for us to see where the issue may be.
sicorpmelAuthor Commented:
Hi Guys,

A service restart fix the problem. Thanks for all the Help.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sicorpmelAuthor Commented:
Do not know what was the cause. Service restart fix that. As this is a single instance so not investigating further
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.