Can you try whitelisting this domains IP to isolate the issue?
James Chong
Sr. Systems Engineer
Simplexity, LLC.
11130 Sunrise Valley Drive, Suite 300
Reston, VA 20191
O (703) 657-4612
C (703) 863-1483
From: exchangelist-bounce@xxxxxxxxxxxxx [exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of James Chong Sent: Thursday, February 28, 2008 11:41 AM To: exchangelist@xxxxxxxxxxxxx Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified This domain cannot reply to your companys messages, but they can send a new message? I have heard of this before with the reply issue but don't recall a resolution. Let me research.
James Chong
Sr. Systems Engineer
Simplexity, LLC.
11130 Sunrise Valley Drive, Suite 300
Reston, VA 20191
O (703) 657-4612
C (703) 863-1483
From: exchangelist-bounce@xxxxxxxxxxxxx [exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Patrick [london31uk@xxxxxxxxx] Sent: Thursday, February 28, 2008 10:40 AM To: exchangelist@xxxxxxxxxxxxx Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified Hi Guys,
any input on this would be greatly appreciated. We can telnet the smtp relay box, but nothing seems to get through. everyone seems to think this is not thier problem. Somehow we feel it is the ISP's but they are not taking responsibility for this.
Any Ideas please ----- Original Message ----
From: Patrick <london31uk@xxxxxxxxx> To: exchangelist@xxxxxxxxxxxxx Sent: Thursday, February 28, 2008 12:00:42 PM Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified Hi,
Someone recommended we do the following. Not quite sure this does. Please advice
Turning off EDNS-0 extended UDP packets in W2k3 server's DNS.(EDNS0 as defined in RFC 2671) Server 2003's DNS server has a new capability, it can handle UDP packets greater than 512 bytes. Unfortunately some firewalls cannot pass these packets so it is desirable to have the DNS server fall back to TCP in this case as it used to do in previous versions of NT DNS. To turn off the EDNS-0 feature run this from a command prompt: dnscmd /Config /EnableEDnsProbes 0 Once you run this your W2K3 DNS server will never advertise its EDNS capabilities and so will never receive a UDP packet > 512 bytes. dnscmd.exe can be found in the Support Tools. To install Windows Support Tools
----- Original Message ----
From: "Kamuni, Prabhakar" <Prabhakar.Kamuni@xxxxxxxxxxxxx> To: exchangelist@xxxxxxxxxxxxx Sent: Tuesday, February 26, 2008 5:21:58 PM Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified If your able to receive and send mails through other domains…still you need to have a look at the below points.
Network connectivity issues you can check using trace route to the problematic domain.
Find out with remote domain administrator if your domain has block listed in there Database
Try telnet from your exchange server to Remote domain (C:\telenet problemdomain.com 25 )
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of
Patrick
Should this be done on mine server though? eveb though I can send and recevie from other domains and can send to the problematic domain, but can not receive
Thanks ----- Original Message ---- Hi,
Please have a look at the below, it can be any of the below issue.
1) Network connectivity issues 2) You might be blocked by Remote server 3) Try to telnet 25 to the remote server and see what the response you can see? 4) Do you use ISP Smart Host for delivering Emails or you got own SMTP server? 5) Finally Check the DNS. ( check FQDN is valid for SMTP Virtual server)
If the issue will not resolve please increase the Diagnosis logging for MSExchange Transport.
Cheers!!! Prabhu
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of
Patrick
Hi guys,
Not quite sure why this is happening. But we can send emails to people ok, but we are having problems from a particular domain. Other domains can send to us ok.
When we send a mail to the domain it arrives ok, but users can not reply to our message. They keep getting the 4.4.7 NDR with message delayed and then timeout.
If anyone can point us in the right direction it would be helpful, cos a lot of steam and trouble is brewing over this.
Windows 2003 Domain, Exchange 2003 SP2. Mail Marshall for filtering.
Thanks
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
Looking for last minute shopping deals? Find them fast with Yahoo! Search. Looking for last minute shopping deals? Find them fast with Yahoo! Search. Never miss a thing. Make Yahoo your homepage. |