Countdown
January 2027: The Day Gmail Stops Sending as Your Domain
Picture opening Gmail one ordinary morning in January 2027, hitting reply to a client, and watching it go out as the @gmail.com address you buried years ago. That's the quiet failure a clock is now ticking toward. The fix isn't another monthly bill — it's owning the thing that sends your mail, and getting there before the deadline.
For years the trick was simple. You kept your familiar Gmail inbox, added your custom address under "Send mail as," and every reply went out looking like it came from your own domain. Nobody you emailed ever saw a @gmail.com address. It felt like you owned your email. You did not — you were borrowing a feature, and the loan is being called in. This article lays out what the January 2027 horizon actually means, what's confirmed versus expected, who gets hurt, and how to read the credential deprecations that are already landing in your own Google account.
What the deadline actually refers to
The feature on the clock is the one buried in Gmail → Settings → Accounts and Import → "Send mail as." It lets a free Gmail account add an outside address and send from it, routed through an external SMTP server you configured. On the current trajectory, that pathway closes for custom domains on consumer Gmail. In plain terms:
- You'd no longer be able to add a new custom-domain address under "Send mail as."
- Addresses already configured stop sending as your domain — replies fall back to your
@gmail.comidentity, or simply fail. - The outbound SMTP relay that made the whole thing work is no longer honored for these addresses.
Your inbox still receives. The loss is on the sending side — the half that carries your name, your brand, and your reputation into other people's inboxes.
Why Gmail is closing the door
None of this is personal, and none of it is surprising if you've watched the direction of travel. Three forces point the same way.
Deliverability got strict
The whole email industry tightened its rules on who may send as whom. SPF, DKIM, and DMARC — the records that prove a message really came from your domain — are no longer optional. "Send mail as" through a third party is a notoriously leaky setup: messages often arrive stamped "via gmail.com" or land in spam because the signatures don't line up. Retiring it lets Gmail stop vouching for mail it can't cleanly authenticate.
Passwords are being phased out
"Send mail as" leaned on SMTP usernames and passwords — exactly the long-lived shared secrets the industry is racing to kill, and the ones Google has already begun removing. A feature built on that foundation was always living on borrowed time.
It was never a paid product
Custom-domain sending is a selling point of Google Workspace, the paid tier. Giving it away on free Gmail through a side door was a quirk, not a commitment. The quirk is what closes.
Who gets hit hardest
If you only ever email from @gmail.com, this is noise. The people who feel it are the ones who quietly built a brand on their own address:
- Freelancers and founders replying as
hello@yourstudio.comwhile living in Gmail. - Small teams sharing
billing@,support@, orpress@through forwarding into personal Gmail. - Anyone with several domains — a main business, a side project, a vanity name — all funneled into one Gmail and answered as the right address.
Detect the deprecations in your own Google account
You don't have to take the January 2027 horizon on faith. The moves underneath it — the ones Google has actually announced — are visible in your own account today, and each leaves a mark you can check for yourself. Work down this list; the more boxes you tick, the closer the ground already is to shifting under your setup.
- App passwords — Google Account → Security → 2-Step Verification → "App passwords." These 16-character SMTP passwords are the credential "Send mail as" usually stores. Google has already removed the option for many accounts, so look for the tell: if the page is gone, greyed out, or your 2-Step screen no longer lists "App passwords" at all, the credential your sending relies on can no longer be reissued.
- "Less secure app access" — Google Account → Security. This toggle once let plain username-and-password SMTP work at all. Google has withdrawn it across consumer accounts, so here the thing to look for is an absence: if you remember the setting but can no longer find the section, that disappearance is the deprecation, not a menu you've misplaced.
- Basic SMTP auth — Gmail → Settings → Accounts and Import → "Send mail as" → "edit info." If your custom entry still shows an SMTP host with a stored username and password, you are riding exactly the basic-auth path Google is retiring in favour of OAuth sign-in. A working entry here is not reassurance — it's the thing on the clock.
- The reissue test. Try to generate a fresh app password, or add a brand-new custom address under "Send mail as." If either refuses to complete on clean, correct settings, the retirement has already reached your account — whatever date is or isn't published.
None of these checks break anything or commit you to a move. They simply tell you where your account already sits on a transition Google has set in motion, so "January 2027" stops being an abstract horizon and becomes a reading of your own settings.
The own-it path, in plain terms
Where your sending lands matters, because the whole lesson of this deadline is that a capability you don't control can be withdrawn. Blue Folder Mail is one destination built for exactly that: a self-hosted, encrypted mail app that lives on your own Cloudflare account. One app, every domain you own, sending and receiving from the exact address each message arrived at — with proper SPF and DKIM behind it because the sending happens on infrastructure that's actually yours, and no per-domain pricing to recreate "Send mail as" somewhere costlier.
On encryption, an honest word: your mail is stored with zero-access encryption, meaning it's encrypted at rest with a key derived from your passkey that never leaves your device in a usable form. That's strong, and it's also not magic — no app can promise the impossible. What it can promise is that the key is yours and the sending is yours, long after January 2027 takes the Gmail shortcut away.
- What is expected to change around January 2027?
- Gmail's "Send mail as" is expected to stop supporting custom domains on consumer accounts. You would no longer send from you@yourdomain.com through free Gmail; receiving mail is unaffected. January 2027 is the deadline this trajectory points to rather than a date Google has published.
- Will my existing Gmail "Send mail as" address keep working?
- The underlying credentials are already being retired, so the setup is on borrowed time. Once the consumer cutoff lands, addresses configured for custom-domain sending stop sending as your domain, and outbound reverts to your Gmail identity or fails.
- Can I just pay Google Workspace instead?
- You can, and it supports custom-domain sending — but it bills per user and often per domain, every month. If you run several domains, that is the recurring cost many people move to a self-hosted inbox to avoid.
- Do I have to switch before January 2027?
- You do not have to wait for the deadline. Moving early means your outbound identity never flickers — you set up custom-domain sending you own, and the Gmail cutoff simply passes you by.