What is an SMTP gateway?

An SMTP gateway is a mail server positioned between mail sources and destinations, providing relay, filtering, security, or routing functions. Outbound SMTP gateways accept mail from your apps and deliver it to recipients (e.g., SMTP2GO, AWS SES). Inbound SMTP gateways filter mail before it reaches your mailbox provider (e.g., Proofpoint, Mimecast). Some gateways do both.

When do I need an SMTP gateway?

You need an outbound SMTP gateway when: your apps need to send mail but can't authenticate to mailbox providers, you want unified outbound logging across multiple apps, or you need a single point of egress for compliance. You need an inbound SMTP gateway when: you require advanced spam/malware filtering beyond your mailbox provider's defaults, or need DLP (data loss prevention) on incoming mail.

What's the difference between SMTP gateway and SMTP relay?

Overlapping terms. 'SMTP relay' specifically means an intermediary server that forwards mail (typically outbound) without filtering. 'SMTP gateway' is broader — includes relay functionality plus filtering, security, routing, or compliance features. Most outbound SMTP relays are also called SMTP gateways; inbound mail security platforms are almost always called gateways.

What's an unlimited SMTP email hosting service?

'Unlimited SMTP' marketing usually means high volume tiers, not actually unlimited. Real high-volume SMTP gateways (SMTP2GO, SMTP.com, AWS SES) have generous limits but enforce rate limiting, IP reputation management, and bounce thresholds. True unlimited SMTP at low cost doesn't exist — providers must protect their IPs from abuse.

How do I set up an SMTP gateway for my apps?

Pick a provider (SMTP2GO, SMTP.com, SendGrid, AWS SES). Verify your sending domain (SPF, DKIM). Get SMTP credentials from your provider dashboard. Point your apps to the gateway's SMTP hostname (e.g., mail.smtp2go.com:587) with your credentials. The gateway accepts and forwards mail using its own reputation and infrastructure.

SMTP Gateway Explained: Architecture and Use Cases

SMTP Gateway: The Three Types

Outbound SMTP Gateway (Send Relay)

Sits between your apps and the internet. Apps submit mail to the gateway; the gateway delivers to recipients. Examples: SMTP2GO, SMTP.com, AWS SES, SendGrid SMTP endpoint.

Why use one:

Apps can't authenticate to mailbox providers
Centralized logging across multiple sending sources
Better deliverability than direct sending
Bypass cloud provider port 25 blocks

Inbound SMTP Gateway (Security/Filtering)

Sits in front of your mailbox provider. Receives inbound mail, filters for spam/malware/compliance, then forwards to your mailboxes. Examples: Proofpoint, Mimecast, Barracuda, Cisco IronPort.

Why use one:

Better filtering than mailbox provider defaults
DLP (data loss prevention) policies
Encryption gateway functions
Compliance archiving

Bidirectional Gateway (Full Mail Server)

Handles both inbound and outbound. Self-hosted mail servers (Postfix, Mailcow, Postal) are bidirectional gateways.

Outbound SMTP Gateway Configuration

For most apps, you configure an outbound SMTP gateway like any SMTP server:

Server: provider's gateway hostname
Port: 587 (STARTTLS) or 465 (SSL/TLS)
Authentication: yes (SMTP credentials or API key)
TLS: required

Common outbound SMTP gateway providers:

Provider	Hostname	Notes
SMTP2GO	mail.smtp2go.com	Affordable, easy setup
SMTP.com	send.smtp.com	One of the original SMTP services
SendGrid	smtp.sendgrid.net	Full-featured
Mailgun	smtp.mailgun.org	Developer-focused
AWS SES	email-smtp.{region}.amazonaws.com	Cheapest at scale
DuoCircle	smtp.duocircle.com	Multi-purpose

Inbound SMTP Gateway Setup

Inbound gateways receive mail at your domain's MX records, filter it, then forward to your mailbox provider (Office 365, Google Workspace, etc.). Configuration:

Sign up with the gateway provider (Proofpoint, Mimecast, etc.)
Provider gives you MX records pointing to their infrastructure
Update your DNS MX records to point to the gateway
Configure the gateway to forward filtered mail to your real mailbox provider
Test by sending mail and verifying it routes through the gateway

The gateway becomes your authoritative inbound mail receiver; your mailbox provider receives filtered mail from the gateway.

Use Cases by Organization Type

SaaS apps

Outbound SMTP gateway for transactional/marketing email. Most use SendGrid, Mailgun, Postmark, AWS SES, or Resend.

Multi-tenant agency

Outbound SMTP gateway centralizes sending across many client domains. Self-hosted gateway (Postal, Mailcow) or per-client ESP setup.

Enterprise (1K+ employees)

Often uses both: inbound gateway (Proofpoint, Mimecast) for security + outbound gateway for application sending.

Compliance-heavy industries

Healthcare, finance, legal often require gateways with DLP, encryption, and archiving (Proofpoint Email Security, Mimecast).

Cost Comparison

Outbound (per message)

AWS SES: $0.10/1K messages — cheapest
SMTP2GO: $0.50-$3/1K messages depending on tier
SendGrid: $1-$5/1K messages
Mailgun: $0.80-$3.50/1K messages

Inbound (per user/month)

Proofpoint Essentials: $4-15/user/month
Mimecast Email Security: $5-20/user/month
Barracuda Email Gateway Defense: $3-10/user/month

Inbound gateways are priced per user; outbound by message volume.

Common SMTP Gateway Problems

"Gateway accepts mail but doesn't deliver"

Check the gateway's queue and bounce logs. Common causes: recipient server rejecting, IP reputation issues, or DKIM signing not configured.

"Inbound gateway dropping legitimate mail"

Adjust filtering thresholds or whitelist specific senders. Aggressive filtering catches false positives.

"MX records point to gateway but mail bypassing it"

DNS propagation incomplete, or another MX record (lower priority) is still active. Verify with dig MX yourdomain.com.

"Authentication failures with the gateway"

Verify SMTP credentials, check that your sending IP is allowlisted (some gateways IP-restrict), and confirm TLS is enabled.

Self-Hosted SMTP Gateway

For organizations that want full control:

Postfix — open source MTA, can be configured as outbound relay or inbound filter
Mailcow — Docker-based full mail server
Postal — open source Postmark alternative
Stalwart — modern Rust-based mail server

See Mailcow setup guide for a full self-hosted gateway walkthrough.

Practitioner note: "Unlimited SMTP email hosting" is a phrase that should make you suspicious. SMTP infrastructure has real costs — IP reputation, bandwidth, monitoring. Anyone offering truly unlimited at low cost is either lying about volume capability or running an abuse-prone shared pool. Pay for real SMTP infrastructure.

Practitioner note: The most common SMTP gateway misconfiguration: company sets up an outbound gateway for "centralized logging" but doesn't configure their apps to actually use it. Apps continue sending direct, and the gateway sees nothing. Audit your apps' actual SMTP configuration after deploying a gateway.

Practitioner note: Inbound SMTP gateways (Proofpoint, Mimecast) provide better filtering than mailbox provider defaults — but they're an extra failure point. Outage at the gateway = your mail flow stops. Plan for failure with secondary MX records and monitoring.

If you're architecting an SMTP gateway for application sending or inbound security, book a consultation. I configure outbound SMTP gateways and inbound security gateways for SaaS and enterprise clients regularly.

Sources

v1.0 · May 2026