Gmail 'Check Mail From Other Accounts' Removed: 2026 Fix

For years, one Gmail setting quietly did the work of five inboxes: check mail from other accounts pulled your Outlook, Yahoo, iCloud and old work mail into a single Gmail tab, applied Google's spam filter through Gmailify, and let you reply from any of those addresses with "Send mail as." In 2026 Google confirmed it is switching that whole system off — and if you route external mailboxes through Gmail on the web, your setup has an expiration date.

This guide explains exactly what is changing, the dates that matter, and the three migration paths that keep your mail flowing after the check mail from other accounts feature disappears. Whether you consolidated a personal address years ago or run a stack of aliases for outreach, you have a narrow window to move before the fetch simply stops and mail starts piling up in an inbox you no longer watch.

What Gmail Is Actually Removing

Three connected features are being retired, and it helps to name them precisely because they solve different jobs. The headline change is the check mail from other accounts option — the POP-based fetcher you configure under Settings, Accounts and Import, that logs into a third-party mailbox on a schedule and copies new messages into Gmail. When Google talks about "dropping POP," this is the consumer-facing feature it means.

Riding on top of that fetcher is Gmailify, which links a supported provider (Yahoo, Outlook.com, AOL and a few others) so your external mail gets Gmail's spam filtering, categories and search without leaving the Gmail interface. Gmailify is being switched off alongside the fetch. The third piece is Send mail as, the setting that lets you compose from an @outlook.com or @yahoo.com address inside Gmail so your replies match the mailbox the message arrived at. For third-party addresses tied to the fetch, that outbound half is going away too.

Put simply: the feature that turned Gmail into a free multi-account aggregator on the desktop web is being dismantled. If you only ever used one Gmail address on its own, nothing here touches you. If you leaned on check mail from other accounts to run your life out of a single tab, you are the person this change is aimed at.

The Shutdown Timeline: Dates That Matter

Google is not flipping one switch on one day — it is closing the door in two stages, and understanding both keeps you from being caught out. The important thing is that the restriction on new setups arrives well before the shutdown of existing ones, so procrastinating quietly narrows your options.

Two takeaways. First, if you have not already connected a mailbox, you likely cannot add a new one through check mail from other accounts anymore — that window has closed, so a fresh setup needs an alternative from day one. Second, if your existing fetch is still running, treat January 2027 as a hard deadline rather than a suggestion. Messages that arrive at your external mailbox after the cutoff will simply never appear in Gmail unless you have already put another route in place. Everything already imported before the shutdown stays safely in your Gmail account — it is only the ongoing pull that ends.

Who Is Affected — Free Gmail vs Workspace

The confusion here is worth clearing up, because "Gmail is dropping POP" got reported in ways that scared people it did not apply to. The change targets the consumer check mail from other accounts aggregator on free @gmail.com accounts — the setup where Gmail reaches out to a different provider's server and pulls mail in.

• Free Gmail users pulling in external mail. You are the primary group affected. Any address you added under "Check mail from other accounts" — an old ISP mailbox, a Yahoo account, a work address on another host — loses its automatic pull in January 2027.
• Gmailify users. If you linked Yahoo or Outlook.com for Gmail-style filtering, that link ends on the same schedule.
• Google Workspace users. Workspace hosts your mail directly on Google's servers, so the POP fetch-from-elsewhere feature is not central to how your mail arrives. The consumer aggregator shutdown does not change where your Workspace mail lives. This is a big reason Workspace keeps coming up as the clean answer for people who were leaning on Gmail as a hub — a trade-off we break down in our Gmail accounts vs Google Workspace comparison.
• People using POP/IMAP to read Gmail elsewhere. Reading your Gmail in another app is a separate mechanism and is not what is being removed here. The retirement is specifically about Gmail reaching out to fetch other mailboxes.

So the honest one-line summary is this: if Gmail logs into another provider on your behalf, that arrangement is ending. If Gmail is simply your mailbox, you are fine.

Why Google Is Killing POP Fetch and Gmailify

POP — the Post Office Protocol — is old. It was designed for a world of dial-up connections where you pulled mail down to one computer and worked offline. It has no real concept of folders, sync, or seeing the same state across devices, and it fetches on a slow, fixed schedule rather than in real time. Every time Gmail runs a check mail from other accounts cycle, it is essentially screen-scraping a legacy protocol, which is slow, error-prone, and a security liability because it often requires storing the third-party password.

Google's direction is unambiguous: push everyone toward modern, real-time, token-based connections (IMAP and OAuth) and away from password-in-a-box POP fetching. Retiring the consumer aggregator also removes a support and abuse surface — fetchers that break silently, credentials that leak, and misconfigured pulls that duplicate or lose mail. From Google's side, killing check mail from other accounts is housekeeping. From your side, it is a migration you did not ask for. Both things are true, and the practical response is the same: move to a supported route before the deadline.

