SMTP relay sends email through an intermediary SMTP server (a 'relay') instead of directly from your application or mail server. The relay handles delivery to recipient servers, manages reputation, retries failures, and provides logging. Common use cases: apps that send mail without their own infrastructure, high-volume sending, transactional notifications, and bypassing port 25 blocks.

What's the best SMTP relay service?

Best SMTP relay depends on use case. Transactional: Postmark or Resend (best deliverability). Marketing + transactional bundled: SendGrid. Cost-optimized high volume: AWS SES. Developer-friendly: Mailgun. For Google Workspace customers: smtp-relay.gmail.com. For Office 365 customers: Microsoft connectors. No single 'best' — fit depends on volume, integration, and budget.

How does an SMTP relay server work?

Your app connects to the relay server via SMTP (typically smtp.provider.com on port 587 with STARTTLS or 465 with SSL/TLS), authenticates, and submits a message. The relay accepts the message, queues it, and delivers it to the recipient's mail server. The relay handles MX lookups, TLS negotiation, retries on temporary failures, and bounce handling.

Do I need an SMTP relay if I have Gmail or Outlook SMTP?

Maybe. Gmail SMTP (smtp.gmail.com) and Outlook SMTP (smtp-mail.outlook.com / smtp.office365.com) work for low-volume sending from individual mailboxes. For higher volume, programmatic sending, or transactional email at scale, dedicated SMTP relay services provide better deliverability, monitoring, and limits. Crossover point: roughly 500-2,000 messages/day.

Is SMTP relay different from an ESP?

Mostly the same thing in 2026. An ESP (email service provider) typically offers SMTP relay PLUS additional features (template management, list management, analytics, marketing tools). 'SMTP relay' usually refers to the bare-bones send-an-email function. Most ESPs (SendGrid, Mailgun, Postmark) offer both API and SMTP relay interfaces.

SMTP Relay: What It Is, How It Works, and Best Providers

What SMTP Relay Solves

Sending email directly from your application or mail server requires:

A static IP address with reverse DNS (PTR record)
Port 25 outbound access (often blocked by ISPs/cloud providers)
Authentication infrastructure (SPF, DKIM, DMARC)
Reputation building (warmup process)
Bounce handling, retry logic, queue management
Monitoring across major mailbox providers

SMTP relay services provide all of this. Your app submits messages; the relay handles delivery.

The Major SMTP Relay Providers

Transactional / Developer-Friendly

Postmark — Best for transactional. Excellent deliverability, clear pricing, simple SMTP and API.
Resend — Modern developer-focused. Generous free tier.
SendGrid — Most-used. Transactional + marketing. Free tier removed in 2025.
Mailgun — Developer-focused, good API, flexible.
AWS SES — Cheapest at scale. Requires more setup. No marketing features.

Embedded / Workspace

smtp-relay.gmail.com — Google Workspace SMTP relay service. Up to 10,000 messages/day per user.
smtp.office365.com — Microsoft 365 SMTP. Up to 10,000 messages/day per mailbox via SMTP AUTH.

Bulk Email / Marketing

Klaviyo — Ecommerce marketing.
Mailchimp — General marketing.
Most marketing platforms offer SMTP relay alongside their main interface.

How SMTP Relay Works (Technical)

When your app sends through an SMTP relay:

TCP connection to smtp.provider.com:587 (or :465 for SSL/TLS)
STARTTLS negotiation to encrypt the connection
EHLO — your app identifies itself
AUTH — your app authenticates (typically PLAIN or LOGIN with API key)
MAIL FROM / RCPT TO / DATA — your app submits the message
Relay queues the message and accepts (or rejects) with an SMTP response code
Relay delivers to the recipient's mail server (MX lookup → TCP → STARTTLS → SMTP)
Relay handles retries, bounces, and reports back via webhooks or polling

The smtp server relay gmail (smtp-relay.gmail.com) works the same way but with Gmail's infrastructure handling delivery.

When to Use SMTP Relay

Always use when:

Sending more than ~500 messages/day
Sending transactional email (password resets, receipts, notifications)
Sending from cloud infrastructure that blocks port 25
Need deliverability monitoring and analytics
Building any production application that sends email

Direct send may work when:

Sending only to your own organization's users
Have proper IP, PTR, and authentication
Single-digit messages per day

In practice, almost every application benefits from an SMTP relay.

SMTP Authentication for Gmail and Outlook

When you're using Gmail or Outlook SMTP for relay scenarios, authentication options:

Gmail SMTP (smtp.gmail.com): app password (most common) or OAuth2
Gmail SMTP relay (smtp-relay.gmail.com): IP-based + SMTP AUTH
Microsoft 365 SMTP (smtp.office365.com): app password (legacy) or OAuth2
Microsoft 365 relay (via connector): IP-based, no per-message auth

For SMTP server settings outlook, see Outlook SMTP setup. For Gmail SMTP authentication: app passwords are still supported but Google is pushing OAuth2.

SMTP Relay Pricing (2026 Snapshot)

Provider	Free Tier	100K/mo	1M/mo
Postmark	100 msgs (one-time)	$15	$135
Resend	3,000/mo	$20	$200
SendGrid	Trial only	$34.95	Custom
Mailgun	Trial only	$75	$450
AWS SES	62,000/mo (from EC2)	$10	$100
Gmail Workspace relay	$6-12/user/mo (Workspace cost)	—	—
Microsoft 365 SMTP	$6-22/user/mo (M365 cost)	—	—

Compare based on volume and what features you need beyond pure relay.

Common SMTP Relay Issues

"Authentication failed"

Wrong credentials (API key formatting often the issue). For most providers, username is apikey and password is the actual API key.

"Sender domain not verified"

Provider requires you to verify the From: domain before sending. Add SPF and DKIM as instructed in the provider dashboard.

"Rate limit exceeded"

You've hit per-second or per-minute limits. Implement client-side throttling or upgrade your plan.

"Message rejected: spam-like content"

Provider's pre-send filtering caught your message. Check content for spam triggers. Some providers (Postmark) strictly enforce transactional-only sending and reject promotional content.

"Reverse DNS check failed"

Mostly for direct send — not usually an issue with relay services since you use their IPs. If running your own relay, ensure your IP has a valid PTR record.

Practitioner note: The fastest path from "I need to send email from my app" to working production sending: use Resend or Postmark. Sign up, verify domain, add DKIM, send. Done in 30 minutes. Save the cost optimization (AWS SES) and feature shopping (SendGrid) for after you've shipped.

Practitioner note: For GoHighLevel agencies asking about SMTP for GoHighLevel, Mailgun is the most battle-tested integration. SendGrid and AWS SES also work. The smtp-relay.gmail.com option doesn't fit GoHighLevel's architecture well — stick with dedicated relay services.

Practitioner note: SMTP relay providers should be treated as commodity infrastructure for the actual sending function. The differences that matter: pricing model, deliverability reputation, ease of integration, and support quality. The actual SMTP protocol is identical across providers.

If you need help choosing the right SMTP relay for your sending volume, use case, and integration requirements, book a consultation. I configure SMTP infrastructure for SaaS, ecommerce, and agency clients regularly.

Sources

RFC 5321: SMTP specification
Google: SMTP relay service for Workspace
Microsoft: SMTP relay configuration
Mailgun: Understanding SMTP

v1.0 · May 2026