100% Inbox Delivery

HomeBlog › How to Smtp server

How to Smtp server

Published October 12, 2024 · Updated July 19, 2026 · SMTP & Deliverability

Every email you have ever sent passed through an SMTP server — you just never saw it happen. SMTP is the quiet engine of email, the system that actually moves a message from your outbox to someone else's inbox. Understand it, and you understand why some emails sail into the inbox while others vanish into spam.

This guide explains what an SMTP server is, how it works in plain English, and how to set one up for reliable, high-volume sending.

What is an SMTP server?

SMTP stands for Simple Mail Transfer Protocol. An SMTP server is a computer whose job is to send and relay outgoing email. When you hit "send," your mail client hands the message to an SMTP server, which figures out where it needs to go and delivers it to the recipient's mail server. Think of it as the post office for email: it accepts your letter, reads the address, and routes it to the right destination.

Port 587
standard submission port
SPF/DKIM
proves you're legitimate
Dedicated IP
controls reputation

How an SMTP server works, step by step

  1. Submission. Your mail app connects to the SMTP server (usually on port 587) and authenticates with a username and password.
  2. Handoff. The server accepts your message and reads the recipient's domain.
  3. Lookup. It queries DNS for the recipient domain's mail (MX) servers.
  4. Delivery. It connects to the recipient's server and transfers the message.
  5. Authentication check. The receiving server verifies SPF, DKIM, and DMARC to decide inbox vs spam.

Shared vs dedicated SMTP servers

This is the distinction that matters most for deliverability. On a shared SMTP server, many customers send from the same pool of IPs — so one spammer can damage everyone's reputation. On a dedicated SMTP server, the IP is yours alone: your sending history, your reputation, your control.

Why it matters: Two identical emails can get opposite results purely because of the IP they were sent from. A clean, dedicated IP with proper authentication is the single biggest lever you have over inbox placement.
Related reading: Mailgun smtp relay · Cloudflare smtp relay · test your email deliverability
Your own SMTP server

A dedicated SMTP server, configured for you

Dedicated IP, unlimited sending, and automatic SPF/DKIM/DMARC — live in minutes. Just plug in the credentials and send. From $39.99/mo.

Explore unlimited SMTP →Compare plans

How to set up your own SMTP server

You have two paths. You can build and maintain your own mail server — powerful, but you own the DNS, security, blacklist monitoring, and IP warm-up yourself. Or you can use a managed dedicated SMTP service, where the server, dedicated IP, and all authentication are configured for you. For most senders, managed wins: you get the control of a dedicated server without the maintenance headache. You simply drop the SMTP host, port, username, and password into your app and start sending.

Frequently asked questions

What is an SMTP server used for?

Sending and relaying outgoing email. Whenever an app, website, or mail client sends a message, it uses an SMTP server to deliver it to the recipient's mail server.

What port does SMTP use?

Port 587 is the modern standard for authenticated submission (with STARTTLS), 465 is used for SMTP over SSL, and port 25 is used server-to-server. For sending from an app, use 587.

Do I need my own SMTP server?

If you send in volume or need reliable deliverability, yes — a dedicated SMTP server gives you a clean IP and full authentication control. A managed provider sets it all up so you skip the technical work.