SMTP Test: Diagnose Why Your Email Won't Send
SMTP Test
An SMTP test verifies that your email sending configuration works, checking the server host, port, credentials, and TLS connection so you can diagnose why mail is failing to send.
What an SMTP test checks
It connects to your SMTP server and walks the conversation between client and server, confirming the host and port are right (usually 587 or 465), the username and password authenticate, and the TLS or SSL connection establishes. When mail is failing to send at all, rather than landing in spam, this is the test to run.
Common failures it catches
An authentication error usually means wrong credentials or, on Microsoft 365, SMTP AUTH disabled on the tenant. A connection timeout usually means a blocked port. A TLS handshake error means the encryption mode doesn't match the port. A 550 error points at the recipient or a content or reputation block rather than your configuration.
These are not hypothetical failures. Chong, on our team, traced a dead outbound path in our own app to a wrong SMTP port, and mail flowed the moment he fixed it. George, our CEO, watched a valid least-privilege SendGrid key get reported as invalid because our Test connection probed GET /v3/verified_senders, an endpoint that needs the Sender Authentication scope a mail-send key does not carry. The check was wrong, not the key.
The trap that catches the most people is the word verified. George is blunt about it: verified only means the DNS records are valid, it does not mean allowed to send right now. One customer's DNS page showed verified while their first test email stayed blocked, because a second gate, the from-address domain match, was still failing. The verified list held the out. subdomain, not the bare domain the from address used. Running a full domain deliverability check catches that mismatch, because it reads the records against the address you actually send from.
Worse than a loud failure is a silent pass. Nick, on our team, worked a BYO SES case where test sends were marked sent whenever the sender returned without raising, with no check of whether SES actually accepted the message. The customer had 9 days, 2026-07-01 to 07-10, where test sends silently succeeded and delivered nothing. Our send paths now fail closed.
Beyond the SMTP test
A passing SMTP test means mail will send, not that it'll reach the inbox. For that, add a spam test email and confirm authentication. A lower-level option is a telnet smtp test run by hand.
None of it costs anything to start. The free testing stack covers the checks above for a small sender, the testing hub lays out which instrument answers which question, and email deliverability is the discipline all of them serve.
A full preflight goes further than the socket. The preflight in George's Email Marketing Bible, built from 908 sources, resolves wrapped CTA URLs, runs a spam score, weighs image against text, lints for dark mode and delivers a copy to a seed address. His baseline rule sits under all of it: offer a test send before any real send.
We hold our own releases to a client-validation bar for the same reason. George's line on an email rendering fix: do not merge until a real Outlook, a Gmail app and a Yahoo have each passed it, because local QA cannot exercise Outlook. And before features touch customers we dogfood the whole path across internal accounts: send, receive, preview and reply validation, end to end.
Running an SMTP test by hand, reading the response codes, and guessing which setting is wrong is exactly the kind of manual configuration an AI agent should be doing instead of you. Tell Claude, ChatGPT or Cursor to send the email, and Nitrosend's MCP server holds the connection, authentication and retry logic behind it, so there is no port or handshake left for you to test.
How Nitrosend removes the SMTP guesswork
There's no host or port to test because you don't configure SMTP by hand. You connect an account from your AI agent and send, and once DNS setup is complete the Setup center sends a real test email automatically to confirm the path end to end.
That is the practical case for moving transactional email off hand-rolled SMTP entirely. An email API replaces host, port, and TLS configuration with an authenticated request, so the whole class of failure this page diagnoses stops being yours to debug.
The Test connection feature does the equivalent of this page for connected providers: it verifies the setup of a BYO provider account before you rely on it. Test sends run as a dry run plus preflight covering domain verification, sender configuration, audience validity, content compliance and a spam score, a pipeline Chong maintains. George's own read after a composing session on the API: POST /v1/my/templates/{id}/send_test is the most reliable endpoint in the API, 3 for 3 with instant Gmail delivery.
The onboarding defaults exist because of what we watched users do. Gmail and the other inbox providers expect a subdomain setup for sending, and George once watched an onboarding where the user, someone who sets up domains for his own customers, typed his own email address in as the sending domain. His fix was to make onboarding default the sending domain to prefilled values behind a single Set button.
Guardrails run on test sends too. Our safety gate once blocked a legitimate user around their 8th test email with no obvious way to say they were not a spammer, which reshaped how the gate responds. The caution is deliberate. George's warning to the team over a 2,500-contact VC list was four words: do not trigger a test send to them all. And our internal seeding tooling ships off by default, in a proof mode that delivers only to the operator until switched live, with a kill switch on an auto-disable date and guards re-checked at enqueue, perform and pre-send.
FAQ
What is an SMTP test?
A check that your email server's host, port, credentials, and TLS settings are correct, used to diagnose why mail is failing to send rather than why it lands in spam.
Why is my SMTP test failing?
Common causes are wrong credentials, a blocked port, an encryption mode that doesn't match the port, or SMTP AUTH disabled on a Microsoft 365 tenant.
Does a passing SMTP test mean my email will reach the inbox?
No. It means the message will send. Inbox placement also depends on authentication, reputation, and content, which a spam test checks.