Exchange 2003 Delivery Status Notification (Failure)

We are using Server 2003 (SP1) & Exchange 2003 (SP2) utilizing POP to access our email host to download emails and distribute to the Exchange users who are using Outook 2000 to access their exchange mail boxes.
We were working without any problems until we switched email hosting services.
Once I changed the DNS Servers on my Registrars site to the new hosting service we began having random email receiving problems.

Delivery Status Notification (Failure)
This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed.

Notepad Details:
Reporting-MTA: dns;
Received-From-MTA: dns;
Arrival-Date: Tue, 26 May 2009 11:07:09 -0700

Final-Recipient: rfc822;
Action: failed
Status: 5.1.1

I have already tried to re-register the imbreg.exe without success. It doesn't appear to "execute".
I do receive an Event Error of 1071.

Again the Failed Delivery Notification started immediatley after  changing  email hosting services.
The hosting account is an "Email only" account.

Any advice or direction is appreciated.
Thank you,
John B
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.

Please check "Default SMTP Virtual Server"  > "Delivery" tab > Advanced > Configure
If there is DNS IP of old email hosting service provider is present, then remove it. The restart Microsoft Exchange routing engine service and SMTP services. Also run ipconfig /flushdns & ipconig /registerdns commands (if Exchange server is not a DNS server).
On the DNS server check the forwarders and restart the DNS service.

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
jbarettaAuthor Commented:
Thanks for responding shahsejal,
There is not a DNS address in the Delivery tab>Advanced>Configure contained in the SMTP Virtual Server.

Would it help to place the DNS of the new Email Hosting Service?

I did performed the actions you mentioned:
restarting Exchange routing & SMTP Services
Iponfig /flushdns    and  ipconfig /registerdns  commands
Since the mail servers were the same and did not change with the new host the above items seem like a good idea.

This Server is not a DNS Server.

I'm at the Server will be about 10-20 minutes before I know if the above items rectified the situation.

I'll let you know,
Thank you for your time,
John B
jbarettaAuthor Commented:
Unfortunatley this did not eliminate the problem.
Any other suggestions?
John B
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Then is there any 3rd party software installed? If possible try to uninstall it only to compare the results
We may also use Nslookup to check if the MX record is resolving to the correct IP address for the remote domains.
jbarettaAuthor Commented:
Thanks shahsejal,
I'm not sure what you mean by "3rd Party" mean another smtp/pop program?
There is another program that sends out emails using one of the user's email accounts to authenticate but that program was installed weeks before the delivery status notification problem begin occurring. It happend immediatley after switching hosts over the weekend.
I did perform a nslookup >type set=mx > and received the following:
non-authoritative answer:  MX preference = 5, mail exchanger =

I have set both the DNS IPs for mail.intlfarm in the "Default SMTP Virtual Server"  > "Delivery" tab > Advanced > Configure settings without resolution.
The problem is random and the Delivery reciept failure errors always occur with users in the cc fields.
Event id 1071 is present in the event viewer/ application log

jbarettaAuthor Commented:
Thanks shahsejal,
The work around of adding as an available email for each user is what I did to "work around" the issue.....obviously it's just a work around.
I have not found a "Solution" or a way to "solve the problem" as of yet.
Thank you for your time.
John B
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
Email Protocols

From novice to tech pro — start learning today.