NDR sent 2 weeks after being sent

Is there a way of finding out why it has taken 2 weeks before a non deliery report has been sent.  Is there a setting which has caused this or is there some way I can find out more information as to why this has happened so that we can prevent this from happening again
LVL 1
mbavisiAsked:
Who is Participating?
 
SembeeConnect With a Mentor Commented:
Nothing you can do about it then.
Once the message has left your server it is out of your control.
The message has probably got stuck on a server somewhere and was only released when the server was restarted. If the recipient is using a major ISP as their mail host (as opposed to their own server) then it is even more likely to be the case.
The NDR might show the server name that bounced the message, but it depends very much on the type of NDR and the server that was rejecting it.

Simon.
0
 
redseatechnologiesCommented:
Exchange version?

And more importantly, do you have anti-virus or anti-spam on the server?
0
 
mbavisiAuthor Commented:
Exchange 2003.  We use trend micro and we also use advascan
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
SembeeCommented:
Internal or external message? Incoming or outbound?
If it was a message to an external email address then it is probably a problem that is out of your control.

Simon.
0
 
mbavisiAuthor Commented:
External message.  There must be something which has caused such a large delay.  Is there anyway of finding out why it has taken so long?
0
 
SembeeCommented:
External message going which way? Coming in to you or going out?

Simon.
0
 
mbavisiAuthor Commented:
Going out
0
 
mbavisiAuthor Commented:
Ive checked the message history and it appears as follows

SMTP Started Message Submission to Advanced Queue
SMTP Message Submitted to Categorizer
SMTP Message Categorized and Queued for Routing
SMTP Started Outbound Transfer of Message
Message transfered to **************************

2 weeks later

SMTP: Message submitted to advanced queuing
SMTP: Sterted message submission to advanced queue
SMTP: Message submitted to Categorizer
SMTP: Message categorised and queued for routing
SMTP Message Routed and Queued for Remote delivery
SMTP Non-Delivered Report (NDR) Generated

This implies that the email has left our server and was stuck in a queue at the receipient end does it not?
0
 
SembeeCommented:
That would appear as if the message was sent out and the NDR'ed later. Exchange detected it was one of its messages and was able to track it.

Simon.
0
 
mbavisiAuthor Commented:
So what is the likely occurance of this event?  Do you suspect that it is a fault with the end users server?  This has happened to another user who had sent something to another email account.

I would just like to rule out the possibility that there nothing further I could do to prevent such an event happening.
0
 
SembeeCommented:
A server somewhere isn't playing by the rules. An NDR should be sent back within 48 hours, or time out. To get one back two weeks later is very unusual. If the message has left your server, then it will be a remote server that is at fault. Very little you can do about it if that is the case. You have no control over the delivery of the email once it has left your server.

Simon.
0
 
mbavisiAuthor Commented:
Is there a way to change the NDR response time?
0
 
mbavisiAuthor Commented:
I just need to know if the NDR response time can be changed and then I will close this ticket
0
 
SembeeCommented:
The NDR in this case is not in your control. You cannot do anything about it. An Exchange server would NDR after 48 hours.

Simon.
0
All Courses

From novice to tech pro — start learning today.