Can’t connect to SMTP Server to send outgoing mail

Most common reason for this is a spam preventative measure by ISP’s to block outgoing port 25. The best way to check is to open a command prompt in Windows and telnet to port 25.

ie. Start > Run > Type `cmd.exe`

When the command windows opens type `telnet mail.yourdomain.com 25` (without the quotes)

If the port is open you should get a response back like this:

Plesk Server:

Trying 85.13.195.119…
Connected to mail.weycrest.com.
Escape character is ‘^]’.
220 www3.weycrest.com ESMTP

Cpanel/WHM Server:

Trying 85.13.250.100…
Connected to xena.dediquick.net.
Escape character is ‘^]’.
220-xena.dediquick.net ESMTP Exim 4.52 #1 Sun, 28 Oct 2007 22:33:03 +0000
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.

If you are getting no responses, and you have no local firewalling issue’s then your ISP is blocking out going mail.

Workarounds:

  • On Plesk you can send mail on the secure port, which ISP’s don’t usually block. This also has the advantage of securing the passwords you use to login to email (especially useful on untrusted wireless networks).
  • On Cpanel you switch the port of your email client (Outlook, Thunderbird etc) to port 26.

But the most obvious solution is to use your ISP’s outgoing (SMTP) server if they permit you to use your domain name as part of the email address!

Share and Enjoy:
  • del.icio.us
  • Reddit
  • Simpy
  • Spurl
  • Digg
  • SphereIt
  • StumbleUpon
  • Technorati
  • PlugIM
  • blogmarks
  • Bumpzee
  • Furl
  • Slashdot
  • YahooMyWeb
  • BlinkList
  • Facebook
  • Google
  • LinkedIn
  • Mixx
  • Pownce
  • Propeller
  • Taggly
Leave a Reply

You must be logged in to post a comment. Login »

Blog Hosted by Weycrest.Com" | Managed Dedicated Servers | Hosted Exchange 2007 | Cheap Backpacker Insurance | Gap Year Insurance

Weycrest Knowledgebase is Digg proof thanks to caching by WP Super Cache!