Best SMTP Provider for Cold Email: What Actually Allows It (2026)

Last updated July 2026.

Most "best SMTP for cold email" lists rank providers on price, uptime and API quality, and skip the question that decides the matter: several of them tell you, in their own terms, not to send cold email through their service. Read the acceptable use policy before the feature table.

First, understand the two kinds of "SMTP"

It covers two products, and conflating them gets people suspended.

A bulk relay or email API (SendGrid, Mailgun, Amazon SES, Postmark, SMTP2GO, Elastic Email) is shared infrastructure: you hand them mail, they push it through pooled IPs alongside thousands of other customers. Their policies exist to keep unsolicited mail off that pool. When one tenant's complaint rate rises, everyone on the pool pays, so enforcement is blunt.

A real mailbox (a Google Workspace or Microsoft 365 account on your own domain) is just an inbox a human could also type in. It exposes an SMTP endpoint you can authenticate against, which is what a proper cold email SMTP sender that connects to the mailboxes you already own uses. The tradeoff: mailbox providers cap how much any one account sends per day, on purpose. We unpack the difference in SMTP relay vs SMTP server for cold email.

What each provider's own policy actually says

From each company's published policy, read July 2026. Nothing here is inference.

Policies read July 2026. Providers revise these documents; check the current AUP before you send. Brevo and Mailjet publish anti-spam policies we could not verify from a primary source, so we make no claim about them. Read them directly.

None of this is arbitrary: these companies sell shared sending reputation, and consent is the only line protecting it. Whether your B2B campaign counts as "unsolicited" turns on the policy's own definition and on whether you have consent, not on how targeted your list feels.

Can you use SendGrid for cold email?

Not within their rules. SendGrid requires affirmative consent for every non-transactional email and states plainly that consent cannot come from a purchased list, a lead generator or an affiliate: you must be the one who obtained it. Cold prospects never gave it. People do try, and accounts do get shut down. The same logic disqualifies Mailgun, Postmark, SMTP2GO and Elastic Email, for the reasons above. The capability is there. The permission is not.

Is Amazon SES good for cold email?

SES is excellent infrastructure and cheap at volume, but the AWS Acceptable Use Policy prohibits sending "unsolicited mass email", and a cold sequence to a prospect list is, on a plain reading, both unsolicited and mass. AWS also reviews sending reputation and can pause accounts. High risk, not a loophole.

What Google Workspace and Microsoft 365 actually allow

Mailbox providers take the opposite position: normal business email is fine, but no single mailbox may send at bulk scale. Their published limits:

Published limits, read July 2026, for standard paid plans. Verify against your plan.

Microsoft is blunt about why. Their documentation says the recipient rate limit exists "to discourage the delivery of unsolicited bulk messages", that "Exchange Online isn't suited to accommodate bulk-mailing scenarios", and that customers needing to send legitimate bulk commercial email "should use third-party providers that specialize in these services".

Read the two tables together and the answer appears. The bulk providers will not take your cold mail. The mailbox providers will, but not much per mailbox. So you use more than one.

What SMTP do cold emailers use?

Real mailboxes on real domains, several of them, with sends rotated across the pool. Not one Workspace account firing 500 emails, but a set of mailboxes each sending a modest, human-looking number per day, all warmed before they carry a campaign.

The published cap is not your working cap. Google will technically accept 2,000 messages from a mailbox, but a new mailbox sending 300 cold emails on day one lands in spam long before it nears any policy ceiling. Experienced senders keep each mailbox around 20 to 50 cold sends per day once warmed: a convention drawn from what survives filtering, not a number any vendor publishes. More in how many cold emails you can send per day.

How to work out how many mailboxes you need

The arithmetic is simple:

Mailboxes needed = target daily sends / safe sends per mailbox per day

Want 400 cold emails a day at a conservative 30 per mailbox? You need roughly 14. Spread them across secondary domains (two or three mailboxes each) so no domain carries the whole reputation risk, and keep your primary company domain out of the rotation. That is what a dedicated sending domain is for.

Two things then run continuously: every mailbox needs automated warm-up so it builds a history of normal, replied-to conversation, and sends must be spread across the pool with human-looking pacing rather than fired in a block. Doing that by hand across 14 mailboxes is a full-time job, which is why rotation belongs in the platform.

Google's sender requirements apply either way

Whatever you send through, Google's sender guidelines set a floor for anyone mailing Gmail addresses. All senders must authenticate with SPF or DKIM, keep valid forward and reverse DNS records, use TLS, and keep the spam rate reported in Postmaster Tools below 0.3%.

Cross 5,000 messages a day to Gmail and you become a bulk sender: SPF and DKIM and DMARC, From-header alignment, and one-click unsubscribe on marketing messages. Most cold teams sit below that, so the bulk rules often do not bite, but the all-senders rules always do. Our cold email deliverability guide covers the setup.

FAQ

Is it illegal to send cold email?

In the US, CAN-SPAM permits unsolicited commercial email provided you identify it honestly, include a valid physical address and honour opt-outs promptly. Provider policies are stricter than the law, which is the point of this article: legal and permitted-by-your-provider are separate tests. You must pass both.

Can I just run my own mail server instead?

You can, and no AUP violation notice will arrive. Provisioning and maintenance are tractable if you already handle your own server setup and deployments. Reputation is not: a fresh IP with no sending history is treated with deep suspicion by Gmail and Microsoft, and you start from zero on an asset Workspace mailboxes hand you free. Rarely worth it.

Do I need a separate SMTP provider if I use a cold email platform?

Depends on the platform. Tools that send through their own shared pool hand you that pool's reputation and their AUP with it. Tools that connect to mailboxes you own leave you in control of both, as we covered in using your own SMTP for cold email.

Where ColdMailer fits

ColdMailer is built for the architecture above. You connect the SMTP accounts you already own, the Workspace and Microsoft 365 mailboxes your team already pays for, and ColdMailer sends through them. No shared pool whose reputation you inherit, no third-party AUP gating your outreach.

Connect as many as you need. ColdMailer rotates sends across every connected mailbox, paces them so no account spikes, and warms each domain in the background. You get the mailbox count your volume target actually requires, not the one your plan tier allows: unlimited SMTP accounts on Pro and Enterprise. Auditing what you have? Start with our email deliverability tools and check your SPF, DKIM and DMARC.