Updated 22 October 2026: Google has added "Send mail as" for non-Google addresses to the January 2027 removal. This guide now covers both halves.
The short version: Google is retiring three things in Gmail: "Check mail from other accounts" (POP import), Gmailify, and "Send mail as" for non-Google addresses. New users already can't turn on POP import, Gmail may refuse new "Send mail as" setups, and existing users lose all three in January 2027 (Google's announcement). If your custom-domain email flows into a free Gmail inbox, via Cloudflare Email Routing, ImprovMX, an alias service, or Gmail's own POP fetcher, and you reply from Gmail as your domain, both the receiving and the sending side of that setup stop working then. Here's exactly what's changing, how to tell if you're affected, and your realistic options.
What exactly is Google removing?
Three consumer-Gmail features:
- "Check mail from other accounts". Gmail's built-in POP client, which logs into another mailbox on a schedule and pulls its mail into your Gmail inbox.
- Gmailify. The linked-account mode that gave non-Gmail addresses Gmail's spam filtering and inbox features.
- "Send mail as" for non-Google addresses. The setting that lets you write from your Gmail account but send as
you@yourdomain.com(or a Yahoo or Outlook address). Google says you "will no longer be able to send mail from third-party email accounts in Gmail on the web or in the Gmail mobile apps."
The timeline, from Google's two help pages (POP and Gmailify, Send as):
- POP import and Gmailify: no new users after the first quarter of 2026.
- Send as: announced in Q3 2026. Existing setups keep working through the transition, but Gmail may already refuse new ones.
- January 2027: all three are removed for existing users.
What isn't changing: sending as another Gmail address or a Google Workspace alias, mail forwarded to Gmail, and non-Google accounts you add directly in the Gmail mobile app. Google Workspace is a separate product and unaffected.
Am I affected? A 60-second check
Open Gmail on the web, then Settings → See all settings → Accounts and Import. You're affected if either of these lists something:
- "Check mail from other accounts" shows a POP account. Gmail pulls that mail in, and the pull stops in January 2027.
- "Send mail as" shows an address that isn't
@gmail.com, such asyou@yourdomain.com. Replying as that address from Gmail stops in January 2027.
A forwarder on its own isn't affected. If Cloudflare Email Routing, ImprovMX, your registrar's free forwarding, or an alias service (addy.io, SimpleLogin, Firefox Relay) pushes your domain's mail to your @gmail.com address, that mail will keep arriving. But almost everyone who set that up added your domain under "Send mail as" so they could reply from it, and that is the half that ends. What's left afterwards is a receive-only copy of your domain's mail: you can read it in Gmail, but every reply goes out from @gmail.com. Forwarded mail also keeps its old weakness: forwarding breaks SPF alignment by design, so more of it lands in spam.
If your domain's mail lands in a paid Google Workspace account with your domain connected properly: you're fine. This page isn't about you.
Your options, honestly compared
Option 1: Pay Google. Move the domain onto Workspace
The path of least visual change: your inbox stays Gmail. Workspace Business Starter runs about $7/user/month (≈$84/year) with your domain connected as a first-class citizen. Real MX records, proper authentication, no forwarding tricks.
Right choice if you live in Gmail's interface and one address per person is your world. The trade-offs: it's per-user pricing (several family addresses multiply it), and your email identity remains inside Google's account system. The lock-in that many custom-domain owners were specifically trying to escape.
Option 2: A real mailbox on your domain (our corner of the world, so judge accordingly)
Point your domain's MX records at a mailbox provider: mail is received, stored, filtered and sent from infrastructure built for it, and you read it in any IMAP app or webmail. Typical cost across the market: $10–90/year depending on tier. A full comparison and a choosing checklist are in our complete guide to email on your own domain.
This is the structurally honest version of what the forwarder-plus-Gmail stack was imitating: one real inbox for your domain (or several domains, some providers, ours included, land any number of them in one mailbox), authentication that actually aligns, and portability. Your mail exports over IMAP and your MX can point elsewhere whenever you choose.
The trade-off is equally honest: it's not Gmail's interface, and if you've got fifteen years of muscle memory there, that's a real switching cost. (Google says the Gmail mobile app will keep supporting non-Google accounts you add directly, so on a phone you can read and send from a real mailbox over IMAP, if your provider supports it. Gmail on the web won't.)
Option 3: Keep forwarding, read in a separate inbox
Do nothing except stop expecting one inbox: your forwarder keeps pushing mail to Gmail (or anywhere), and you accept that you can no longer reply from your domain in Gmail. Zero cost, real degradation. Every reply from the wrong address slowly leaks your @gmail.com into conversations you wanted on your domain.
Reasonable for low-stakes hobby domains. Not for an address you give to humans.
What about self-hosting?
A legitimate fourth path for the technically enthusiastic. And a genuinely demanding one (port 25 access, reverse DNS, IP warmup, permanent blocklist vigilance). We wrote up what it actually involves in the self-hosting section of the main guide. If the list there reads like fun, enjoy; if not, options 1–2 exist.
If you're moving: do it in this order
The full playbook is in the migration section of the main guide; the Gmail-specific shape of it:
- Pick the destination (Workspace or a mailbox host) and create the account for your domain before touching anything.
- Export your Gmail history, Google Takeout gives you everything as MBOX, or let your new provider's IMAP import pull straight from Gmail (enable IMAP in Gmail settings first; imports of large mailboxes take hours, not minutes, start early).
- Switch your domain's records (MX/SPF/DKIM/DMARC) to the new provider. Or, if you were POP-fetching from some other mailbox all along, simply repoint your reading habit; the mailbox was already there.
- Update the address on accounts that matter. Anywhere that has your
@gmail.comas the login or recovery address is a lock-in you can now remove at leisure. - Keep the Gmail account. It costs nothing, it holds years of history, and dozens of forgotten services still know it. Just stop treating it as home.
Don't wait for December 2026: imports are slow, DNS mistakes want calendar room, and nothing about this gets easier closer to the deadline.
Questions we keep hearing
Is Google shutting down free Gmail?
No. Only POP import, Gmailify and "Send mail as" for non-Google addresses are being retired. Your @gmail.com address and inbox continue as before.
Will mail forwarded to my Gmail stop arriving in January 2027? No. Plain forwarding keeps working. What ends is Gmail fetching mail itself and sending as your domain, and with them the tidy unified setup. Forwarding-only into Gmail also remains subject to forwarding's structural problems (broken SPF alignment, occasional spam-foldering of legitimate forwarded mail).
Can I still send as my domain from Gmail after the change? Not from a free Gmail account. From January 2027, Google removes "Send mail as" for non-Google addresses on the web and in the Gmail apps. The ways to keep sending as your domain: move the domain onto Google Workspace, where "Send as" is unaffected, or use a real mailbox for your domain (option 2) in its own webmail, a desktop app, or the Gmail mobile app.
My "Send mail as" still works today. Am I fine? Until January 2027. Google says existing setups keep working through the transition, but new ones may already be refused, so if you remove the address or need to set it up again, you might not get it back.
Does this affect Google Workspace? No. Workspace domains, including Workspace "Send as" aliases, are unaffected. This is a consumer-Gmail change.
I use Cloudflare Email Routing / ImprovMX / an alias service. Do those shut down? The services themselves, no. They keep forwarding. The Gmail features that made them feel like a complete mailbox solution, fetching and sending as your domain, are what's going away. Several of these services already document mailbox providers as the recommended destination; forwarding into a real mailbox on your own domain sidesteps the whole issue.
Full context, records explained, provider checklist and costs: Email on Your Own Domain. The Complete 2026 Guide. And if "every domain you own, one real inbox, $29/year" sounds like your shape of solution. That's MailHow.