SMTP vs Gmail for cold email

Authentication and ownership

With SMTP on your own domain you publish SPF, DKIM and DMARC yourself, so alignment is under your control and a block does not affect your personal mailbox. With Gmail, Google authenticates its own domain; you inherit its reputation and cannot change the records that decide it.

Ownership also affects continuity. A domain you control can move between providers. A Gmail account is a single point of failure: if it is restricted, the outreach stops and the sent history goes with it.

• Your domain: you own SPF, DKIM, DMARC and the sending history.
• Gmail: Google owns the authentication, you own the account risk.
• Cold outreach on a personal Gmail mixes reputation with everything else.

If you choose your own domain, the record setup is in SPF, DKIM and DMARC setup.

Limits and pacing

SMTP sending is limited by your provider's daily cap and by the interval you choose. At thirty to sixty seconds between messages, a mailbox can sustain hundreds to low thousands per day, and you can add mailboxes for more.

Gmail applies its own sending limits and terms for bulk mail. Exceeding them affects the account, not just the campaign, and the limits are not designed for cold outreach at volume. A Gmail address is a good reply-to address; it is a poor campaign engine.

Cost, honestly

SMTP costs money: a domain, mailboxes, and sometimes a sending platform. Gmail is free at the mailbox level, which is why it looks cheaper. The comparison changes when a restricted account costs you a month of pipeline, or when a complaint against your personal mailbox affects client correspondence.

The published plans on this site start at $18 a month for one SMTP mailbox, 2,000 emails and 1,000 contacts, and rise to $1,000 a month for ten mailboxes and 500,000 emails. That is the cost of the managed route, stated plainly; a Gmail account plus a separate domain costs less in cash and more in risk.

• Starter: $18, one mailbox, 2,000 emails, 1,000 contacts.
• Growth: $38, one mailbox, 10,000 emails, 10,000 contacts.
• Business: $198, two mailboxes, 100,000 emails, 100,000 contacts.
• Enterprise: $1,000, ten mailboxes, 500,000 emails, 500,000 contacts.

Every tier and allowance is listed on published plans and prices, with no hidden sending fee.

A worked migration

A founder sent 150 messages a day from a personal Gmail account and got a temporary restriction after a complaint. The campaign stopped, and so did ordinary correspondence. They moved outreach to a subdomain with its own SMTP mailbox, left the Gmail address as the reply-to, and resumed at 80 messages a day.

Replies still arrived in the Gmail inbox, which is what they wanted. Complaints now affected only the outreach domain. The cost was a domain and a mailbox; the benefit was that a bad week could no longer lock them out of their own email.

If you need mailboxes on your own domain, SMTP accounts provides them ready for outreach.

What to check before moving sending providers

Moving the sending route is a DNS change with a reputation consequence. Before the switch, confirm the new provider supports the authentication you need, that you can publish its DKIM selector, and that the return path will align with your From domain. A provider that cannot align will pass SPF and fail DMARC.

Plan the warm-up as part of the move. A new mailbox, even on a familiar domain, starts without a sending history. Keep the old route available for replies while the new one warms, and do not run the same campaign through both.

Finally, check where replies land. Changing the sending mailbox should not change the inbox your team reads, or replies will be split across two places and half of them will be missed.

• DKIM selector and return-path alignment confirmed first.
• Warm the new mailbox before routing campaign volume to it.
• Keep reply routing stable across the move.
• Document the sending setup where the team can find it: domain, provider, selector, reply-to and who owns the DNS. The next person to change a record should not have to reverse-engineer it.
• Keep the reply-to address independent of the sending provider. When the provider changes, the reply path should not, or a month of conversations ends up split between two inboxes and the team starts missing answers that look like silence.
• Test the new route with real replies before moving a campaign to it. Send a small batch, answer the responses from the intended inbox, and confirm that threading works. A route that sends correctly but breaks reply threading costs more time than a slower warm-up would have.

SMTP on your domain and a Gmail mailbox compared

A common pattern is SMTP for sending and Gmail for reading replies.

Frequently asked questions