What Breaks the Day It Switches Off

It is easy to underestimate a "feature removal" until you map what actually stops. When the check mail from other accounts fetch is disabled, here is the concrete fallout for someone who never migrated:

• New external mail stops arriving in Gmail. Messages sent to your Yahoo, Outlook or ISP address still land in that mailbox — they just never get pulled into your Gmail inbox. If you stopped checking the original mailbox years ago, you effectively go dark on it.
• Replies from the external address stop working. With Send-as gone for that address, you can no longer compose from it inside Gmail, so outgoing continuity breaks along with incoming.
• Gmailify filtering ends. Any spam and category cleanup Gmail was applying to that linked mailbox stops. You are back to that provider's native filtering.
• Silent failure is the real danger. Gmail does not bounce the mail — it simply is not there. Missing messages with no error is exactly the pattern that makes people think their inbox is broken, which we cover in depth in our guide to Gmail not receiving emails.

The takeaway: this is not a cosmetic change. For anyone who consolidated a real, active address into Gmail, an un-migrated shutdown means missed mail you may not notice for weeks.

Fix 1: Provider-Side Auto-Forwarding

The simplest replacement for check mail from other accounts is to flip the direction. Instead of Gmail pulling from your other mailbox, have that mailbox push every new message to your Gmail address automatically. Almost every provider — Outlook.com, Yahoo, iCloud, most ISPs and hosts — offers an auto-forwarding rule in its own settings.

Set it up from the source side:

• Log into the external mailbox directly (not through Gmail) and open its settings.
• Find "Forwarding" — often under Mail, Rules, or Automatic processing — and enter your Gmail address as the destination.
• Choose whether to keep a copy at the source. Keeping a copy is safer during the transition so nothing is lost if a rule misfires.
• Confirm the verification email that Gmail or the provider sends to prove you own the destination.

Forwarding is the closest one-to-one swap for the incoming half of the fetch, and it happens in near real time rather than on a slow poll. The one thing it does not restore by itself is the ability to reply as that address — that is the Send-as problem covered below. Forwarding also has deliverability quirks worth knowing, because forwarded mail can trip authentication checks and land you the dreaded warning banner we explain in our piece on the "be careful with this message" warning.

Fix 2: IMAP in the Gmail Mobile App

Here is the detail most panicked headlines buried: the Gmail mobile app is not losing third-party account support the way the desktop web fetcher is. On Android, iPhone and iPad, the Gmail app can add an external account over IMAP — the modern, real-time, folder-aware protocol — and you can both read and send from that address inside the app.

So if your whole reason for using check mail from other accounts was "I want all my mail in the Gmail app on my phone," you may barely feel this change:

• Open the Gmail app, tap your avatar, and choose Add another account.
• Pick the provider (or "Other" for a generic IMAP mailbox) and sign in.
• The app connects over IMAP, syncing folders and state in real time rather than polling.
• You get a unified view and can send from the external address on mobile.

The catch is that this is a mobile experience. It does not stitch the external mailbox into your @gmail.com inbox on the desktop web the way the old fetcher did — instead you switch between accounts. For many people that is a perfectly good trade for keeping real-time sync and outbound sending. Pair it with forwarding (Fix 1) and you cover both desktop visibility and mobile control.

Fix 3: Move to Workspace or a Real Client

If the external address is a domain you actually own — a business address, or mail on your own domain — the cleanest long-term answer is to stop bolting it onto a free Gmail account and host it properly. Two routes fit here:

• Google Workspace. Host the domain's mail directly on Google. You keep the Gmail interface you already know, gain native (not fetched) delivery, and sidestep the entire consumer-aggregator shutdown. For anyone running outreach, sales, or a brand address, this is usually the right move — the cost and deliverability math is laid out in our Workspace vs Gmail breakdown.
• A desktop email client over IMAP. Apps like Thunderbird, Apple Mail or Outlook connect to every one of your mailboxes over IMAP and present them in one place — a true multi-account inbox that never depended on Gmail's fetcher at all. This is the classic answer for people who want one desktop app to rule several addresses.

Both routes replace the fragile POP pull with a modern, real-time connection. The difference from the old check mail from other accounts model is that your mail lives where it should — on a proper host or in a proper client — rather than being scraped into a free consumer inbox on a timer.

The "Send Mail As" Problem and Its Replacement

Incoming mail is the easy half. The part people forget until it bites them is Send mail as — replying from your other address so recipients see the right sender. When that goes away for third-party addresses, forwarding alone leaves you replying from your @gmail.com address, which looks wrong and can confuse contacts who only know your old address.

Your options to preserve outbound identity:

