Skip to main content
CaptainDNS

Gmail ends POP fetching in January 2027: impact and action plan

By CaptainDNS
Published on December 5, 2025

Updated on November 6, 2026

POP fetching from external accounts into Gmail on the web ends in January 2027, with three alternatives for receiving mail: automatic forwarding, the Gmail mobile app, and an IMAP mail client
Update - November 6, 2026

Google's documentation, checked on November 6, 2026, gives the following timeline:

  • After the first quarter of 2026, Gmailify and POP fetching no longer support new users. Existing users can use them until January 2027.
  • Google announces their complete removal in January 2027, without an exact day.
  • Send as for third-party addresses is now explicitly affected, on the same schedule. This guide stays focused on receiving; our article details the end of Send as for third-party addresses.

To prepare the switch, see our action plan.

TL;DR
  • In January 2027, Gmail on the web will no longer let you automatically fetch messages from external accounts via POP (menu "Check mail from other accounts"). New users have not been supported since the end of the first quarter of 2026.
  • On the same schedule, Google is removing Gmailify, which applied Gmail's spam filters and features to Yahoo/Outlook/other mailboxes directly from Gmail.
  • Emails already imported stay in your Gmail mailbox. Only new messages will stop being fetched after the removal.
  • POP and IMAP remain supported to access Gmail itself from external clients (Thunderbird, Outlook, Apple Mail, etc.). What goes away is Gmail's role as a hub for other accounts on the web.
  • Google's pages list no exception for Google Workspace for POP fetching and Gmailify: an organization that uses Gmail to fetch other mailboxes must prepare its migration.
  • For receiving, Google recommends automatic forwarding at the external provider or connecting the account in the Gmail mobile app. To group several accounts and send from each one, use a dedicated mail client.

Context: what exactly Google is removing

For years, Gmail on the web could serve as a single interface for several mailboxes:

  • through the "Check mail from other accounts" feature in the "Accounts and import" settings;
  • by fetching messages from external mailboxes (hosting provider mail, Yahoo, Outlook, another Gmail, etc.) via POP;
  • optionally by enabling Gmailify, which applied Gmail spam filters, tab categories (Primary / Social / Promotions...) and advanced search to those external accounts.

In practice, Gmail acted as a POP vacuum: at regular intervals, it connected to your other accounts, downloaded new messages, and stored them in your Gmail mailbox.

When we published this guide in December 2025, Google's documentation mentioned "Starting January 2026". Checked on November 6, 2026, its pages now give a different timeline:

  • Gmailify will be removed;
  • continuous POP fetching "Check mail from other accounts" will disappear from Gmail on the web;
  • all of this in January 2027, along with Send as for third-party accounts, which concerns sending.

These changes are described on the official pages Learn about upcoming changes to Gmailify & POP in Gmail and Learn about changes to third-party email account support in Gmail.

Timeline: when does this happen?

Google's two pages complement each other:

  • After the first quarter of 2026: Gmailify and POP fetching no longer support new users. Existing users can use them until January 2027.
  • Third and fourth quarters of 2026: transition period. Send as for third-party accounts, Gmailify, and POP keep working, but Gmail may restrict new setups. Google encourages migrating during this period.
  • January 2027: complete removal of Send as for third-party accounts, Gmailify, and POP. Google has not given an exact day.

Without an exact day, we advise finishing your migrations before the end of December 2026: list the affected accounts, choose an alternative, and test the new access path before that date.

Timeline with three milestones: after the first quarter of 2026, no new users for Gmailify and POP; in the third and fourth quarters of 2026, announcement of the end of third-party Send as and transition; in January 2027, removal of third-party Send as, Gmailify, and POP

Archive - update of January 24, 2026

We recorded this warning banner in the Gmail interface in January 2026:

Warning banner recorded in Gmail in January 2026, which at the time announced the end of Gmailify and POP3 for early January 2026

The banner read: "Starting early January 2026, Gmailify will be discontinued, and the ability to check mail from other accounts (POP3) on the Gmail website will no longer be available."

At the time, this banner announced January 2026. Google's documentation checked on November 6, 2026 now gives the timeline above. It does not say whether this banner was followed by a cutoff for existing users.

What exactly changes for users?

There are two use cases to distinguish:

1. Accessing Gmail from another client (POP/IMAP)

Nothing changes here.

Per the official documentation, Gmail continues to accept inbound POP and IMAP connections from third-party clients (Thunderbird, Outlook, Apple Mail, mobile apps, etc.), as long as those clients are configured with the right settings.

In short:

  • you can still set up your Gmail or Google Workspace account in a mail client via POP or IMAP;
  • what goes away isn't POP as a protocol to access Gmail, but Gmail using POP to fetch mail from other mailboxes.

