Fundamentals

What is SMTP? A Plain-English Guide

The protocol behind every email you have ever sent, explained without the RFC jargon.

Short answer: SMTP (Simple Mail Transfer Protocol) is the standard protocol mail servers use to send email to each other. Your app or email client hands the message to an SMTP server (usually on port 587), and that server delivers it to the recipient's mail server.

SMTP in one sentence

SMTP (Simple Mail Transfer Protocol) is the set of rules two mail servers use to hand a message from one to the other. It has been doing this job, largely unchanged, since 1982.

The handshake, step by step

When your app sends an email, roughly this happens:

  • Connect. Your client opens a connection to the recipient's mail server, usually on port 587 or 465.
  • Greet. The client says EHLO, the server replies with what it supports.
  • Authenticate. The client proves who it is, usually with a username and password (an API key, in most modern providers).
  • Declare sender and recipient. MAIL FROM and RCPT TO tell the server who the message is from and where it is going.
  • Send the message. DATA followed by the headers and body, ended with a single dot on its own line.
  • Close. QUIT ends the session.

SMTP only delivers between servers, not to the inbox

SMTP's job ends once your message reaches the recipient's mail server. What happens after that — landing in the inbox, promotions tab, or spam folder — is decided separately, based on authentication (SPF, DKIM, DMARC) and sender reputation. See SPF, DKIM and DMARC explained.

Ports you'll actually use

PortEncryptionUse it for
587STARTTLS (upgrades after connecting)The standard choice for submitting mail from an app
465TLS from the first byteAn older but still valid alternative, blocked by fewer networks in practice
25Plaintext, or STARTTLSServer-to-server relay only — most ISPs block outbound 25 for residential and cloud IPs

Why your own SMTP server is usually a bad idea

Running your own mail server means managing IP reputation, blocklist monitoring, retry queues and bounce handling yourself. Most teams instead send through a relay — your app still speaks SMTP (or a REST API), but the provider owns the infrastructure and the reputation.

Frequently asked questions

Is SMTP still used in 2026?

Yes. Nearly every transactional and marketing email still travels over SMTP at some point, even when your app talks to a REST API — the provider relays it via SMTP on the last hop.

What is the difference between SMTP and IMAP/POP3?

SMTP sends mail out. IMAP and POP3 are how a mail client reads mail that has already arrived in a mailbox. They solve opposite ends of the problem.

What is SMTP email?

"SMTP email" is just email sent through an SMTP server, as opposed to an HTTP API. Your app connects to the SMTP server with a username and password, hands over the message, and the server delivers it.

How do I use SMTP to send email?

You need an SMTP host, port (587 with STARTTLS is the usual choice), a username and a password from your email provider. Put those into your app, framework or email client, verify your sending domain with SPF, DKIM and DMARC, and send.

How can I get a free SMTP server?

Use an email provider's SMTP relay with a free tier instead of running your own server. Sendcorex includes SMTP relay on its free plan: create an account, verify your domain and use the SMTP credentials from the dashboard.

Skip the server, keep the protocol

Sendcorex gives you an authenticated SMTP relay and a REST API on the same account — free up to 3,000 emails a month.

No credit card required