If you searched for telnet smtp, this is the fastest diagnostic sequence:

  1. verify basic SMTP connectivity
  2. verify TLS with OpenSSL
  3. validate auth and envelope commands
  4. run inbox and deliverability checks

Quick answer: should you still use Telnet for SMTP?

Yes for first-pass diagnostics. Telnet is useful for plain connectivity and protocol responses, but it is not encrypted. For secure checks, use OpenSSL with STARTTLS.

Basic SMTP connectivity test with Telnet

telnet smtp.example.com 25

If the connection works, you should see an SMTP greeting such as:

220 smtp.example.com ESMTP ready

Then test command flow:

EHLO test.local
MAIL FROM:<sender@example.com>
RCPT TO:<recipient@example.com>
QUIT

Useful response patterns:

  • 220: service ready
  • 250: accepted
  • 4xx: temporary issue
  • 5xx: permanent failure (auth/policy/config)

For authenticated submission flows, test STARTTLS on port 587:

openssl s_client -starttls smtp -connect smtp.example.com:587

After TLS negotiation, run:

EHLO test.local

Confirm advertised capabilities such as STARTTLS and AUTH.

Related references:

Common SMTP troubleshooting patterns

Cannot connect to SMTP host

Likely causes:

  • wrong hostname or port
  • blocked outbound firewall or VPC egress
  • provider network restrictions

STARTTLS fails

Likely causes:

  • TLS mismatch for selected port
  • certificate chain or trust issues
  • middlebox/network interference

535 auth failure or 550 relay rejection

Likely causes:

  • incorrect credentials
  • sender identity policy mismatch
  • relay restrictions for account/domain

Use Telnet/OpenSSL as step one, not final validation

Protocol checks do not confirm inbox placement or template correctness.

Follow with:

Release checklist after SMTP connectivity tests

  1. Verify SMTP connectivity and capability responses.
  2. Verify TLS and auth posture with OpenSSL.
  3. Validate end-to-end delivery and content in real inbox tests.
  4. Add webhook-based observability for bounce and failure events.
  5. Re-run checks after DNS or provider config changes.

FAQ

Is Telnet secure for SMTP testing?

No. Telnet is plaintext and best used only for low-risk connectivity checks. Use OpenSSL for TLS validation.

Should I test SMTP on port 25 or 587?

Port 587 is usually preferred for authenticated client submission. Port 25 is commonly restricted in cloud environments.

Why does SMTP test pass but users still do not receive email?

Connectivity success does not guarantee inbox placement. Run deliverability and inbox-based integration tests.

Next steps