Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NDRs with no specific reason given.

Status
Not open for further replies.

lbicher

MIS
Jun 13, 2002
41
US
I have an Exchange Org that has a 2K server and a 5.5
server. We are migrating from the 5.5 server. At times,
some of the users who reside on the 2K server will receive
the following NDR:

"The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.The MTS-ID of the original message is:c=US;a= ;p=Langan;l=EPMAIL-020611212947Z-608 MSEXCH:MSExchangeMTA:ELMWOOD_PARK:MAIL"

This has occurred with both outgoing SMTP mail as well as
mail mail sent to users that are still on the 5.5 server.
Also, it does not happen to everybody at the same time. If
anyone has any idea, I would be grateful. Thank you.
 
Hi...
Try getting the NDR via pop3 protocol or apply the latest patches to your 2k server (post SP2). This will, at least, send the error detail with the NDR.

I've had the same problem...



PS.: sorry the bad english
 
Thanks,
Do you know where I can get the post-SP2 rollup? MS's website says it is available if I call Product Support.
Also, you say you've had the same problem, did the patches clear it up?

 
About the post-SP2, serch for
- Exchange 2000 Admin Patch 5770.21 (Q316056)
- Exchange 2000 CDO Patch 5770.16 (Q314606)
- Exchange 2000 Unified Messaging Patch 5770.72 (Q319361)

Unfortunalety, the patches didn´t solved it...
 
Its a free call for hotfixes...

Try to track the message. Dan
Microsoft Exchange Support @ Microsoft
 
Thanks to all for your help. The problem is now resolved.

Tracking the message (thanks Dan) showed that the messages were when transferring over to the 5.5 server from 2000. I then looked at the Application Logs on the 5.5 server and discoverred entries that exactly matches examples in KB article Q288848. It has to do with virus scanning using VAPI. There is a post SP4 hotfix for Exchange 5.5 that addresses this specific issue. I applied the hotfix and have been running good ever since.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top