How to Test SMTP Server: Complete Guide with Free Tool

Testing your SMTP server is a fundamental skill for troubleshooting email delivery issues, verifying configuration settings, and ensuring your application can send emails correctly. Whether you’re a developer or system administrator, knowing how to properly test SMTP connectivity can save you hours of frustration. Let’s explore the complete toolkit—from manual command-line testing to specialized free tools.

Understanding What You’re Testing

Before diving into the testing methods, it’s helpful to understand what an SMTP test actually accomplishes. SMTP (Simple Mail Transfer Protocol) is the standard protocol for sending email messages from one server to another . When you test SMTP, you’re essentially simulating an email send to verify that:

• The server is reachable and responding
• Authentication works correctly
• The server accepts messages for delivery
• Mail flow is functioning as expected

Testing is particularly useful if you’re having trouble sending or receiving messages, as it allows you to manually send SMTP commands to a messaging server and see exactly how it responds .

Method 1: Telnet for Manual SMTP Testing

The most direct way to test an SMTP server is using Telnet—a command-line tool that lets you send raw SMTP commands to a mail server. It’s like having a conversation with the server where you type each command and see the response.

Before You Start: Install Telnet

On most Windows versions, you’ll need to install the Telnet client before you can use it . On Windows 10 and 11, you can enable it through “Turn Windows features on or off” in Control Panel, or use the command:

text

dism /online /Enable-Feature /FeatureName:TelnetClient

On macOS and Linux, Telnet usually comes pre-installed.

Find the SMTP Server Address

To connect to an SMTP server, you need its Fully Qualified Domain Name (FQDN) or IP address. If you don’t know the address, you can use the nslookup command to find the MX (Mail Exchange) record for a domain:

1. Open a command prompt and type nslookup, then press Enter
2. Type set type=mx, and press Enter
3. Type the domain name (e.g., gmail.com.), and press Enter 

The output will show the mail servers for that domain, with preference values indicating priority (lower numbers are preferred).

Step-by-Step Telnet SMTP Test

Once you have the server address, here’s how to test SMTP communication:

1. Open a Command Prompt and type telnet, then press Enter
2. Optional: Set localecho by typing set localecho to see characters as you type 
3. Open the connection: Type OPEN mail.example.com 25 (replace with your server address) 
4. Identify yourself: Type EHLO yourdomain.com – this tells the server who you are 
5. Set the sender: Type MAIL FROM:<sender@example.com> 
6. Set the recipient: Type RCPT TO:<recipient@example.com> 
7. Start the message: Type DATA 
8. Add subject: Type Subject: Test message
9. Add a blank line then type your message body
10. Send the message: Type a period . on a line by itself 
11. Close the connection: Type QUIT 

Important Tip: You can’t use the backspace key in a Telnet session after connecting. If you make a mistake, you’ll need to press Enter and start the command again .

Reading SMTP Response Codes

SMTP servers respond with three-digit numerical codes. The first digit is most important for understanding success or failure :

• 2.y.z – Success! The command was completed
• 3.y.z – Accepted but needs more information
• 4.y.z – Temporary failure, try again later
• 5.y.z – Permanent failure, command rejected

Method 2: Online Tools and Browsers

Microsoft Remote Connectivity Analyzer

For Exchange environments, Microsoft offers a free online tool that simplifies SMTP testing. Instead of manually typing Telnet commands, you can use the Remote Connectivity Analyzer at https://testconnectivity.microsoft.com/ .

Select “Inbound SMTP Email” test, follow the step-by-step instructions, and the tool will run the test for you and display the results . This is particularly helpful if you’re not comfortable with command-line tools or want a more structured testing approach.

Online SMTP Debug Tools

There are also browser-based SMTP debug tools that let you test SMTP connections without installing anything. One example is the SMTP Debug Tool, an accessible technology tool for developers, maintainers, and owners of websites and apps to check SMTP connections and see full session logs online .

Email Verification Services

For a more specific use case—verifying whether an email address actually exists—services like MailCannon.pro provide real-time SMTP verification, MX record checking, and disposable email detection directly from a web browser .

Method 3: Local Development with MailHog

For developers who need to test email functionality during development without sending actual emails, MailHog is a game-changer. It’s a free, open-source tool that creates a “fake” SMTP server on your local machine .

What Makes MailHog Special

Instead of actually sending emails to real inboxes, MailHog intercepts all messages sent to it and displays them in a clean web interface. This means you can test user registration emails, password resets, and order confirmations without:

• Accidentally spamming real users
• Waiting for test emails to arrive
• Hitting sending limits on sandbox services 

How to Use MailHog

• Install via Docker, binary file, or Homebrew on macOS
• Configure your application to use localhost:1025 as the SMTP server (no password needed)
• Open http://localhost:8025 in your browser to view all “sent” emails 

Important: MailHog is designed for development and testing only—not production use. It’s a “mail sandbox” that keeps all emails locally in memory and never sends them to real recipients .

Common Testing Scenarios

Testing Mail Flow from the Internet

If you want to test whether external servers can send email to your organization, Telnet from an external location to your SMTP server on port 25 . This helps verify that your mail exchanger is reachable and accepting connections.

Testing Authentication

When you’re getting SMTP authentication failures, a manual Telnet test can reveal what’s going wrong. After sending EHLO, look for 250-AUTH in the response—this indicates what authentication methods the server supports .

Testing Local Email Functionality

For WordPress sites or web applications, using a tool like MailHog during development lets you verify that your application’s email-sending code works correctly before going live .

Quick Reference: SMTP Commands

Command	Purpose	Example
EHLO	Identify yourself and request supported features	EHLO example.com
MAIL FROM	Set the sender address	MAIL FROM:<user@example.com>
RCPT TO	Set the recipient address	RCPT TO:<user@domain.com>
DATA	Start the message content	DATA
QUIT	Close the connection	QUIT

When to Use Each Method

• Telnet: Best for deep troubleshooting of connectivity issues and server responses
• Microsoft Remote Connectivity Analyzer: Ideal for Exchange server administrators
• Online SMTP Debug Tools: Quick browser-based testing without installation
• MailHog: Essential for developers during local development and testing
• Email Verification Services: When you need to verify individual email addresses

Bottom Line

Testing your SMTP server doesn’t have to be complicated. For quick checks, a browser-based tool might be sufficient. For serious troubleshooting, Telnet gives you complete control and visibility into the SMTP conversation. And for development work, MailHog provides a safe, free sandbox environment.

The key is choosing the right tool for the right situation. A connection begins with a 220 response code , and understanding what each code means will help you diagnose most issues quickly. Whether you’re verifying a production server or testing a new email feature, these tools will get the job done.