SMTP port number

An SMTP port number is the TCP port a mail client or application connects to when handing a message to a mail server. The port selects the role and the encryption model, not the speed or the reliability of the send. Four numbers cover essentially all mail submission: 587, 465, 25 and 2525.

VerifiedBy Kam Low, Co-founder·Updated

The distinction that matters is submission versus relay. Submission is an authenticated client handing over a new message, and it belongs on 587 or 465. Relay is one mail server passing a message to another, and that is port 25. Choosing a relay port for a submission job is the single most common SMTP misconfiguration.

Common SMTP Ports and Uses

Ports 587 and 465 both carry authenticated submission over TLS and differ only in when encryption starts. Server-to-server relay runs on port 25, which most consumer and cloud networks block outbound. Some providers also accept 2525, an unofficial alternative with no protocol difference, for networks that block 587.

The four SMTP port numbers
587
465
2525
25
submission default
RFC 6409 · STARTTLS
submission
implicit TLS, encrypted from the first byte
provider fallback
no IANA assignment; for networks that block 587
server-to-server relay
widely blocked for client submission as anti-abuse policy
Authenticated submission
Relay
Three of the four numbers do the same job: authenticated submission, with 587 the default. Port 25 is the odd one out, relay between servers, blocked for clients almost everywhere.

Port 587

Port 587 is the default port for authenticated mail submission, defined as the submission port in RFC 6409. It uses STARTTLS, which opens as plaintext and upgrades the connection to TLS via the STARTTLS command before authentication. A correctly configured server on 587 requires that upgrade and refuses to accept credentials over an unencrypted connection.

This is the port to choose unless something specific rules it out. Mail clients default to it, providers document it first, and networks that block port 25 generally leave it open.

Port 465

Port 465 uses implicit TLS: the connection is encrypted from the first byte, with no plaintext phase and no upgrade command. It was deprecated in the late 1990s, then formally reinstated for message submission in RFC 8314, which recommends implicit TLS over STARTTLS for new deployments.

Functionally the outcome matches 587. The difference is that the encryption cannot be skipped, because there is no unencrypted state to skip it from.

Port 25

Port 25 is the original SMTP port and it remains the standard for server-to-server relay, which is how mail moves between mail servers across the internet. It is not intended for authenticated client submission, and most internet service providers, cloud hosts and office networks block outbound traffic on it.

The blocking is deliberate anti-abuse policy rather than a limitation. An unauthenticated open port that accepts mail for anywhere is the exact shape of an open relay, and compromised machines used it to send spam at scale.

Port 2525

Port 2525 is not assigned to SMTP by IANA and carries no protocol difference. Several email providers listen on it as a fallback for networks that block 587, and it behaves as an alternative submission port with the same authentication and TLS expectations.

It is a workaround for a blocked network, and it works only where the receiving provider has chosen to support it.

Every port on this page is a workaround for something else: a blocked network, an old default, a relay rule written before application mail existed. The actual fix for most people reading this is not picking the right port number, it is not touching a port at all. Describe the email to Claude, ChatGPT, Cursor or Codex and Nitrosend's MCP server sends it, so the four numbers above stay reference material instead of something you configure by hand.

Go deeper

First send in thirty seconds.

Simple pricing. Unlimited contacts.

Every plan includes full stack emailing: Flows, Newsletter Campaigns and Transactional Email, plus our NitroWheel LLM and all agent integrations (Claude, ChatGPT, Codex, Cursor and others). Pay for what you send, not who you store.

Choose your billing interval

Every paid plan includes 3 agent inboxes and no Nitrosend footer.

Starter

For your first email program.

$16USD / month

$192 billed yearly.

20,000 emails / month

Choose Starter
  • 5 brands · 3 seats
  • 5 custom sending domains
  • 500 email verifications/month
  • $1.50 / 1,000 extra emails

Pro

For a growing audience.

$40USD / month

$480 billed yearly.

60,000 emails / month

Choose Pro
  • 10 brands · 5 seats
  • 10 custom sending domains
  • 1,000 email verifications/month
  • $1.20 / 1,000 extra emails

Growth

For teams and agencies.

$120USD / month

$1,440 billed yearly.

200,000 emails / month

Choose Growth
  • Unlimited brands · 10 seats
  • 25 custom sending domains
  • 2,500 email verifications/month
  • $0.90 / 1,000 extra emails

Scale

For high-volume sending.

$240USD / month

$2,880 billed yearly.

500,000 emails / month

Choose Scale
  • Unlimited brands · 20 seats
  • 100 custom sending domains
  • 5,000 email verifications/month
  • $0.70 / 1,000 extra emails
Enterprise

Hey, big sender.

Sending 500,000+ emails a month? Get a custom plan designed for you, with volume pricing for sending, verification and enrichment.

Start free. No card needed.

5,000 emails to start, then 500 emails every month. No expiry on your starter emails.

Start free

Daily allowances depend on your plan and sender standing. Strong list, domain and delivery evidence can raise standing, including on day one. Trusted receives the full plan allowance; available email credits, safety checks and delivery pacing still apply.

Free forever. No credit card required. See full comparison →