Gmail to drop POP3 fetch and Gmailify in 2026 migrate to IMAP or Workspace

Google will stop fetching mail from third‑party accounts via POP3 and will retire Gmailify starting in January 2026, a move that immediately changes how many consumers consolidate email in Gmail and hands enterprises a clear migration path to Workspace tools.

Background / Overview​

Beginning January 2026, Gmail will no longer support two legacy conveniences that helped users centralize non‑Gmail mailboxes inside their @gmail.com inboxes: the “Check mail from other accounts (POP3)” fetch option and Gmailify, the feature that layered Gmail’s spam filters, inbox categories, and search on compatible third‑party accounts. Google’s help page states that these capabilities “will no longer be supported” and directs users toward IMAP (for mobile) and forwarding or migration options for continued access. The change has been widely reported by independent outlets and hosting providers, which emphasize the security rationale Google has offered: POP3 is older, has well‑known limitations (notably weaker authentication and plaintext transmission risks in some configurations), and doesn’t support modern sync semantics that IMAP provides. Multiple industry write‑ups confirm the timeline and practical implications for consumers and hosts.

---

What exactly is changing?​

POP3 fetch (“Check mail from other accounts”)​

• Gmail’s browser/web interface option that periodically logged into external mailboxes using POP3 and pulled new messages into a Gmail inbox will be removed. After the deprecation date, Gmail on the web will not be able to fetch mail from another provider using POP. Messages already fetched into Gmail remain in users’ mailboxes.

Gmailify​

• Gmailify—launched to give Yahoo!, Outlook.com and other supported accounts access to Gmail-style protections (spam filtering, categories, advanced search, enhanced notifications)—will also be discontinued. Accounts previously “Gmailified” will lose those Gmail-applied features.

What remains possible​

• The Gmail mobile app on Android, iPhone and iPad will continue to support adding third‑party accounts via IMAP, so mobile users can keep reading and sending messages from other providers inside Gmail on phones and tablets. However, the web/browser Gmail experience will not allow continuous IMAP linking for third‑party accounts — the web client’s “check mail from other accounts” removal applies to POP3 fetch only. Google’s help text points users to forwarding and the mobile IMAP option as the primary alternatives.

---

Why Google is doing this — the case for security and sync parity​

Google’s public explanation frames the change as an attempt to “provide the most secure and current options to access your messages in Gmail.” POP3 is old by Internet standards: it was designed for single‑device download behavior, lacks robust sync semantics, and historically has been used with weaker authentication patterns. Security commentators and technical writers point out that POP3 configurations can risk plaintext credential exposure and generally do not support modern multi‑device sync or advanced server‑side protections the way IMAP does. That said, Google’s help page does not present a detailed technical incident or single vulnerability that prompted the sunset; instead it frames the change as an alignment with stronger, more current protocols (IMAP) and service models that allow Gmail to keep applying its spam and safety features reliably. Where specific security claims are made by third parties (for example, that POP3 “shares passwords in plaintext” in all configurations), those are contextually accurate for many legacy deployments but depend on how an external provider implements encryption (SSL/TLS, STARTTLS) and authentication. Readers should treat general security‑reasoning as strongly suggestive rather than an account of a single confirmed exploit.

---

Who this affects most — consumers vs. businesses​

Consumers and individual users​

• Most immediately affected are people who used Gmail’s web fetch to consolidate multiple third‑party addresses (ISP mail, small hosting accounts, personal Yahoo or Outlook accounts) into a single Gmail inbox. Those owners will lose continuous fetch on the web; the mobile app IMAP option remains, but mobile access alone may be insufficient for users who depend on the browser or desktop Gmail for full workflow.
• Gmailify users will lose the extra Gmail protections (spam filtering, inbox categories and enhanced notifications) for eligible third‑party accounts; that often means more spam or less precise sorting unless the user configures equivalent protections with their third‑party provider or migrates mail to Gmail.

Businesses, schools and managed accounts​

• Enterprises are in a better position: Google’s Workspace migration tooling and migration services are designed to bring email, calendar and contact data into Workspace accounts at scale. Google’s Data Migration Service and other Workspace migration tools are available for admins and can handle IMAP sources, Microsoft Exchange and a variety of enterprise environments. For businesses, the move is framed as an opportunity to consolidate onto Workspace with vendor‑supported migration paths and partner services.

---

Practical impact: features lost, features kept​

