
The SMTP relay vs SMTP server question is partly about words: every SMTP server can relay mail, and a relay service is just an SMTP server you send through rather than one you run. The practical difference is responsibility. Run your own SMTP server and you own delivery, IP reputation and security. Use a relay and another provider's servers carry your mail, with their limits and rules. This guide explains both, how Google Workspace's SMTP relay service works and what it's designed for, why open relays are dangerous, and which setup suits cold email.
SMTP Relay vs SMTP Server: The Short Answer
SMTP server (self-run) | SMTP relay (service) | |
|---|---|---|
What it is | Software you operate that sends and receives mail | Someone else's SMTP servers that forward your mail |
Delivers mail to recipients' servers | Itself, from your IPs | From the relay provider's IPs |
Reputation | Yours (IP and domain) | Provider's IPs + your domain |
Setup effort | High | Lower |
Typical use | Full control, high volume | Apps, devices, transactional mail |
How an SMTP Server Works
An SMTP server (mail transfer agent) accepts mail from your apps or users on submission ports (587 or 465), looks up the recipient domain's MX record, and connects to that server on port 25 to deliver. You manage the software, IPs, rDNS, authentication and security — see SMTP server setup and SMTP ports.
How an SMTP Relay Works
With a relay, your app or server hands mail to a provider's SMTP endpoint, which then delivers it. Google Workspace's SMTP relay service is an example: it routes outgoing mail from on-premise servers, devices and apps through Google, connects on smtp-relay.gmail.com using port 25, 465 or 587, and authenticates by IP address or SMTP authentication. Google documents separate relay limits — for example, each user can relay to up to 10,000 recipients per day — and says the relay is intended for devices and applications generating outbound mail.
Google also recommends SMTP relay for sending from printers, scanners and apps (Google guide).
The Open Relay Problem
⚠️ Never run an open relay
A server that relays mail for anyone without authentication is quickly found and abused by spammers, which gets its IP blocklisted. Always require authentication or restrict relaying to known IPs.
Relay denials ("relay access denied") are a common cause of 5.7.1 errors — see SMTP 550 5.7.1.
Side-by-Side Comparison
Factor | Own SMTP server | Relay service |
|---|---|---|
Control | Full | Limited to provider settings |
Deliverability ownership | All yours | Shared with provider |
Maintenance | Ongoing | Provider's job |
Limits | Your IPs' reputation | Provider's quotas and policies |
Port 25 blocks | Affects you directly | Avoided via 465/587 to relay |
Cost | Hosting + time | Subscription or included |
Which Should Cold Emailers Use?
Neither, usually. Most cold email runs from individual mailboxes — Google Workspace or Microsoft 365 inboxes on secondary domains, connected to a sequencer by OAuth — rather than through a relay or a self-run server. Relays like Google's are designed for apps and devices, and marketing or transactional relay services typically have their own acceptable-use rules. If you need dedicated IPs, use a provider built for outreach (dedicated IP email providers) or weigh self-hosting carefully.
Decision Guide
Need | Choose |
|---|---|
Cold outreach at scale | Mainstream inboxes on secondary domains |
App notifications and alerts | Relay service |
Printer / scanner email | Google Workspace SMTP relay or Gmail SMTP |
Full control, high volume, expert team | Own SMTP server or dedicated IP provider |
Deliverability Doesn't Change With the Pipe
Server or relay, the same basics apply:
🔐Authenticate every domain
SPF, DKIM and DMARC aligned (authentication guide, Google Workspace setup, Microsoft 365 setup).
🌐Use secondary sending domains
Keep your main domain out of cold outreach (domain setup, domain risks).
🔥Warm or start pre-warmed
Ramp gradually (warm-up guide) or use pre-warmed inboxes (pre-warmed vs fresh).
📉Keep per-inbox volume low
Scale with inboxes, not volume (safe sending limits, inbox sizing).
✅Verify every list
Bounces damage reputation fast (verification tools, list cleaning).
📊Monitor weekly
Spam rate, bounces and blocklists (Postmaster setup, blacklist tools).
Neither Relay Nor Server — Just Inboxes
LiteMail | Mailboxes built for outreach
Fresh from $2.50/inbox
Official Google Workspace and Microsoft 365 inboxes for outreach
LiteMail provisions official Google Workspace and Microsoft 365 inboxes on secondary domains, configures SPF, DKIM and DMARC automatically and lists dedicated US and EU IPs. Inboxes export by OAuth to Instantly, Smartlead, Lemlist and Pipl.ai, so there's no relay or server to configure.
Strengths | Keep in mind |
|
|
Explore pricing, the inbox calculator, infrastructure, bulk inboxes and setups for agencies, SaaS and recruiters. Comparing providers? See Google Workspace vs Microsoft 365.
Use real inboxes for outreach — not relays. Get Pre-Warmed Inboxes →
Frequently Asked Questions
What's the difference between an SMTP relay and an SMTP server?
An SMTP server is software that sends and receives mail; a relay is an SMTP server you send through that forwards your mail.
Is every SMTP server a relay?
Every SMTP server can relay, but it should only relay for authenticated or authorised senders.
What is Google Workspace SMTP relay?
A Google service that routes outgoing mail from on-premise servers, devices and apps through Google's servers.
What ports does Google's SMTP relay use?
Google documents smtp-relay.gmail.com on port 25, 465 or 587.
What is an open relay?
A server that relays mail for anyone without authentication; it's quickly abused and blocklisted.
Should I use an SMTP relay for cold email?
Usually not; most cold email runs from individual mailboxes connected to a sequencer.
Do relays avoid port 25 blocks?
Yes, by submitting to the relay on 465 or 587.
Which is cheaper?
Self-run servers cost less in fees but more in time and risk.
Skip the Plumbing, Send From Real Inboxes
Official Google Workspace and Microsoft 365 inboxes with automated SPF, DKIM and DMARC on dedicated US and EU IPs.
Automated DNS · Pre-warmed options · OAuth export
About LiteMail — LiteMail provides fresh and pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated SPF, DKIM and DMARC setup, dedicated US and EU IPs, separate client workspaces and one-click OAuth export to Instantly, Smartlead, Lemlist and other sending tools. View pre-warmed inbox plans →
Related reading: Smartlead Setup · Google Workspace + Smartlead · Microsoft 365 + Smartlead · SDR Infrastructure · Domain Setup · Bulk Email Inboxes


