SendAs Relay

Guides › Cloudflare Email Routing: Send From Gmail in 2027

Cloudflare Email Routing: Send From Gmail in 2027

Updated 2026-10-03 · by Adam Hale

Cloudflare Email Routing keeps forwarding your domain's mail into Gmail after January 2027. The usual way to reply as you@yourdomain.com, adding it under Gmail's "Send mail as" through smtp.gmail.com, stops working. Email Routing has never sent mail itself, so to send from Gmail in 2027 you need an outbound SMTP service for your domain plus a way to use it. The same applies to ImprovMX free users.

What changes for Cloudflare Email Routing users

ImprovMX send as Gmail alternative

ImprovMX users are in the same spot:

ImprovMX's own guide to Gmail Send-as alternatives says "every option here sends through ImprovMX SMTP, which requires a paid plan". It suggests Thunderbird, Apple Mail, Fastmail or Zoho. If you already pay for ImprovMX, its SMTP server (smtp.improvmx.com, port 587 or 465) is the natural outbound choice.

Cloudflare Email Routing send from Gmail in 2027: outbound options

Outbound service Cost Limit Keep Email Routing?
Brevo Free 300/day Yes
SMTP2GO Free 1,000/month, 200/day Yes
Mailjet Free 6,000/month, 200/day Yes
Resend Free 3,000/month, 100/day Yes
Mailgun Free 100/day, 1 domain Yes
Cloudflare Email Sending Workers Paid, $5/mo 3,000/month included Yes
ImprovMX Light (if you switch forwarders) $50/yr 750/month No, ImprovMX forwards instead
Forward Email Enhanced $3/mo Reputation-based No, Forward Email forwards instead
Purelymail / Migadu Micro $10 / $19 per year Migadu: 20 outbound/day No, MX moves to a real mailbox
Google Workspace Business Starter $7/user/mo, annual Native No, MX moves to Google

(our estimate) The free senders are built for transactional and marketing mail. Nothing we read bans low-volume personal replies, but spam complaints can get an account suspended. The free SMTP guide covers the trade-offs in detail.

DNS: adding a sender next to Email Routing

Your MX records stay pointed at Cloudflare; the outbound service doesn't need MX. What you add:

  1. SPF. A domain may have only one SPF record, and Cloudflare warns that multiple SPF records break Email Routing. Email Routing already created v=spf1 include:_spf.mx.cloudflare.net ~all when you enabled it. Add the sender's include: to that same record instead of creating a second one, for example v=spf1 include:_spf.mx.cloudflare.net include:<your-sender> ~all.
  2. DKIM. Add the CNAME or TXT records the sender gives you, then click verify in its dashboard.
  3. DMARC. If you don't have one, start with v=DMARC1; p=none; rua=mailto:you@yourdomain.com. Tighten it once reports show your mail passing.

Send a test to a Gmail address you don't own and check "Show original". SPF, DKIM and DMARC should all say PASS.

Where to write from

Don't confuse the two Cloudflare products

SendAs Relay's relay also runs on Cloudflare, but on Cloudflare Workers, a separate product from Email Routing. It doesn't replace Email Routing, and you don't need Email Routing to use it. If you already manage your domain in Cloudflare, you can deploy your own copy of the relay in that same free account (self-host guide).

A note on Google's warning

Google cautions that "third-party tools or browser extensions that offer to replicate 'Send as'" often need your credentials. For a Cloudflare-routed domain, the credential is a sending key from Brevo, SMTP2GO or similar. It's a dedicated SMTP login you can revoke on its own, which is less sensitive than a mailbox password. Still, keep it somewhere you control.

How SendAs Relay fits

Not the right fit if you use Chrome, need to send from your phone, or would rather pay for a native setup (Workspace). Free covers one address; see pricing.

Sources