• Lost for Gmailified/POP‑fetched third‑party accounts in Gmail on the web:
• Spam protection applied by Gmail (Gmailify)
• Enhanced mobile notifications supplied by Gmailify
• Inbox categories (Primary, Social, Promotions) applied by Gmailify
• Advanced Gmail search operators applied natively to the third‑party mailbox via Gmailify
• Continuous POP3 fetch into Gmail on the web (the “Check mail from other accounts” option)
• Web‑based synchronization using POP3 (POP is not a sync protocol like IMAP)
• Still possible:
• Add third‑party accounts to Gmail mobile app via IMAP to keep reading and sending from those accounts on mobile.
• One‑time import of mail and contacts on the web (not continuous sync).
• Use third‑party desktop clients (Thunderbird, Outlook) that support IMAP to consolidate mailboxes on desktop.
• Set up forwarding on the third‑party provider so new mail is pushed to Gmail (forwarding must be offered by the third‑party service).

---

Step‑by‑step: what affected users should do now​

Follow these prioritized actions to preserve inbox continuity and avoid service disruption after January 2026.

• Inventory: Identify every third‑party account you currently receive in Gmail via POP3 or Gmailify.
• Look in Gmail Settings → Accounts and import → “Check mail from other accounts” and “Gmailify” sections.
• Back up: Export or archive important mail now with Google Takeout or your local mail client. Messages already imported into Gmail will remain, but a local backup reduces risk during any migration.
• Enable IMAP on your third‑party provider (if supported) and add the account to the Gmail mobile app. The Gmail help center includes mobile setup instructions. If IMAP isn’t offered, proceed to step 4.
• Set up forwarding at the originating mail provider to your Gmail address if you want browser‑side continuity. Forwarding will deliver new mail to Gmail like POP fetch did, but you must configure it with the external provider and confirm forwarding rules.
• Consider migrating to Google Workspace if you represent a business or a managed domain; admins can use Google’s Data Migration Service or partner migration tools for large or complex moves. Workspace migration preserves mail, calendars and often permissions when done correctly.
• If you rely on Gmailify for spam filtering on a non‑Gmail provider, implement equivalent spam controls at your provider or move mail into Gmail itself to keep Google’s protections. Alternatively, adopt a stronger desktop/mobile client with integrated spam filtering rules.

---

Alternatives and workarounds​

• Use the Gmail mobile app + IMAP: For users who primarily check mail on phones or tablets, adding the third‑party account to the Gmail mobile app with IMAP will preserve access and allow Gmail to send/receive from that account on mobile devices. This does not restore web fetch capabilities.
• Configure server‑side forwarding at the third‑party host: Forwarding is the closest replacement for continuous fetch on the web; it pushes incoming mail into Gmail as it arrives and keeps the Gmail web interface as your single inbox. Be mindful of forwarding rules, SPF/DKIM/DMARC implications for outbound mail, and how replies appear to recipients (reply‑from address behavior varies).
• Use a dedicated desktop client with IMAP support: If you need desktop consolidation, clients such as Mozilla Thunderbird or Outlook configured to use IMAP for each account replicate a multi‑account workflow similar to Gmail’s fetch but under your control. This is a practical alternative for users unwilling to forward mail or migrate.
• Migrate to Google Workspace or another provider: For businesses and power users, a controlled migration to Workspace preserves many Gmail features and is supported by Google’s migration tooling and partner ecosystem.

---

Technical details and caveats IT teams should note​

• POP3 is not inherently insecure if configured with TLS and modern authentication, but many legacy deployments and consumer ISPs still use configurations that are less robust than IMAP with modern auth. Therefore, Google’s blanket removal of POP3 fetch in Gmail on the web prioritizes a consistent security posture across a heterogenous set of external mailboxes. That reasoning aligns with security analysis by independent outlets, though precise implementation risk varies by provider. Treat specific security‑severity claims as context‑dependent rather than universally absolute.
• Forwarding and reply behavior: When you forward messages into Gmail, replies from Gmail may come from your Gmail address by default. Configuring “Send mail as” in Gmail allows you to send from another address, but that setup often requires SMTP credentials for the external domain. Ensure you test send/email authentication (SPF, DKIM, DMARC) so outbound mail doesn’t get flagged or rejected.
• One‑time imports vs continuous sync: Google’s web interface will still permit a one‑time import of messages and contacts from another account, but this is a snapshot operation — not a continuous sync. Users who relied on Gmail’s periodic POP fetch for live consolidation must move to IMAP or forwarding for continuity.

