Google just announced they’re killing three Gmail features that a lot of people rely on. Starting January 2027, you won’t be able to send emails from a Yahoo or Outlook address through your Gmail account anymore. The web version of POP fetching is going away too. And Gmailify—the thing that lets Gmail’s spam filters work on your external accounts—is also getting the axe.
I’ve been using Gmail as my central inbox for years. I have my personal domain, a couple of old Yahoo addresses, and my main Gmail all routed through one place. So this one stings a bit.
Let me break down what’s actually happening, because Google’s announcement is a little dense.
The Three Features That Are Going Away
“Send as” for third-party accounts is probably the biggest one. If you’ve ever gone into Gmail settings, added a non-Gmail address, and set it up so you can send emails that look like they’re coming from that address—that’s going away. Both the web version and the mobile apps are affected.
Here’s a concrete example: say your main Gmail is [email protected], but you also own [email protected]. Right now, you can compose an email in Gmail and send it as [email protected]. The recipient sees that address, not your Gmail. Starting January 2027, that stops working for non-Google addresses.
POP fetching on the web is the second one. This is how Gmail pulls emails from your Yahoo, Outlook, or other accounts into your Gmail inbox. You set it up once, and Gmail periodically checks those accounts and brings new mail over. That’s going away on the web version.
Gmailify is the third. This was Google’s way of letting external accounts—mostly Yahoo and Outlook—get some Gmail superpowers. Spam protection, inbox categorization, better mobile notifications. All that goes away in January 2027.
What Still Works
The mobile app is fine. You can still add Yahoo, Outlook, or other non-Google accounts in the Gmail app on Android or iPhone. They show up as separate accounts, and you can switch between them to read and send mail. It’s just not as seamless as having everything flow into one inbox.
Gmail-to-Gmail aliases and Google Workspace “Send as” are unaffected. If you have multiple Gmail addresses or a Workspace account, nothing changes.
And if you use an external email client like Outlook, Thunderbird, or Apple Mail to access your Gmail—those still work through IMAP and POP. This change is specifically about accessing other accounts from Gmail, not accessing Gmail from other apps.
Why Is Google Doing This?
Google’s official line is that these features require “disproportionate maintenance resources”. They want to keep Gmail “secure, smart, and easy-to-use,” and maintaining these older integrations is apparently too much work.
I’m not buying that entirely.
The cynical take—and I’m seeing a lot of people say this on Reddit—is that Google is nudging power users toward paid Workspace accounts. Workspace “Send as” still works. The free version loses it. That’s not a coincidence.
What This Means for You
If you just use Gmail for your Gmail account, nothing changes. You won’t notice a thing.
If you’re like me—someone who uses Gmail as a central hub for multiple email addresses—this is annoying. Here’s what I’m planning to do:
Option one: Move to a desktop email client. Something like Thunderbird or Apple Mail can handle multiple accounts in one place. It’s not as convenient as having everything in Gmail’s web interface, but it works.
Option two: Just use the Gmail mobile app for everything and accept that the web experience is going to be more fragmented. The mobile app still supports multiple accounts.
Option three: Pay for Google Workspace. If “Send as” is critical for your workflow, this keeps it working. But it’s $6–$12 a month, which feels like a lot for a feature that used to be free.
The Timeline
Here’s when things happen:
- Q3 2026: Google starts notifying affected users.
- Q3–Q4 2026: Transition period. Existing features still work, but Google may restrict new setups.
- January 2027: Everything gets turned off.
So you’ve got until early 2027 to figure out your new setup. That’s plenty of time, but don’t put it off. If you’re using “Send as” or POP fetching right now, start thinking about alternatives.
My Take
Honestly? I’m disappointed. Gmail’s ability to act as a universal inbox is one of the reasons I stuck with it for so long. Being able to send from my custom domain while using Gmail’s interface was a killer feature.
But I also get it. Maintaining legacy integrations is expensive, and Google’s not in the business of running free services indefinitely. They’re a business, and businesses make these kinds of calls.
I’ll probably try the desktop client route first. Thunderbird has come a long way, and I’ve heard good things about its modern interface. If that doesn’t work, I might just accept the mobile-only approach and deal with the web version being less useful.
Either way, I’m not switching away from Gmail entirely. The core product is still solid. But this change does make me think about how much I’ve come to rely on features that Google can just decide to remove one day.
That’s the thing about free services. You’re not the customer. You’re the product. And sometimes the product gets rearranged in ways you don’t love.
I’ll report back once I’ve settled on a new workflow. If you’ve got a setup that works well, drop me a note—I’m curious what other people are doing.
