Has anyone found an acceptable reason for this? Running Exchange on SBS2003 w/ Exchange SP2.I have a reverse PTR that my ISP created. I created a SPF record with my domain hosting account, and still I get these time outs from primarly users at army.milCould not deliver the message in the time limit specified. Please retry or contact your administrator.<domain-name.com #4.4.7>Any suggestions will be greatly appreciated

Are you sending to users @army.mil? Or @us.army.mil? Can those users sendYOU e-mail? It is possible that they are not acknowledging your DNS, who hosts it? I have seen issues where the Army's DNS servers ignore anything registered via dyndns.com and its other domains.

Hi Jim,Thanks for the response. Yes it's us.army.mil Yes my users are able to receive emails from us.army.milOur DNS is hosted at eNom. Our ISP (Surewest) recently upgraded from T-1 to Fiber over Ethernet and there have been issue with our new IP address range being seen as a dynamic range. They had to aggressively pursue delisting from SORBS, MailAbuse, etc... (No one bothered to check the IP range prior to issuing them to us, bad business call)At my request they've implemented a PTR record. I've created a SPF record with eNom.We have not received that many NDR's since the creation of both of these records. It's just this annoying time 4.4.7 from the us.army.milI was hoping for a setting in Exchange to allow to extend a request or time limit... but Alas... I'm sure the problem is extending far beyond the reaches of the realm of my control. Can't switch ISP because they're the only game in my neck of the woods. Maybe change were my DNS records hosted... but that may be a far stretch...Let me know. Thanks once again.Laurence

This is a fix or an area to look at when you get the 'email could not deliver in time specied' when it involves multiple domains....ie cannot email hotmail.com, verizon.com, cbeyond.net etc. Emails can still be sent from the domains and recieved locally at your domain.we had an issue where all of the sudden we could not email multiple domains, we would get 'could not deliver in time specified'.The ISP had us change our FQDN on our 2003 exchange server from a .local to a .com. It fixed the problem for a week.then the problems started up again, could not email hotmail.com, verizon.net etc.What fixed our problem was correcting an incorrect Secondary I.P. setting located on our DNS server. SPECIFICALLY located at Start/administrative tools/DNS then select the FORWARDERS tab.Forwarders are servers that can resolve DNS queries not answerd by your local server. These would be a primary and secondary I.P. addresses that your ISP provider would give you.While this does not address why the primary was failing to vailidate PTR (DNS queries) records from recieving SMTP servers, for the time being it has fixed our emails. (and the emails delivered immediately after hitting APPLY).I am not an I.T. person, but I was able to get our email working when our Microsoft Certified Support people could not (at least not in 3 visits and over 8 hours at $155 bucks an hour)Again, I still think there is an underlying issue with our Primary DNS, but I am working with our ISP to verify that everyting is as it should be, because the secondary I.P DNS should only be used when the Primary is not available. I dont think that the remote domain requesting a DNS validation require both the primary and the secondary be available or else we would never have been able to send emails to those domains.