When your GUI mail client doesn't work, you need to know whether the problem is at the server or the client. You could download a different client (Thunderbird, if you are using Outlook or Apple Mail) but why spend that time when you can test from the command line?
Note that some ISP's won't allow you to make port 25 connections to anything but their mail servers. This is to keep viruses from sending mail. If you need to test some other server, you may not be able to without using a system that does not impose this restriction.
The lines preceded by numbers are typical responses. The actual response may be different.
$ telnet mail.somewhere.com 25
Trying 192.168.75.194...
Connected to smtp.somewhere.com.
Escape character is '^]'.
220 smtp.somewhere.net ESMTP Sendmail 8.9.3+Sun/8.9.1; Thu,
12 Oct 2000 04:39:40 -0700 (PDT)
helo aplawrence.com
250 smtp.somewhere.com
mail from: tony@aplawrence.com
250 tony@aplawrence.com... Sender ok
rcpt to: foobah@aplawrence.com
550 foobah@aplawrence.com... Relaying denied
rcpt to: foobah@somewhere.com
250 foobah@somewhere.com... Recipient ok
data
354 Enter mail, end with . on a line by itself
test
look ma no headers!
.
250 HA00945 Message accepted for delivery
quit
221 smtp.somewhere.com closing connection
You might also need to do a
helo mymachine.mymachine.com
first, and addresses may need to be in angle brackets: <foo@xyz.com>
Remember: some ISP'S block your outgoing packets, only allowing port 25 to their SMTP server. You won't be able to test any other server if this is true.
If your server accepts secure smtp (it should), you can use openssl instead of telnet:
openssl s_client -connect mail.yourserver.com:465 -crlf
(If you don't use the "-crlf" you may have trouble using "." to end a DATA input)
I also have found Clean Code Email very helpful for command line testing.
If you have sendmail. you can use it from the command line with -v to see what really happens. See Debugging sendmail problems

Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
Click here to add your comments
Mon Jan 5 10:32:26 2009: 5085 aravind
The post is so usefull thanks a lot.
Wed Sep 1 17:01:50 2010: 8948 alain
http://giantdorks.org/alain/
Howdy,
I’ve always used telnet for SMTP testing. Finally, got sick of copy/pasting and decided to write a quick script. But scripting telnet is a pain. Netcat to the rescue! Here's the script: http://giantdorks.org/alain/smtp-test-message-via-shell-script-using-netcat-instead-of-telnet/
Cheers,
Alain
Wed Sep 1 17:38:31 2010: 8949 TonyLawrence
Thanks, Alain!
I'm annoyed that Verizon won't let me do this from my network anymore. I now have to ssh to my webhost to do this kind of testing.
Wed Sep 1 20:55:53 2010: 8952 alain
http://giantdorks.org/alain/
Yep, ISPs blocking port 25 is all too common. That's why I configure my smtp boxes to listen on 465 and 587 as well, which typically aren't blocked.
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar