<div>
From your description it sounds like these are outbound emails only, no internal issues. &nbsp;You mentioned seversl DNS servers. &nbsp;This isn't necessarily a good thing, 2 or 3 that or close to home with good records is the best route. &nbsp;In other words, unless you use a garage ISP you should use your ISP's DNS. &nbsp;It's the closest responder. &nbsp;Furthermore, ISP's sometimes limit DNS responses to clients that aren't on thier network.<br />
I assume this all worked at one time. &nbsp;What is your Internet connection? &nbsp;If it's something like DSL or Cable these are best effort connections that can often give intermittent problems for higher need services like email and VPN.
</div>


<div>
You should check the reason why messages aren't being delivered. If you click the queue that has problems you can see the reason in the bottom of your exchange management console under 'additional queue information'<br />
Could you also post the NDR report you get when the message failed to deliver?
</div>


<div>
Go through below article from Msexchange written by author Author: Marc Grote <br />
<br />
<a href="http://www.msexchange.org/tutorials/exchange-server-2003-mailflow-part-2.html" rel="ugc">http://www.msexchange.org/tutorials/exchange-server-2003-mailflow-part-2.html</a>
</div>


<div>
Another possible reason - has your IP/Domain been added to a SPAM blacklist?
</div>


<div>
Here is the typical NDR report:<br />
Action: delayed<br />
Status: 4.4.7<br />
<br />
Every queue says &quot;The connection was dropped by the remote host&quot;. &nbsp;It seems to be related to timeout issues. &nbsp;Any thoughts?<br />
<br />
I checked the SMTP log, and seeing this quite a bit:<br />
Timeout+waiting+for+client<wbr />+input<br />
Error:+timeout+exceeded<br />
<br />
<br />

</div>


<div>
Normally, error 4.4.7 indicates there's a problem on the receiving side. Can you try to mail through a smart host to see if it makes a difference?<br />

</div>


<div>
Still could be a SPAM rejection or poor Internet connection. &nbsp;Did you check the blacklists? &nbsp;Do you run a single ISP or load balance?
</div>


<div>
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
</div>


<div>
<div class="content wysiwyg-content">
Our Exchange 2003 is having major problems with outbound delivery delays. &nbsp;There are several messages in the queue in retry mode. &nbsp;Some messages are delivered without a problem, however a majority of messages end up in retry mode, and eventually fail. &nbsp;There is no smarthost being used. &nbsp;The SMTP Virtual Server is configured to use several external DNS servers for lookups. &nbsp;Any ideas?
</div>
</div>


Our Exchange 2003 is having major problems with outbound delivery delays.  There are several messages in the queue in retry mode.  Some messages are delivered without a problem, however a majority of messages end up in retry mode, and eventually fail.  There is no smarthost being used.  The SMTP Virtual Server is configured to use several external DNS servers for lookups.  Any ideas?

Exchangeg 2003 Queues in Retry

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.