Re: Undeliverable 4.4.7 - telnet test connects OK, but fails.

Hi Paul,

Thanks for following this up.

We still have this problem.

The receiving server's IT people have been very reluctant to help out. I had
one response to check the correct email address and retry, but nothing
further despite a few email reminders detailing the problem, with links to
MS KB to check for the known firewall issues.

Next step is for me to phone them I guess to see if I can get some answers.
:-)

Thanks again for following up, I'll repost if I have any more news.

Cheers,

Mark


"Paul Ford (Edge IT Ltd)" <paulford@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:u8L8yC0hHHA.4076@xxxxxxxxxxxxxxxxxxxxxxx
Mark,

Any joy on getting this resolved ?

Paul

"Mark" <nospam@xxxxxxxxxxxxx> wrote in message
news:%23vnEeKZfHHA.4872@xxxxxxxxxxxxxxxxxxxxxxx
Hi Paul,

Thanks for your reply.

I had not seen that MSKB, but it does look relevant. I'll investigate the
receiving domain's firewall setup.

I am unaware if the receiving domain has this problem with other
'senders', we don't have that close a relationship with them.

Using helo or ehlo from Telnet results in the same outcome - connection
dropped immediately after typing first letter.

Unfortunately our ISP does not have a mail server we can relay through.

Thanks,

Mark


"Paul Ford (Edge IT Ltd)" <paulford@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:%23NTHn0RfHHA.596@xxxxxxxxxxxxxxxxxxxxxxx
Mark,

Have you had a look at http://support.microsoft.com/kb/895857/en-us

Does anyone else report issues sending to this domain ?
What happens if you try sending an ehlo instead of helo command from
telnet ?
Do you have an ISP that you can bounce messages off of and if so is it
possible to try sending messages that way just to see if it works, not
as a solution ?

Regards

Paul Ford


"Mark" <nospam@xxxxxxxxxxxxx> wrote in message
news:uURiZdKfHHA.4652@xxxxxxxxxxxxxxxxxxxxxxx
Hi there,

We are having trouble sending email to one particular domain. Other
domains work fine.

After 4 hours we get a DSN delay from our own Exchange server saying
Status: 4.4.7

After 48 hours, we get an undeliverable message from our server
stating:
=====================================
Could not deliver the message in the time limit specified. Please retry
or contact your administrator.
<(our domain) #4.4.7>
=====================================

I tried telnet to the recipients email server from our exchange server,
and it connects OK, but as soon as I type 'H' for Helo, or 'E' for
Ehlo, the telnet session is ended with "Connection to host lost". See
this command prompt dump:
=====================================
220 hfexch.holdfast.com.au Microsoft ESMTP MAIL Service, Version:
5.0.2195.6713
ready at Thu, 12 Apr 2007 11:28:48 +0930
H

Connection to host lost.

C:\Program Files\Exchsrvr\bin>
=====================================

Any ideas what can cause the Telnet session to drop after only a single
character is typed in? I expect this is related to the problem.

Thanks,

Mark









.

Relevant Pages

  • Re: Cannot send mail to "some" domains
    ... I was able to telnet to my server and send email to myself as well as my ... of anyone not receiving inbound emails at this time. ... the addresses from my personal email account outside. ...
    (microsoft.public.exchange.admin)
  • Re: how to handle multiple-message-in-same data-buffer (async programming)
    ... if it's _not_ on separate ... then the recipient (whether server or client) is by definition ... If you're talking about receiving two messages that were sent on the same ... connection by the same sender, then the only "same time" you could be ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: IP Blocker in SBS2003 exchange
    ... > What I was trying to explain in the telnet section was that I realise ... > the server is listening for connections on ports 110 and 25. ... > but he can connect to port 110. ... > well as another wireless broadband connection. ...
    (microsoft.public.windows.server.sbs)
  • Re: how to handle multiple-message-in-same data-buffer (async programming)
    ... then the recipient (whether server or client) is by definition _not_ receiving two messages exactly at the same time. ... If you're talking about receiving two messages that were sent on the same connection by the same sender, then the only "same time" you could be talking about is that they may be combined into a single chunk of data to be received by your server. ... This means that before you start processing a chunk of received data, you need to check to make sure you've completed receives on all of the buffers that were posted before the one you're operating on currently. ...
    (microsoft.public.dotnet.languages.csharp)
  • RE: Your message did not reach some or all of the intended recipie
    ... In your details you are saying to type the following command ... > SMTP telnet session. ... When the issue happens again, in the Exchange Server, please telnet ... > times to close the connection to the server and leave the Telnet session ...
    (microsoft.public.windows.server.sbs)