Best SMTP for Cold Email: SMTP Servers and Providers That Allow Cold Outreach
The best SMTP for cold email is not a bulk relay, it is a set of real mailboxes on domains you own at Google Workspace or Microsoft 365. SendGrid, Mailgun, Postmark, SMTP2GO and Elastic Email all require recipient consent in their own published policies, and the AWS Acceptable Use Policy prohibits unsolicited mass email outright, so cold sequences sent through them put the account at risk. Mailbox providers permit ordinary business mail but cap each mailbox hard, which is why volume comes from running several mailboxes rather than one big pipe.
Every policy quote below was read off the provider's own document, not repeated from a roundup
Last updated July 2026
Cold email cost calculator
Where the money goes
| Line item | Qty | Per month |
|---|---|---|
Free tool. Nothing you enter is stored or sent anywhere.
What actually makes an SMTP setup work for cold email
Authentication on every sending domain
SPF, DKIM and DMARC are not optional any more. Google requires all three from bulk senders, and mailbox providers increasingly treat an unauthenticated domain as unsigned mail. Set them up before the first send, not after the first bounce report.
Separate domains from your primary
Send from a secondary domain that resembles your brand, never the domain your invoices and contracts run on. If a sending domain gets burned you retire it and keep the business running.
Several mailboxes, deliberately under-used
Volume comes from mailbox count, not from pushing one mailbox to its cap. Around 30 cold emails per mailbox per day is the steady state that keeps domains healthy, well under the 2,000 a day Google technically allows.
Warm-up before the first campaign
A brand new mailbox with no sending history looks exactly like a throwaway spam account. Two to three weeks of gradually increasing, replied-to mail gives the domain a record to be judged on.
Rotation across the pool
Spreading a campaign across every connected mailbox keeps each one inside a normal human sending pattern and stops a single reputation problem taking the whole program down.
A complaint rate you actually watch
Google asks bulk senders to keep spam complaints below 0.30% and recommends staying under 0.10%. That is the number that decides whether you keep landing in the inbox, and it moves with list quality more than with copy.
Bulk relay or real mailbox: the choice that decides everything
The word SMTP covers two very different products, and conflating them is what gets accounts suspended. One is shared infrastructure you rent. The other is a mailbox you own.
| Feature | Real mailboxes (Workspace or M365) | Bulk relay or email API |
|---|---|---|
| Permission model | Ordinary business mail is what the product is for. No opt-in requirement is imposed on you | Consent required by contract, with purchased and scraped lists named as prohibited |
| Sending reputation | Yours alone, tied to your domain. Good behavior compounds into a durable asset | Pooled across thousands of tenants. Another customer's spam run can hurt your delivery |
| Volume ceiling | Hard per mailbox: 2,000 a day at Google, 10,000 recipients a day at Microsoft. Scale by adding mailboxes | Effectively unlimited, which is the whole attraction and also the whole problem |
| What happens when complaints rise | You see it in your own metrics and can slow down before damage spreads | Enforcement is blunt and fast, because one tenant's complaint rate costs everyone on the pool |
| Cost at 10,000 emails a month | About $117 a month for 16 mailboxes across 6 domains, including the domains themselves | A few dollars of send cost, plus the risk of losing the account and the domain reputation with it |
| Right job for it | Cold outreach, sales sequences, recruiting, partnership and investor mail | Password resets, receipts, alerts, and marketing to a list that opted in |
Both products are good at what they were built for. The failure mode is using a transactional relay for outbound prospecting and treating the acceptable use policy as boilerplate.
What each SMTP provider's own policy says about cold email
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. Nothing in this table is inference. Each row quotes the provider's published policy.
Last updated July 25, 2026
| Provider | Built for | What its own policy says | Verdict for cold outreach |
|---|---|---|---|
| Twilio SendGrid | Transactional and opt-in marketing email over an API | "Except for transactional email, affirmative consent is required for all email sent using Twilio SendGrid." Consent cannot be blanket or gathered from a third party, and specifically not from a purchased list, a third party lead generator or an affiliate. | Cold prospects have not given affirmative consent. Not a fit. |
| Mailgun | Developer transactional email | Email, unless transactional, "can only be sent where permission has been expressly obtained", to recipients who granted "clear, explicit and provable consent" through a confirmed opt-in system. "Acquiring or sending to a third-party mailing list is prohibited." | Requires provable opt-in. Scraped or bought lists explicitly out. Not a fit. |
| Amazon SES | High volume application email on AWS | The AWS Acceptable Use Policy prohibits using the services "to distribute, publish, send, or facilitate the sending of unsolicited mass email or other messages, promotions, advertising, or solicitations (or 'spam')." | A cold sequence is, on a plain reading, both unsolicited and mass. High risk. |
| Postmark | Transactional application email with fast delivery | "All email lists contained and/or used with respect to the Service must be permission-based subscriptions. Use of a list that has been purchased or rented from a third party is prohibited." Complaint rate must stay below 1 in 1,000 emails. | Permission-based subscriptions only, plus a contractual 0.1% complaint ceiling. Not a fit. |
| SMTP2GO | Managed SMTP relay | The most explicit of the group: "We forbid the use of the service to send unsolicited mass emails or unsolicited emails of any kind." Lists "must be 100% opt-in", and prohibited sources include purchased lists, addresses scoured from the internet, and marketing leads built via LinkedIn. | Names LinkedIn-sourced lead lists directly. Unambiguously not a fit. |
| Elastic Email | Email API and marketing platform | "Do not send unsolicited email (i.e. 'spam')." Nothing other than transactional messages may go out "unless the recipients have validly consented". "Do not send email to purchased, rented or third-party email lists of any kind." | Valid consent required for anything non-transactional. Not a fit. |
| Google Workspace | Real mailboxes on your own domain | Ordinary business correspondence is exactly what the product is for. The constraint is volume, not permission: 2,000 messages a day per mailbox, 3,000 external recipients a day, and 100 recipients per message over SMTP. | Permitted, and capped per mailbox. The standard base for cold email. |
| Microsoft 365 | Real mailboxes on your own domain | Also built for business correspondence, with a 10,000 recipient daily limit and a rate limit of 30 messages a minute. Microsoft states that Exchange Online "isn't suited to accommodate bulk-mailing scenarios", so treat the cap as a ceiling. | Permitted, and capped per mailbox. A solid alternative to Workspace. |
Swipe the table sideways for more
Policies read July 2026. The SendGrid and Amazon Web Services clauses were re-read at the source on July 25, 2026. Providers revise these documents, so check the current version before you send. Brevo and Mailjet publish anti-spam policies we could not confirm from a primary source, so we make no claim about them.
Run this with ColdMailer
Connect your SMTP, let AI personalize every email, and start landing in the inbox. Your first 100 emails a month are free.
Setting up cold email SMTP that lasts
Buy the sending domains
Register two to six secondary domains close to your brand name. A .com runs about $11 a year at a registrar that includes privacy, so the domain layer is the cheapest part of the whole system.
Create mailboxes and authenticate
Add roughly three mailboxes per domain at Google Workspace or Microsoft 365, then publish SPF, DKIM and DMARC records for each domain before any mail goes out.
Warm every mailbox
Run two to three weeks of warm-up so each mailbox builds a sending history and an engagement record. Skipping this is the single most common reason a technically perfect setup still lands in spam.
Connect them and send through rotation
Point your sending tool at the mailboxes over SMTP, cap each at about 30 cold emails a day, and let the campaign rotate across the pool rather than hammering one inbox.
Can you use SendGrid for cold email?
Not within their rules. SendGrid requires affirmative consent for every non-transactional email, and states that consent cannot come from a purchased list, a lead generator or an affiliate: you have to be the party that obtained it. A cold prospect never gave it. People do try, and accounts do get shut down, usually once complaint volume shows up rather than at signup.
The same reasoning disqualifies Mailgun, Postmark, SMTP2GO and Elastic Email. The technical capability is there in every case. The permission is not. If you want the detail on how a relay differs from a mailbox, we cover it in SMTP relay vs SMTP server for cold email.
Is Amazon SES good for cold email?
SES is excellent infrastructure and very cheap at volume, which is exactly why it comes up. The problem is the AWS Acceptable Use Policy, which prohibits sending "unsolicited mass email". A cold sequence to a prospect list is, on a plain reading, both unsolicited and mass. AWS also reviews sending reputation and can pause an account with little warning.
Treating SES as a loophole because the per-email price is low tends to end with a suspended AWS account, which for most companies is far more expensive than the sending was ever going to be.
What Google Workspace and Microsoft 365 allow
Mailbox providers take the opposite position. They sell you an inbox for ordinary business correspondence, and cold outreach that a human could plausibly have typed sits inside that. What they impose instead is a hard volume cap per mailbox: Google allows 2,000 messages a day and 3,000 external recipients, Microsoft allows 10,000 recipients a day at 30 messages a minute.
Microsoft is explicit that Exchange Online "isn't suited to accommodate bulk-mailing scenarios", which is the right way to read both caps. They are ceilings that describe an unusual day, not targets to plan against. This is the whole reason serious outbound runs on cold email infrastructure made of many modest mailboxes.
How many mailboxes does your volume need?
Work backwards from the send target at about 30 cold emails per mailbox per day, three mailboxes per domain, across 22 business days a month. Ten thousand emails a month is 455 a day, which needs roughly 16 mailboxes spread over 6 domains.
At $7.00 a seat on an annual commitment plus about $11 a year per domain, that lands near $117 a month in infrastructure. Fifty thousand a month needs about 76 mailboxes and 26 domains, near $556 a month, and at that scale infrastructure is roughly 85% of the total bill rather than the software. The calculator at the top of this page runs the arithmetic for any volume.
Why the cheapest SMTP is usually the most expensive
A relay quotes fractions of a cent per email and a mailbox costs $7 a month, so on a spreadsheet the relay wins by an order of magnitude. That comparison leaves out the two costs that actually bite: the account you can lose, and the domain reputation you cannot buy back.
Sending reputation is the only durable asset in outbound. It accrues to a domain over months of ordinary behavior, and it does not transfer. When a shared pool degrades, or an account is suspended, you restart that clock from zero. The $7 mailbox is not a sending cost, it is what a reputation you control costs to rent.
What to look for in a cold email SMTP provider
Once you accept that the answer is real mailboxes, the shortlist is short: Google Workspace and Microsoft 365 cover almost every case, and the choice usually follows whatever the rest of the company already uses. Beyond that, the questions worth asking are about your sending tool, not your mail host.
Does it connect to mailboxes you own over standard SMTP rather than locking you into its own pool? Does it rotate across the pool automatically? Does it cap per mailbox rather than per account? A tool that answers yes to all three lets you keep the reputation you build. Our SMTP email sender connects to any mailbox you already own.
Who this setup is for
Agencies running outbound for several clients
Each client gets its own domains and mailboxes, so one client's complaint rate never touches another's delivery. That separation is impossible on a shared relay where everything shares a pool.
Founders sending their own first campaigns
Two domains and six mailboxes cost under $50 a month and support around 4,000 emails a month, which is more than enough to test a market before hiring anyone.
Sales teams that outgrew one mailbox
Once a rep hits the point where their personal inbox is doing outbound work, splitting onto secondary domains protects the company's primary domain from the consequences.
Recruiters contacting passive candidates
Candidate outreach is exactly the ordinary business correspondence a mailbox provider expects, and exactly the unsolicited mail a transactional relay's policy prohibits.
Common questions about SMTP for cold email
Real mailboxes on domains you own, at Google Workspace or Microsoft 365, sending through a tool that rotates across the pool. Both providers permit ordinary business correspondence and cost about $7.00 a seat on an annual plan. Bulk relays are cheaper per email but require recipient consent in their terms, which cold outreach by definition does not have.
Not within SendGrid's rules. Their policy requires affirmative consent for all non-transactional email and states that consent cannot come from a purchased list, a third party lead generator or an affiliate. Cold prospects have not consented, so cold sequences put the account at risk of suspension even though the platform is technically capable of sending them.
SES is strong, cheap infrastructure, but the AWS Acceptable Use Policy prohibits sending "unsolicited mass email or other messages, promotions, advertising, or solicitations". A cold prospecting sequence is both unsolicited and mass on a plain reading, and AWS can pause accounts over sending reputation. The low per-email price does not offset losing the AWS account.
A relay is shared infrastructure you rent: you hand mail over and it goes out through pooled IPs alongside thousands of other senders. An SMTP server behind a real mailbox is an inbox you own on your own domain, with its own reputation. Relays optimize for throughput, mailboxes optimize for trust, and cold email needs trust.
Google Workspace permits 2,000 messages a day per mailbox and Microsoft 365 permits 10,000 recipients a day, but those are ceilings rather than targets. A healthy cold email program sends about 30 a day per mailbox and scales by adding mailboxes, because sending near the cap from a new domain is the fastest way to land in spam.
No. At cold email volumes a dedicated IP has too little traffic to build a stable reputation, and mailbox providers increasingly judge the sending domain rather than the IP. Dedicated IPs make sense above roughly a million messages a month on a relay, which is a different problem from outbound prospecting.
Free SMTP tiers are transactional relays with the same consent requirements as their paid plans, so the policy problem is unchanged and the sending limits are tighter. The realistic floor for cold email is a paid mailbox at about $7 a month, which buys permission to send ordinary business mail and a reputation that belongs to you.
Yes, on every sending domain, before the first campaign. Google requires SPF, DKIM and DMARC from bulk senders along with one-click unsubscribe, and asks that spam complaints stay below 0.30%, recommending under 0.10%. An unauthenticated sending domain is filtered aggressively regardless of how good the copy is.
Cold email itself is legal in the United States under CAN-SPAM provided you identify yourself, give a real postal address, describe the message honestly and honor opt-outs. What varies is your sending provider's contract. Mailbox providers permit business correspondence, while transactional relays contractually require opt-in, which is a private agreement rather than a law.
Bring your own SMTP and keep the reputation you build
ColdMailer connects to the Google Workspace or Microsoft 365 mailboxes you already own, rotates sends across the whole pool, and personalizes every email with AI. Flat $49 a month, no per-seat or per-mailbox charge.
No credit card · Bring your own SMTP · Cancel anytime