2. Using Gmail to group other accounts (POP Checkmail)

This is the flow Google is removing.

Until now, in Settings → Accounts and import → Check mail from other accounts, you could:

  • add an external account;
  • ask Gmail to fetch new messages from that account via POP, label them, and optionally archive them.

According to Google, in January 2027:

  • the "Check mail from other accounts" option will no longer be available in Gmail on desktop;
  • Gmail will no longer fetch messages from your external accounts via POP;
  • messages already imported stay in Gmail;
  • only new messages sent to those external accounts will stop being brought into Gmail automatically.

And what about Gmailify?

Gmailify, which applied Gmail's filters and features to some external accounts (Yahoo, Outlook, etc.), is also removed in January 2027.

On these accounts, you will lose Gmail's spam protection, enhanced mobile notifications, inbox categories, and advanced search. Their messages already imported stay visible in Gmail. In the Gmail app for Android, iPhone, and iPad, you can keep reading and sending messages from these accounts over a standard IMAP connection.

And sending from an external address?

Send as, which lets you send from a third-party address inside your Gmail account, goes away on the same schedule, on the web and in the mobile apps. If you currently reply with your external address from Gmail, receiving is only half the issue: also read our article on the end of Send as for third-party addresses.

Gmail and Google Workspace: who is affected?

For Gmailify and POP fetching, Google's pages do not distinguish consumer Gmail accounts from Google Workspace accounts, and list no exception for Workspace. The page on Gmailify and POP does state:

"Important: If you have a work or school account, your administrator can help migrate your email data into Google Workspace."

Here is what that means by account type:

  • Personal Gmail accounts

  • Loss of the "Check mail from other accounts" POP feature in Gmail on the web.

  • POP/IMAP remain available to access the Gmail account itself from external clients.

  • Option to connect external accounts in the Gmail mobile app.

  • Google Workspace accounts (business, education, etc.)

  • If your users fetch external mailboxes via POP in Gmail, treat this flow as affected.

  • The administrator can help migrate email data to Workspace, or organize the move to a mail client or to forwarding.

  • POP/IMAP remain available to access the Workspace account itself.

A Workspace organization that uses Gmail as a POP aggregator must therefore prepare its migration just like a free Gmail account. Identities hosted by Google stay supported for Send as, but that exception concerns sending: it does not cover POP fetching.

IMAP, POP, Gmailify... quick refresher

Before looking at alternatives, here is a one-minute reminder of the terms.

  • POP (Post Office Protocol) Older protocol that downloads messages from a mail server to a client. By default, it works in "bursts": connect, fetch new items, disconnect. Messages are often deleted from the server after download (unless you change the option).

  • IMAP (Internet Message Access Protocol) More modern protocol that keeps messages on the server and syncs states (read/unread, folders, etc.) across multiple clients. IMAP is the standard for multi-device access today.

  • Gmailify Gmail feature that applied Gmail functionality (spam, categories, advanced search...) to external accounts linked via IMAP (Yahoo, Outlook, etc.).

  • POP Checkmail / "Check mail from other accounts" Gmail feature acting as an embedded POP client: Gmail regularly connected to your other mailboxes via POP, fetched messages, and stored them in your Gmail mailbox.

  • Send as Sending feature, separate from the previous ones: it lets you send from another address inside your Gmail account.

  • Google Workspace Collaboration suite (Gmail, Drive, Docs, etc.) with paid accounts, typically used by organizations. Mailboxes are also accessed via the Gmail interface and via POP/IMAP.

Gmailify and POP Checkmail are what disappear in January 2027 on the receiving side, and Send as for third-party addresses on the sending side.

What you can still do... and what becomes impossible

The new usage matrix comes down to this:

Diagram of receiving flows: until January 2027, Gmail on the web fetches external accounts via POP; starting January 2027, external accounts go through automatic forwarding to Gmail or through IMAP in the Gmail mobile app or a mail client