• Reply from the source mailbox directly. Log into the external account's own webmail or app to send from it. Simple, but it means leaving Gmail for outbound.
• Use the Gmail mobile app's IMAP account. As covered above, the app lets you send from the added address on mobile, restoring the reply-as-yourself behavior on phones and tablets.
• Move to Workspace or a client. Both host the address as a real account, so sending from it is native, not a bolted-on alias.
• Consolidate onto aliases you control. If the point was just to manage several public addresses, Gmail's own alias tools may cover part of the job — the dot trick, plus-addressing and send-as within Gmail's own domain still work, as detailed in our Gmail email aliases guide.

Whatever you pick, decide the outbound plan at the same time as the inbound one. A migration that fixes receiving but forgets sending is only half done, and you will discover the gap the first time you hit reply.

Your Step-by-Step Migration Checklist

Here is the order of operations that gets you off check mail from other accounts cleanly, without a gap where mail could vanish:

• List every connected mailbox. In Gmail on the web, open Settings, Accounts and Import, and note every address under "Check mail from other accounts" and "Send mail as." You cannot migrate what you have not inventoried.
• Decide the destination for each. Personal legacy address you rarely use? Forwarding is enough. Active address you own? Workspace or a client. All-your-mail-on-your-phone? The mobile app over IMAP.
• Set up the new route first, before turning anything off. Add forwarding at the source, or add the IMAP account in the app, while the old fetch is still running. Overlap protects you.
• Verify a test message arrives through the new route from each mailbox before you rely on it.
• Rebuild your Send-as plan so replies still go out from the right address.
• Update filters and labels that assumed fetched mail, so incoming forwarded mail sorts the way you expect.
• Keep the source mailbox alive. Do not delete the external account — it is now the real home of that mail, and forwarding depends on it staying active.

Do this before January 2027 and the shutdown becomes a non-event. Do it after, and you are reconstructing a mail flow while messages are already going missing.

What This Means for Deliverability

There is a quieter angle to this change that matters for anyone who sends volume, not just personal users. The old check mail from other accounts plus Send-as combination was a common way to run several public addresses through one Gmail interface. As that collapses, people are rethinking how many real, separate, properly hosted inboxes they actually need — and consolidating five scraped addresses into one aggregator was always a fragile foundation for sending.

Two deliverability realities to carry forward. First, forwarded mail can fail authentication. When a message is auto-forwarded, SPF checks against the forwarding server, not the original sender, which is exactly why forwarded mail sometimes lands in spam or triggers warning banners. Setting up forwarding is not a free lunch; test it. Second, reply-as identity affects trust. Recipients who suddenly get replies from a generic @gmail.com address instead of your known business address may hesitate, and inconsistent sending identity can nudge your mail toward the spam folder over time.

For senders who were stretching one Gmail account across several identities, this is a nudge to do it properly: real inboxes, correct authentication, and one clean sender per purpose. If deliverability is your goal, our broader Gmail accounts overview lays out why one solid, properly hosted inbox per identity beats a stack of fetched aliases held together by a feature Google is now removing.

Frequently Asked Questions

Is Gmail really removing "check mail from other accounts"?

Yes. Google is retiring the consumer POP fetcher — the "check mail from other accounts" setting — along with Gmailify and third-party "Send mail as." New setups were restricted starting in early 2026, and existing configurations are scheduled to stop working in January 2027. After that, Gmail will no longer log into your other mailboxes to pull mail in, so you need forwarding, the mobile app over IMAP, or a proper host in place before the cutoff.

Will I lose the emails already imported into Gmail?

No. Every message that was already fetched and sitting in your Gmail account stays exactly where it is. The shutdown only stops the ongoing pull of new mail from the external mailbox — it does not delete anything Gmail already imported. Your history is safe; it is only future messages from the linked account that will stop arriving unless you set up an alternative route.

Does this affect Google Workspace accounts?

Not in the same way. Workspace hosts your mail directly on Google's servers, so it does not depend on the consumer "check mail from other accounts" aggregator that is being removed. The change targets free @gmail.com accounts that were pulling mail in from other providers. In fact, moving a domain you own onto Workspace is one of the recommended long-term replacements for the feature.

What is the easiest replacement for the fetch feature?

For most personal users, provider-side auto-forwarding is the simplest swap: log into your other mailbox, turn on forwarding to your Gmail address, and confirm the verification email. It pushes mail to Gmail in near real time. If you want to also reply from that address, add the account in the Gmail mobile app over IMAP, or move it to Google Workspace or a desktop client so sending stays native.

Can I still read and send from other accounts in the Gmail app?

Yes. The Gmail app on Android, iPhone and iPad can add third-party accounts over IMAP, which is the modern real-time protocol, and lets you both read and send from them. This is separate from the desktop web fetcher that is being retired, so mobile users who just wanted all their mail in one app are largely unaffected — you switch between accounts rather than blending them into one @gmail.com inbox.

Migrating off check mail from other accounts and rethinking how many real inboxes you actually need? Browse quality-checked options on our product page, or message us on Telegram at t.me/mixgmail for live stock, setup advice, and help moving your mail flow onto something Google is not about to switch off.