The short version — Google is retiring Gmail's "Check mail from other accounts" (POP import) and Gmailify. The feature is already closed to new users, and existing users lose it 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 — the unified-inbox setup you built stops working then. Here's exactly what's changing, how to tell if you're affected, and your realistic options.
What exactly is Google removing?
Two related 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.
Per Google's help page: no new users after the first quarter of 2026, and existing users can continue only until January 2027. This affects free consumer Gmail — Google Workspace is a separate product and unaffected.
What Google is not announcing here: the removal of "Send mail as" (using an external SMTP server to send from another address). But read on, because losing the receiving half still breaks the setup most people actually run.
Am I affected? A 60-second check
You're affected if mail to you@yourdomain.com arrives inside a free Gmail inbox, and it gets there because either:
- Gmail pulls it in — Settings → Accounts and Import → "Check mail from other accounts" lists a POP account. That's the feature being removed; the pull stops in January 2027.
- A forwarder pushes it in — Cloudflare Email Routing, ImprovMX, your registrar's free forwarding, or an alias service (addy.io, SimpleLogin, Firefox Relay) forwards your domain's mail to your
@gmail.comaddress.
Case 2 deserves a careful word, because pure forwarding into Gmail is not the feature being switched off — forwarded mail will keep arriving. But most people in case 2 completed the loop with Gmailify or POP-fetch (for spam filtering and clean threading), and replying as your domain relies on "Send mail as" verification flows that these setups made workable. What January 2027 removes is the glue that made a free Gmail account feel like a genuine mailbox for your domain. What's left afterwards is a strictly worse version: forwarded-only inbound with alignment-damaged authentication (forwarding breaks SPF by design), and outbound that depends on finding an SMTP relay to plug into "Send mail as" — which free forwarders don't provide.
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. (You can keep the Gmail app pointed at some providers over IMAP — but check the provider supports it before counting on it.)
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 replying from your domain becomes somewhere between awkward and impossible. 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 the POP-import and Gmailify features 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 with it 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? "Send mail as" with an external SMTP server isn't named in this removal. But it requires an actual SMTP service that will relay for your domain — which a free forwarder isn't. In practice: if you have a real mailbox somewhere that provides SMTP, you have the option (and at that point you have a real mailbox — read option 2). If your whole stack was free forwarding, you don't.
Does this affect Google Workspace? No. Workspace domains 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 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.