[ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- From: William Holmes <wtholmes@xxxxxxxxxxxxxx>
- To: <exchangelist@xxxxxxxxxxxxx>
- Date: Thu, 6 Mar 2008 07:25:30 -0500
|
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 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
---- 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
From:
exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Patrick 1: The SMTP Server in Domain B is reporting the NDR's 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
---- 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
From:
exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Patrick 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
---- 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
From:
exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Patrick 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
---- do u have
reverse DNS configure,some mail server will not accept pls have regards ----- Original Message
---- 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
---- check the firewall for smtp 25 port ,guess is block some where .. try
and run SMTPdiag. cheers
----- Original Message
---- Can you try whitelisting this domains IP
to isolate the issue? James Chong Sr. Systems Engineer Simplexity, LLC. O (703) 657-4612 C (703) 863-1483 From:
exchangelist-bounce@xxxxxxxxxxxxx [exchangelist-bounce@xxxxxxxxxxxxx] On Behalf
Of James Chong 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. O (703) 657-4612 C (703) 863-1483 From:
exchangelist-bounce@xxxxxxxxxxxxx [exchangelist-bounce@xxxxxxxxxxxxx] On Behalf
Of Patrick [london31uk@xxxxxxxxx] 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
---- 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
For complete setup information, refer to the
Readme.asp file available in this folder.
----- Original Message
---- 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. 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. 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. | ||||||||||||||||
- References:
Other related posts:
- » [ExchangeList] NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified
- » [ExchangeList] Re: NDR 4.4.7 Could not deliver the message in the time limit specified