Delivery status notification delay errors when sending mail.

Posted on 2004-09-07
Last Modified: 2013-11-15
We are running Exchange 2003 in an AD environment. When our users send mail it works well except to the following specific addresses i.e and we get an NDRs with the following message body ,
This is an automatically generated Delivery Status Notification.

Your message has been successfully relayed to the following recipients, but the requested delivery status notifications may not be generated by the destination.    

This is an automatically generated Delivery Status Notification.



Delivery to the following recipients has been delayed.

But when these people send mail back to our server, We do receive the emails.  The deliver status notification on our server is set to 12 hours. Please help as am desperate.


Question by:Mfana
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +2
LVL 12

Expert Comment

ID: 11996051

The DNS states the "Your message has been successfully relayed to the following recipients" ... this is not a failure notification ...  your last sentence states you receive emails from them ... so I'm not sure what the problem is? Did you mean that when they send .. you don't receive emails? Can you receive emails from other domains?

Are the users receiving NDR failure notifications if so?

Please provide more info ...
LVL 20

Expert Comment

ID: 11996401
"but the requested delivery status notifications may not be generated by the destination." - the mail has been relayed to the destination server but the delivery status notification which was requested from your end has not been acknoledged by the destination server. They might have disable delivery reports notification from thier end.

"Delivery to the following recipients has been delayed" - The delivery to the destination server has been delayed. there are many reasons for this
1.poor internet bandwidth
2.connection timed out
3.large message size.

Create an SMTP connector to the destination domain forward the mail to your ISP smart host to resolve the issue.

Hope this helps you!
LVL 20

Accepted Solution

ikm7176 earned 100 total points
ID: 11996411
Create an SMTP connector to the destination domain  or forward the mail to your ISP smart host to resolve the issue.
Problems using Powershell and Active Directory?

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


Author Comment

ID: 11996822
Taking my explanation further :
When we send to other domains, we do not get the error or NDR. And when users from these domains( and sends us mail it comes through fine. The problem is encountered only when we send mail to them and they do not receive from our domain but as I said they can send to our domain.

I hope this clarifies.

Expert Comment

ID: 13566199

How did you end of fixing this?  I am having the same problem.

Expert Comment

ID: 14397718
We are having the exact same problem as well.  I've checked with technet, done tons of goolge searches and varified settings all over the place.  Still have'nt come up with an answer.  Is this an exchange 2003 bug?  Does anyone know?

Expert Comment

ID: 14402237
we ended up reloading exchange over the top of itself and it cleaned itself up.

Expert Comment

ID: 14465849
Thanks for the reply!  I'll give that a shot.  Is it the SMTP sink that may have got corrupt and the reinstall repaired it.  I think our problem started when we added a third party disclaimer software on the server.  That's when emails would appear to be delivered but the clients would not recieve the message.  The fix to this situation we removed the disclaimer software components.  Everything seems to work but there are still certain domains we cannot send to.

Is reinstalling exchange 2003 over itself a safe and clean thing?  Will it incorporate all the settings?



Expert Comment

ID: 14465903
Yes it is clean.  No problems.  We kept all the settings.

Featured Post

MIM Survival Guide for Service Desk Managers

Major incidents can send mastered service desk processes into disorder. Systems and tools produce the data needed to resolve these incidents, but your challenge is getting that information to the right people fast. Check out the Survival Guide and begin bringing order to chaos.

Question has a verified solution.

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

Lotus Notes – formerly IBM Notes – is an email client application, while IBM Domino (earlier Lotus Domino) is an email server. The client possesses a set of features that are even more advanced as compared to that of Outlook. Likewise, IBM Domino is…
MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
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
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

739 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