Exchange 2003 NDR held until server restart, most related to 451 4.7.1 Greylisting.

Exchange Server 2003 SP2 on Windows 2003 Server SP1 releases old NDRs when physically restarted.  Most NDRs are 451 4.7.1 Greylisting related.  Subject emails are variously dated, some multiple months previous, and the NDRs have not been reported as released during intervening server boots, but all NDR's that are reported happen during a server boot.  Main general question is whether NDRs pool somewhere that is emptied on restart and, if so, why do some ride through several restarts before appearing?  Thanks.
Who is Participating?
This a bug, known as the greylisting bug. The messages are held in a retry queue that is hidden.

Copy the following to notepad and save it as a .reg file and apply it. Then restart the SMTP Server Service.

Windows Registry Editor Version 5.00



If your question has been answered, please remember to accept the answer and close the question.
kkettnerAuthor Commented:
The suggested solution of a regedit on the Exchange 2003 SP2 with Windows 2003 SP1 server


did not solve the problem in my case and NDRs remained in queue until SMTP Service restart.

Microsoft Hot Fix KB934709 relating to the aqueue.dll has seemed to fix the problem.
Another work around is to restart the SMTP service each night using a .BAT file and the task scheduler.

1.  Create a .txt file and rename it SmtpSvcRestart.bat.
2.  Cut and paste this text into the .BAT file:

net stop smtpsvc
netstart smtpsvc

3.  Schedule this .BAT file to run each night usng the Task Scheduler.

Restarting the SMTP service forces the server to "find" the lost messages and retry the send.
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

kkettnerAuthor Commented:
The KB934709 hotfix provided by Microsoft has worked along with a PTR update from my ISP for my email server addresses.  The restart/resend routine -- even if automated -- doesn't seem to address the underlying problem and adds a layer of administrative intervention.  I'm curious why the hot fix isn't a good choice for you.  Happy New Year!
MS acknoledge the problem, and now provides the bug fix.

Here it is:

E-mail senders do not receive an indication that some messages have been
held by Exchange Server 2003 until the SMTP service, the Microsoft Exchange
Information Store service, or the Exchange server is restarted
as always Experts Exchange is the font of all knowledge TY again
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.