Hey, it's Pavel. Email Deliverability Expert helping email operators raise the bar for themselves and their teams. I'm building this newsletter for high-performing email marketers who want to stay ahead of the game. If you're serious about email deliverability, don't forget to subscribe.
The Gmail Change That's Already Breaking Email Setups
As of January 2026, Google officially ended two features that millions of people quietly built their entire email workflow around.
"Check mail from other accounts" is gone from Gmail on the web. Gmailify is gone. The unified inbox setup pulling Yahoo, Outlook, custom domains, all of it into one Gmail account — no longer works. Google sent notification emails to affected users back in September 2025. Now the cutoff has passed, and new mail from external accounts is no longer being fetched.
Emails already in your Gmail stay put. Only new fetching stopped.
Why Google made this move
POP3 dates back to the 1980s. The security issue at its core is that it transmits passwords in plaintext. It also has no native support for modern authentication like OAuth2 or Two-Factor Authentication. For a provider that has spent the last two years tightening SPF, DKIM, DMARC, and TLS requirements for bulk senders, killing off POP3 fetching on the receiving side is consistent with the same direction.
There's also an architectural problem. POP3 was built for a world with one device. It downloads mail and removes it from the server. In 2026, where the same inbox is checked on a phone, a laptop, and a tablet, that model creates sync failures. An email downloaded to your phone disappears from your desktop and it's how the protocol was designed.
🪄Why it's important:
A temporary reputation dip is not failure. It’s feedback. What turns it into real failure is treating it like noise and continuing to push volume anyway.
Want a Second Pair of Eyes on Your Setup?🔮
If January's Gmail changes touched any part of how your domain sends or receives mail, it's worth a proper check before the damage shows up in your inbox placement. I work directly with teams to audit authentication, identify forwarding risks, and make sure every part of your sending infrastructure is still working the way Gmail expects.
What to do now
You have two real options, and one important consideration about the simpler one.
IMAP is the clean path. Set up the external account via IMAP — it keeps mail on the server, syncs read/unread status across every device, and works properly. The Gmail mobile app still supports adding third-party accounts via IMAP, so that access point remains open.
⚠️Pay attention: IMAP through the Gmail mobile app still works — but this is not the same as the web-based "Check mail from other accounts" feature that was removed. Don't assume you're covered until you've confirmed the connection is live and new mail is actually arriving.
Forwarding is the faster setup, but carries a risk worth knowing. When your external account forwards everything to Gmail — including spam — it can make that account look like a spam source, which damages its sending reputation and affects deliverability for messages sent from that address. If your external account is a personal address you rarely send from, forwarding is fine. If it's a domain you send from regularly, IMAP is the safer choice.
⚠️ Pay attention: If you use forwarding and your external account sends real mail, watch your deliverability closely. Forwarding spam into Gmail flags the source address, and that damage to your sending reputation is silent — no bounce, no alert.
For teams running CRMs, support desks, or automation tools that used POP3 to read an inbox: check whether your tool supports OAuth2 login as most modern platforms do. If the tool is older and still needs a server address, generate an App Password in your provider's security settings after enabling two-factor authentication. That 16-character code often gets legacy tools working again while you plan a proper migration.
The deeper shift here is that Google is no longer willing to maintain a background service that reaches into other providers' servers on your behalf. That era is over. What replaced it is more secure, but it requires each person to understand their own setup.
Most people don't. Now is a good time to.
Behold! The Spam Filter Slayer speaks! 🔮
You can get started with beehiiv and get 20% off for three months using my link or simply paste my promo code: PAGTH7YX. They've built their entire platform around deliverability best practices, which means you won't end up troubleshooting broken authentication chains at midnight. From reverse I will get 50% of your payment from beehive so I can continue supporting my infrastructure, tools and day-to-day business.
|