There are in different locations but we use same ISP, so we are in same ISP network to say. What happens is that When you attempt to telnet from Domain C to domain A, an ISp given IP address is then contacted which redirects the connectin to Domain A's Mail server. In the case of Domain C to A it works ok, and I can telnet successfully.
In the case of Domian B to Domain A, they can not get through, and that is were it times out trying.
Hope my explanation is clear
Thanks
Hi,
Start by running tracert to determine the network paths that are being taken. Start with B to A, then try C to A. Verify the routes that exist on all the servers with the route command. Verify that the routes are valid. How do the two domains connect to each other? Are they at different locations?
Bill
From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Patrick
Sent: Thursday, March 06, 2008 5:59 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
This is driving everyone crazy.
Scenario so far.
Domain B can not successfully carry our a Telnet session to Domain A. However domain C can Telnet to domain A.
Domain B does not have outbound mail filterting turned on, so that kinda rules out mail filtering issue.
We still think that this might be a routing issue with our ISP, but it is so difficult to get them to see so. Any pointers would be greatly appreciated.
----- Original Message ----
From: James Chong <jchong@xxxxxxxxxxxxxx>
To: "exchangelist@xxxxxxxxxxxxx" <exchangelist@xxxxxxxxxxxxx>
Sent: Friday, February 29, 2008 4:23:04 PM
Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
1. When you do the telnet from Domain B to A and send message does telnet say it was queued for delivery? Did you using Exchange message tracking?
2. If possible; have them disable GFI and test sending.
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 [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Patrick
Sent: Friday, February 29, 2008 11:09 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
1: The SMTP Server in Domain B is reporting the NDR's
2: Yes We can Telnet port 25 from the SMTP server in Domain B to the SMTP server in Domain A
3: Yes we currently have domain B's domain whitelisted on the Spamfilter server, no emails in Junk mail
4: GfIMailessential
5: Yes we have verified that MX records are setup fine
----- Original Message ----
From: James Chong <jchong@xxxxxxxxxxxxxx>
To: "exchangelist@xxxxxxxxxxxxx" <exchangelist@xxxxxxxxxxxxx>
Sent: Friday, February 29, 2008 3:35:10 PM
Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
Thanks! Can you verify the following?
1. What SMTP server is reporting the NDR to domain B users?
2. From Domain B you tried telnetting to port 25 to Domain A mail server? Did it go through if not; any errors? Did you try message tracking it?
3. Did you try whitelisting and also checking your junk mail?
4. What content SPAM filter is Domain B using now?
5. You verified that all your MX records are set up correctly?
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 [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Patrick
Sent: Friday, February 29, 2008 9:59 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
Hi James,
Sorry for the confusing scenario, it so happens that we own both domains, and I am trying to fix it for both. ok this is the story
Domain A can send emails to domain B, but domain be can not reply to emails sent from domain A or create and send new emails. however both domains can send to external domains including Hotmail, yahoo, and recieve emails ok.
There is not fixed connector between the sites, but we all use the same ISP. now the story is that Domain A stopped using our ISP for content and spam filtering and the story is that ever since that happened the problem came about
Hope my explaination is clear.
Thanks
----- Original Message ----
From: James Chong <jchong@xxxxxxxxxxxxxx>
To: "exchangelist@xxxxxxxxxxxxx" <exchangelist@xxxxxxxxxxxxx>
Sent: Friday, February 29, 2008 2:20:54 PM
Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
Can you go over the symptoms again? Getting confused J I thought it was a reply only issue below:
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.
Or is it that you cannot send to this particular external domain at all?
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 [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Patrick
Sent: Friday, February 29, 2008 6:12 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
I am not quite sure that is the case here, cos we can recieve from the other side, but can not send, and we can send and recieve from everyone else. The only pointer here is that we all share the same ISP. So we suspect they have done something they are not telling us.
This is the story. The other site chose to stop using our ISP for mial filtering as this was too expensive and chose to have it in house. Every since that service was disable, this problem started. I think they might have setup up some sort of static route between the 2 sites which isnt quite right. but that is only a guess, as they claim all is well @ thier end.
----- Original Message ----
From: Sola Alabi <solaalabi@xxxxxxxxx>
To: exchangelist@xxxxxxxxxxxxx
Sent: Friday, February 29, 2008 9:59:20 AM
Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
do u have reverse DNS configure,some mail server will not accept ur mail if u do not have that , like aol e.t.c
pls have ur ISP or if u have the admin right to do it .pls try this .
regards
----- Original Message ----
From: Patrick <london31uk@xxxxxxxxx>
To: exchangelist@xxxxxxxxxxxxx
Sent: Friday, 29 February, 2008 10:05:02 AM
Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
smtp port 25 is not blocked, cos we can send to other domains and receive. And according to the logs from ISA, an smtp connection is established
----- Original Message ----
From: Sola Alabi <solaalabi@xxxxxxxxx>
To: exchangelist@xxxxxxxxxxxxx
Sent: Friday, February 29, 2008 8:35:58 AM
Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
check the firewall for smtp 25 port ,guess is block some where .. try and run SMTPdiag.
cheers
----- Original Message ----
From: James Chong <jchong@xxxxxxxxxxxxxx>
To: "exchangelist@xxxxxxxxxxxxx" <exchangelist@xxxxxxxxxxxxx>
Sent: Thursday, 28 February, 2008 5:45:43 PM
Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
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
(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
For complete setup information, refer to the Readme.asp file available in this folder.
----- 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 )
|
Thanks and Regards | |||
|
| ||
|
|
| ||
From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Patrick
Sent: Tuesday, February 26, 2008 8:56 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
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 ----
From: "Kamuni, Prabhakar" <Prabhakar.Kamuni@xxxxxxxxxxxxx>
To: exchangelist@xxxxxxxxxxxxx
Sent: Tuesday, February 26, 2008 2:47:49 PM
Subject: [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
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
|
Thanks and Regards | |||
|
| ||
|
|
| ||
From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Patrick
Sent: Tuesday, February 26, 2008 7:51 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] NDR 4.4.7 Could not deliver the message in the time limit specified
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.
Yahoo! Answers - Get better answers from someone who knows. Try it now.
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
Sent from Yahoo! Mail.
A Smarter Inbox.
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.
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.
