Outbound Email not Sending - Sitting in Outbound Queue


Exchange 5.5 running on NT 4 has following problem.

All outgoing Email sits in the Outbound Queue.  If I open any of the Queued messages [Host Unreachable] is the reason given.  I need to get this resolved real fast ;-).  The machine has IP Connectivity on the LAN.  From the Command Line I can ping and resolve Apple.com  I am however unable to telnet on port 25 to the Exchange machines IP address from a LAN PC or even when tried on the Exchange Server.

Port 25 is open on the firewall. Please help :-(
Who is Participating?
As your old server is still available, you could compare your new setup to the old one and see if it saves you a reload.

The address book in the Outlook Mail Profile my still be looking for the old GAL from the other server. In the Outlook client, you should be able to select which GAL or addressbook to use as default.

Hi robjeeves,
Either the server isn't up, or you're firewalled somewhere along the line.
First, can you ping the server? Do you know the difference between the MX records and the domain name?

A good test is to go to network-tools.com or dnsreport.com and enter the username you want to send mail to and run the mail tests.  If that works you're issue is most likely local.
Try telnetting port 25 to another mail server you know works (note this is usually different to apple.com; you need to do an mx record.  A DNSreport.Com on the domain will show you the MX records to try).
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

this could be a dns issue or ayour outbound port 25 is blocked . use nslookup  at the command prompt .  then type
> set type =mx
not put in the doamin name e.g hotmail.com or yahoo.com etc .
if you get the correct output then your dns is ok .

try to check with your network admin if your filrewall or router has port 25 closed . you can check this by telnenng some mail server at port 25 . many mail server dont let you telnet , but is u get an error that unable  to connect at port 25 then probably it is a firewall issue .  
Doesn't sound like a DNS issue, but I would usually do an nslookup myself. DNSReport just makes this a little easier (and shows a lot of other potentially useful info)... You can then ping the resulting name or just try telnetting to it as I have advised.
In my experience (and I've tried hunderds or thousands by now) every mail server accept port 25 requests from telnet. Some will not send an echo response, but if you know what you are typing is correct, they will respond to the commands.
The only exception for a working public mailserver could possibly be a firewall filtering layer 7 traffic (something such as Cisco's CBACS).  If you really want, I can teach you how to use telnet properly as it is a wonderful tool.  Give me a server you don't believe responds to telnet and I'll help :)
So hows it going there?  Can you telnet externally to a mail server?
After just re-reading your post, it looks like you cannot telnet to your OWN mail server on the LAN from a client PC on the LAN (ie: telnet lanmailservername 25)??
If the SMTP protocol is not configured correctly on your server mail will not go out. There are many options and or reasons why this can be the case, so before I go on, please confirm whether this is an issue.
robjeevesAuthor Commented:
hi - That is correct - I am unable to telnet to port 25 on the local exchange box.  . The internet Messace connector starts with no problem.

Do you receive mail directly to that box from the net? Or do you pickup POP3 from a server elsewhere (like your ISP?).
Unfortunately I'm rusty on Exchange 5.5, lets see how we go.
You might be able to cut to a solution by forwarding your emails to your ISPs SMTP Server (Usually called a smarthost but it might be 'Forward All Messages To Host:'.
At this point we should probably check to see if your ISP will allow you to relay. You can do this by telnetting to the isps provided SMTP server (port 25 of course) then type as follows:
helo your.external.ip.address
mail from: user@yourdomain.com
rcpt to: user@somewhereelse.com
If you get an error relaying denied, you may need a username/pass - it is often the same as the POP3 pickup). If that doesn't work, you may need to call your ISP to continue with that option. If the username/pass thing works, you'll need to find where to enter this authentication into Exchange... Of course if it was already using this option you should try changing it to using DNS.
Still stuck?
Try the following (including the nslookup/telnet etc.)
Sorry, wish I could give you a step-by-step guide, but it's been too long & I don't have a server handy.  Hope this nails your solution.  I'll check again in the next 24 hrs or so. :)
robjeevesAuthor Commented:
hi - I actually had an Exchange Guru called out and we built a new Exchange Box (Same organisation) and setup a new IMC.  I've moved all the mail boxes off the original Server onto the New Server.  I have followed the instructions in


Trouble is soon as I power of the Original Server (as a test before I format and re-install) No one can access the Address Book.  The Message is "Network Problems are preventing Access . . . . ." Clearly the Clients are looking for the original Server. This is now the problem. I'm happy to leave the points available if we can get to a point where I delete the original Server so I can begin a rebuild.

p.s The instances for Public folders appear to work fine with the Original Server powered off
robjeevesAuthor Commented:
Hi - I actutually worked it out as the Clients held on to the old Servers name. A quick close/reopen Outlook of Outlook and everything was fine.  I'm now well on the way to rebuilding the new box.  Thanks everyone for input.
Glad to hear it.  Hope all goes well :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.