Picking the best SMTP server for cold email isn't about finding the cheapest per-email rate, it's about finding a provider that won't shut your account down the moment your bounce rate looks like, well, cold email.
Cold email behaves differently than the marketing or transactional email most SMTP providers are built around, and that difference matters more than any feature comparison chart. You're emailing people who never opted in, so bounce rates run higher, spam complaints spike faster, and a chunk of mainstream email service providers ban cold outreach outright in their terms of service.
What you actually need from an SMTP provider for cold email is tolerance for that pattern, the option to move to a dedicated IP once your volume justifies it, and a support team that won't suspend your account the first time your complaint rate ticks up. Pair whichever provider you pick with a proper warmup process, see best email warmup tools and an ip warming schedule, because the provider alone won't build your reputation for you.
Amazon SES is the cheapest option by a wide margin, priced in fractions of a cent per email, and the infrastructure behind it is as reliable as anything AWS runs. But SES gives you almost no hand-holding: you start in a sandbox with tight sending limits, you have to request production access, and monitoring bounce and complaint rates is on you through SNS notifications rather than a friendly dashboard.
It's a strong choice if you're comfortable configuring DNS records yourself and want the lowest possible cost at scale, but it's not the pick if you want a provider that flags problems before they become a suspended account.
Postmark built its reputation on transactional email specifically, receipts, password resets, that kind of thing, and it polices content closely enough that cold outreach isn't really what it's for. SendGrid is more permissive and widely used for cold sending, though its shared IP pools mean your neighbors' sending habits can affect your reputation unless you pay for a dedicated IP.
Mailgun sits in a comfortable middle ground: a flexible API, region choice between the US and EU, and reasonable tolerance for cold email patterns, with dedicated IPs available once your volume qualifies. It's the one I see technical teams reach for most often when they want more structure than raw SES but more flexibility than a fully managed cold email tool.
SMTP2GO is a smaller name but a solid one for senders who want simple setup and responsive support without wading through AWS-style configuration. It's a reasonable middle-tier choice for people who don't need Amazon-level scale but want more structure than a bare-bones relay.
It's also worth knowing that some cold email tools bundle their own sending infrastructure so you never touch a separate SMTP provider at all, Instantly and Lemlist both work this way, see Instantly vs Lemlist if you'd rather have the sequencing and the sending bundled together instead of managing them separately.
If you're technical and sending at real volume, Amazon SES gives you the lowest cost with the most work required on your end. If you want more guardrails and a support team that answers emails, Mailgun or SMTP2GO are the safer middle ground. If you'd rather skip managing SMTP entirely and use a tool with sending built in, a cold email platform handles it for you at a higher per-seat cost.
Whichever you choose, the provider is maybe a third of the equation. List quality and a proper warmup schedule decide the rest, and skipping either one will sink even the best SMTP setup, see how to clean an email list before you scale sending volume.
No. Most mainstream email service providers prohibit unsolicited cold outreach in their terms of service and will suspend accounts that try it, since they're built around opt-in lists.
It depends on your volume. Most providers only recommend a dedicated IP once you're sending a few thousand emails a day consistently, below that a shared IP with a good reputation usually performs better.
Roughly two to six weeks depending on your target volume, ramping your daily send count gradually rather than jumping straight to full volume.
It's the cheapest option available but has the least built-in guidance, so it suits people comfortable configuring DNS records and monitoring bounce and complaint feeds themselves.
I've watched founders pick a great SMTP provider and still land in spam because nobody warmed the domain properly or fixed the authentication records. If you want a plain look at where your cold emails are actually landing before you scale volume, run a free Inbox Scorecard at Unbury.