---

Strengths of Google’s decision (analysis)​

• Security posture improvement. Removing a legacy fetch mechanism reduces one class of cross‑provider authentication surface that Google must account for; it simplifies Gmail’s threat model and allows Google to standardize on protocols it can secure and support consistently.
• Simplifies product support and product parity. Gradually removing older, single‑device protocols helps maintain consistent feature behavior across web and mobile interfaces and reduces the variety of integrations Gmail must maintain and test.
• Cleaner migration funnel for businesses. For organizations, the change clarifies the path: either migrate to Workspace with Google’s data migration tools or use IMAP/forwarding. Google’s Workspace migration tooling and partner ecosystem make large migrations manageable and auditable.

---

Potential risks, downsides and user harms​

• Consumer friction and loss of convenience. Many casual users relied on Gmail’s fetch capability as a low‑touch merge tool. Removing it without a browser IMAP alternative forces users into steps they may not understand: enabling IMAP, configuring forwarding, or switching apps. That creates immediate friction and potential support calls for small hosts and ISPs.
• Loss of Gmail’s protective layer for third‑party mail. Gmailify was a rare convenience: it applied Gmail’s advanced spam filters to eligible external accounts. Losing that protection may increase spam exposure for users who don’t configure equivalent filters on their third‑party host.
• Ambiguity for certain edge cases. Not every hosting provider supports IMAP or forwarding, and some corporate policies prohibit forwarding to external addresses. For users in those situations, the pathway may be complex and may require paid migration services or admin intervention. These real‑world edge cases are likely to affect users of smaller or legacy hosting setups disproportionately.
• Support and phishing risk during transition. Major account‑level changes create windows for phishing and social‑engineering attacks. Users setting up forwarding or changing mail clients may be targeted with fake help pages; organizations should include guidance and warnings in staff communications.

---

Recommendations for IT support teams and power users​

• Prepare a short, prescriptive internal playbook that:
• Identifies impacted accounts and owners.
• Offers a standard migration path (forwarding + Send As SMTP config, mobile IMAP, or formal Workspace migration).
• Includes a checklist to validate SPF/DKIM/DMARC before and after forwarding or Send As changes.
• Stage the change: perform pilot migrations and test mailbox behavior for reply‑from address, calendar invites, and shared Drive/Docs ownership if a mailbox is moved to Workspace.
• Educate users on distinguishing legitimate Google notices from phishing (two‑factor authentication, official Google Help links, and the Gmail settings UI).
• For small hosting providers: publish clear guidance on how customers can set up forwarding and IMAP, and consider partnering with migration services to offer a paid migration path.

---

What to watch next (timeline and signals)​

• January 2026 — the public cutover window. Google’s help text uses “Starting January 2026” rather than a specific day in most languages; users should treat January 1, 2026 as the operational start of the deprecation window unless their account UI shows alternative messaging. Check your Google Account notifications and Gmail settings for account‑specific timelines.
• Watch for follow‑on clarifications from Google about the precise rollout per region and language; early coverage showed some localized support pages surfacing detailed numeric or timing guidance before the central pages did. Confirm the guidance shown inside your account or admin console.

---

Bottom line — what WindowsForum readers should know​

Google’s decision to retire POP3 fetch and Gmailify is a pragmatic, security‑focused narrowing of Gmail’s integration surface that benefits Google’s ability to provide consistent protections and support across devices. For businesses, the move is manageable: Workspace’s migration tools and third‑party partners give admins clear, supported options to consolidate mail. For consumers and small hosting customers, however, the change removes a convenient, low‑effort way to centralize mail and hands them a choice: adopt IMAP in the Gmail mobile app, configure forwarding at the source, use a desktop IMAP client, or migrate mail to Gmail/Workspace.
Prepare now: inventory accounts, back up mail, and decide whether forwarding, mobile IMAP, or a formal migration is the right long‑term solution. The deprecation won’t delete mail already fetched, but it will remove future convenience for many users — and that’s a change that benefits from planning rather than surprise.

---

The practical next steps are simple and immediate: audit the accounts you access through Gmail, back up any irreplaceable messages, and pick the replacement path that fits your usage (forwarding, IMAP in mobile, desktop IMAP client, or migration to Workspace). Doing so now avoids disruption when Gmail’s POP3 and Gmailify support ends in January 2026.

---

Source: TechRadar Google set to end POP3 support - here's what we know