Still possible after January 2027

  • Access your Gmail / Workspace account from:

  • an IMAP client (recommended);

  • a POP client (still supported per the official documentation);

  • the Gmail mobile app (Android / iOS);

  • the mail.google.com website.

  • Add external accounts (Yahoo, iCloud, your host's IMAP mailboxes, etc.) to the Gmail mobile app and use them in the mobile interface. On Android, Google also says that accessing third-party accounts via POP remains possible in the Gmail app.

  • Receive messages in Gmail that are automatically forwarded from an external account.

  • Run one-off imports ("Import mail and contacts") from another account into Gmail: it isn't real time, but a one-time migration.

No longer possible starting January 2027

  • Use the Gmail web interface to:

  • continuously fetch messages from external accounts via POP;

  • centralize several mailboxes (from hosts or other providers) in a single Gmail inbox via POP Checkmail;

  • benefit from Gmailify on Yahoo / Outlook & co. accounts.

  • Offer your Workspace users an "all Gmail" (web) experience for external mailboxes hosted elsewhere, without forwarding or a mail client.

  • Send from a third-party address with Send as, on the web or in the mobile apps.

Alternatives: how to keep mailboxes centralized?

For receiving, Google offers two options: automatic forwarding at the provider and the Gmail mobile app. Its page on third-party accounts adds the provider's website or app and the desktop mail client. The choice also depends on sending: forwarding brings messages into Gmail, but it does not let you reply to them with the external address. It is the only option below that covers receiving alone.

1. Use a multi-account mail client

For many advanced uses, the closest solution to grouping accounts in Gmail is to hand that grouping to a dedicated mail client, for example:

  • Thunderbird / Betterbird;
  • Outlook;
  • Apple Mail;
  • or other professional IMAP clients.

Advantages:

  • native handling of several IMAP/POP accounts in the same interface, with SMTP sending from each account;
  • sorting rules, filters, shared folders, delegated mailboxes, etc.;
  • no dependency on a single provider for aggregation.

Drawbacks:

  • requires a computer (or mobile app) with that client installed;
  • some Google features (Gmail search, labels, etc.) are not available as-is for external mailboxes.

2. Set up automatic forwarding at the external provider

Google's official guide recommends enabling automatic forwarding at the external mailbox provider to your main Gmail address. Google specifies that this setting is independent of Send as.

Typical scenario:

  1. On the external mailbox (host, other provider), you configure a forward to your Gmail or Workspace address.
  2. Gmail receives messages directly, without fetching them over POP.

Points to watch:

  • forwarding handles receiving and does not replace Send as: it does not bring back replying with the external address;
  • SPF can fail after forwarding, because the message leaves from a server the original domain has not necessarily authorized;
  • a preserved DKIM signature aligned with the From can let DMARC pass despite that failure, as long as forwarding does not modify the signed message;
  • SRS rewrites the envelope address and helps SPF pass, but SRS alone does not guarantee DMARC, because the rewritten domain is not aligned with the From;
  • changing your SPF therefore does not fix every forward: test with real messages and read the headers received in Gmail.

If you manage the domain or server doing the forwarding, use the migration to check SPF, DKIM, and DMARC. MX records only come into play if the hosting of your incoming mail changes.

3. Use the Gmail mobile app as an aggregator

If you accept aggregation being available only on mobile:

  • the Gmail app for Android, iPhone, and iPad lets you add several external accounts over a standard IMAP connection;
  • you can read and send from these accounts in the same app (but not in a unified inbox on the web).

An account added directly like this is not Send as: it keeps working after January 2027, while Send as goes away on mobile too.

This option suits you if you manage your messages only on mobile. For a support team or daily use on a computer, it often falls short.

4. Migrate some mailboxes to Google Workspace or a dedicated provider

If your users are already used to reading everything in Gmail, this change can be the occasion to:

  • migrate critical mailboxes to Google Workspace (or another service) to group the hosting of your mailboxes with a single provider;
  • consolidate your mail domains and subdomains to reduce routing complexity;
  • review your MX records and routing rules (including SMTP relays and anti-spam gateways), if the hosting of your incoming mail changes.

For work or school accounts, Google says the administrator can help migrate email data to Google Workspace, with its data migration service.

5. Stay on the provider's website or app

This is the simplest option, and Google lists it first on its page about third-party accounts: read and send your messages directly from your provider, for example outlook.com or mail.yahoo.com. You give up centralization, with nothing to reconfigure.

Right now

  • Inventory the affected accounts:

  • in Gmail, go to Settings → Accounts and import → Check mail from other accounts;

  • list all external mailboxes configured via POP Checkmail;

  • also identify third-party addresses used to send via Send as: see our article on the end of Send as for third-party addresses.

  • Identify user profiles:

  • individual user centralizing two or three personal mailboxes;

  • small business using Gmail as the mail interface for mailboxes hosted elsewhere;

  • Workspace organization with legacy use cases (shared mailboxes, temporary redirects, etc.).

  • Don't count on a new setup: Gmail may already restrict new settings during the transition period.

Before January 2027

For each external account:

  1. Choose a target strategy:
  • multi-account mail client;
  • automatic forwarding to Gmail;
  • migration to Workspace or another provider;
  • access only on the provider's mail website or through its IMAP access.
  1. Test in real conditions:
  • send messages from outside;
  • check reception, spam, and headers;
  • check which address replies are sent from;
  • validate the user experience (folders, search, archiving).
  1. Communicate with end users:
  • explain Google's change and the January 2027 deadline;
  • document the new way to read their mail;
  • plan support during the switchover.

After the announced removal

  • Check that messages from each mailbox that went through POP Checkmail now arrive by their new path.
  • Monitor deliverability (SMTP logs, user feedback) to detect any lost messages caused by incomplete reconfiguration.
  • Update your internal documentation and troubleshooting procedures to reflect the new model.

Specifics for hosting providers and ISPs (and CaptainDNS customers)

If you host mailboxes for customers, this Google decision has a direct impact:

  • some of your users probably use Gmail as a POP client without you having clear visibility;
  • after the January 2027 removal, they simply won't see their messages appear in Gmail, even though everything will keep arriving correctly on your servers.

We therefore advise you to:

  • inform your customers before the deadline, explaining that this is not an outage of your service but a change in Gmail;

  • offer a migration guide, for example:

  • IMAP (reading) and SMTP (sending) setup in a client (Thunderbird, Outlook, etc.);

  • forwarding to Gmail, tested with real messages;

  • possible migration to Google Workspace or another service if the need is a unified web interface.

On the DNS and deliverability side, large-scale forwarding to Gmail calls for a few precautions:

  • keep the message intact during forwarding: a preserved, aligned DKIM signature is what can let DMARC pass when SPF fails;
  • don't present SPF or SRS as a universal solution: SPF can fail during forwarding, and SRS alone does not guarantee DMARC;
  • sign your own flows with DKIM and deploy a DMARC policy consistent with the reality of your flows.

FAQ

Did POP fetching stop in January 2026?

Google's pages checked on November 6, 2026 do not say so. A banner recorded in Gmail in January 2026 announced that date. The current documentation says that after the first quarter of 2026, the feature no longer supports new users, that existing users can use it until January 2027, and that its complete removal will take place in January 2027, without an exact day.

Will I lose the emails already imported into Gmail via POP?

No. Google says messages already imported before the feature is removed stay in your Gmail mailbox. The change is that new messages from your external accounts will no longer be fetched automatically via POP after the January 2027 removal.

Is POP completely removed from Gmail?

No. POP is not being removed as a protocol to access Gmail. You can still configure your Gmail or Workspace account in an external client via POP or IMAP. What goes away is Gmail using POP to fetch mail from other servers ("Check mail from other accounts").

Can I still use Thunderbird, Outlook, or Apple Mail with Gmail / Google Workspace?

Yes. Mail clients like Thunderbird, Outlook, or Apple Mail can still access your Gmail / Workspace account via IMAP (or POP). Removing POP Checkmail only affects the feature where Gmail itself acted as the POP client for other accounts.

Is my company Google Workspace account affected?

Yes, if your users use Gmail on the web to fetch messages from external mailboxes via POP. Google's pages list no exception for Workspace on this point, and say the administrator can help migrate email data to Google Workspace. POP/IMAP access to the Workspace mailbox itself remains supported.

Is there an official alternative to centralize several mail accounts in Gmail on the web?

For receiving, yes: Google recommends automatic forwarding from external mailboxes to your Gmail or Workspace address, so new messages arrive in your main mailbox. Google does not name a web replacement for Gmailify, or for replying with the external address from Gmail. The other options are the Gmail mobile app, a dedicated mail client, or the provider's website.

Is the 'Send mail as...' feature also removed?

Yes, Google also announces the end of Send as for third-party addresses not hosted by Google in January 2027. Other Gmail addresses and Google Workspace identities hosted by Google stay supported. Our article details the end of Send as for third-party addresses and the solutions for continuing to send.

Glossary

POP Checkmail

Name sometimes used for the feature that fetches mail from external accounts via POP in Gmail on the web.

Gmailify

Feature that applied Gmail spam filters and features to external accounts (Yahoo, Outlook, etc.) linked via IMAP.

Send as

Gmail feature that lets you send from another address inside your account. Google is removing it in January 2027 for third-party addresses it does not host.

POP (Post Office Protocol)

Protocol that downloads messages from a mail server to a client, often without state synchronization.

IMAP (Internet Message Access Protocol)

Protocol for synchronizing messages between a server and multiple clients, keeping folders and states aligned.

Mail client

Software (Thunderbird, Outlook, Apple Mail, mobile app, etc.) used to read and send emails via POP/IMAP/SMTP.

Google Workspace

Google's business offering including Gmail, Calendar, Drive, Docs, etc., with mailboxes hosted by Google.

Forward / automatic forwarding

A server or mailbox feature that automatically sends incoming messages to another address.

MX, SPF, DKIM, DMARC

DNS records and mechanisms used to announce your mail servers (MX) and protect your domains from spoofing (SPF/DKIM/DMARC).

📚 Related Gmail guides

Similar articles