Essay · 11 min read
Gmail's 2027 POP3 and Send-As changes and what breaks.
Google is retiring Gmail Web 'Check mail from other accounts' and tightening third-party Send-As in January 2027. See what breaks and how to migrate.
For more than fifteen years, one of the most popular cost-saving hacks for budget-conscious founders was using personal Gmail as a free email client for custom business domains. The playbook was well-known: buy a domain at a registrar, configure free email forwarding to personal Gmail, connect Gmail's 'Check mail from other accounts' via POP3, and configure a 'Send As' custom SMTP relay.
Google has formally announced the end of this era. According to Google's published account support updates, Google will permanently retire the 'Check mail from other accounts' (POP3) feature in Gmail on the web starting in January 2027. Additionally, Google is strictly enforcing modern authentication (OAuth 2.0) and DMARC alignment on all outbound SMTP relay connections, rendering unaligned 'Send As' aliases obsolete.
If your business operations currently rely on personal Gmail to triage custom domain email, your workflow will break when Google disables these endpoints. This guide details what is changing, why Google is making the move, and how to execute a clean, permanent migration to professional multi-domain hosting ahead of the deadline.
What breaks versus what continues working.
To avoid unnecessary panic, it is important to distinguish between the specific legacy protocols Google is retiring and the modern features that remain supported:
| Gmail Feature & Workflow | Technology / Protocol | Status as of January 2027 | Impact on Solo Founders & Operators |
|---|---|---|---|
| Check mail from other accounts (Web) | Legacy POP3 (RFC 1939) | Permanently Retired | Gmail Web will no longer fetch mail from external email hosts or cPanel servers |
| Third-party SMTP 'Send As' (Web) | Legacy SMTP authentication | Strictly Restricted / Sunset | Unaligned relays without OAuth 2.0 fail; DMARC misalignment triggers spam flags |
| Google Workspace Alias Domains | Native Google infrastructure | Fully Supported | Workspace user alias domains managed in Google Admin Console continue working |
| Gmail Mobile App (iOS / Android) | Modern IMAP / EAS protocols | Fully Supported | Mobile app connections to external IMAP accounts remain functional |
| Dedicated Multi-Domain Hosting (Folio) | Native cloud webmail & API | Fully Supported | Complete multi-domain inbox with automatic From matching and 2048-bit DKIM |
Scroll to see every column →
Why Google is deprecating legacy POP3 and third-party SMTP.
Google's decision to retire POP3 fetching and restrict external SMTP relay is not an arbitrary attempt to force users into paid Workspace plans; it is the culmination of a decade-long security migration across the internet ecosystem:
- ·1. Password-based authentication vulnerabilities: Legacy POP3 and basic SMTP rely on plain-text or password-based credentials stored on Google's servers. Modern security architecture requires token-based OAuth 2.0 authentication with multi-factor verification.
- ·2. Strict DMARC enforcement: When users send mail through Gmail's 'Send As' feature using a custom domain, Google's servers attempt to send as an external domain. Unless complex reverse DNS and SPF alignment are maintained, messages fail strict DMARC checks (RFC 7489), damaging sender reputations.
- ·3. Spam and malware ingestion: POP3 downloads mail blindly into an inbox without real-time connection-level reputation checks. By eliminating POP3 fetching, Google forces all external mail through standard MX transmission where edge spam filtering can evaluate connecting IP reputations in real time.
Four migration paths ahead of the 2027 deadline.
If you currently manage business email through personal Gmail forwarding and POP3 fetching, you have four distinct architectural paths forward:
- 01Upgrade to paid Google Workspace seats: You can purchase a Google Workspace Business Starter account for each business domain you own at $7 per user per month ($84/user/year). This provides a native Google experience but becomes expensive ($420/year for 5 domains) and forces you to log into separate Google accounts for each brand.
- 02Consolidate under Workspace alias domains: If you already pay for one Google Workspace account, you can add up to 20 secondary domains as user alias domains at no extra charge. All mail delivers to your primary inbox, but all brands share the same storage, login, and primary DKIM key.
- 03Switch to desktop IMAP software: You can host your mail on budget IMAP servers (like Purelymail at $10/yr) and read your email inside desktop applications like Apple Mail or Thunderbird. You avoid Google's web retirement, but must configure ports and server settings manually across all your computers and phones.
- 04Migrate to a dedicated multi-domain webmail platform: You can move your domains to Folio. Folio provides flat operator pricing ($2.99/mo for 3 domains, $12/mo for 10 domains), dedicated 2048-bit DKIM keys per domain, and automatic reply-From matching in a modern browser webmail interface, completely replacing the fragile Gmail POP3 hack with enterprise-grade email infrastructure.
Step-by-step migration playbook before January 2027.
To transition your business domains before Google shuts down its legacy endpoints, follow this orderly migration sequence:
- 01Inventory your existing 'Send As' and POP3 accounts: Open Gmail on your computer, navigate to Settings > Accounts and Import, and review every entry under 'Send mail as' and 'Check mail from other accounts'. Note which domains and addresses are active.
- 02Select and configure your new mail host: Set up your custom domains in your new email platform. If using Folio, connect your domains and verify that your desired role addresses (e.g.
alex@company.com,billing@company.com) are provisioned. - 03Repoint your domain MX and authentication records: In your domain registrar's DNS manager, replace your old MX forwarding records with your new mail host's authoritative MX records. Update your SPF TXT record per RFC 7208 and publish your unique DKIM keys per RFC 6376.
- 04Verify delivery using DNS diagnostic tools: Use Folio's free domain health checker to ensure all DNS records resolve globally with passing verdicts.
- 05Clean up legacy Gmail settings: Once your new mail host is receiving mail, return to Gmail Settings > Accounts and Import. Delete the legacy POP3 entries under 'Check mail from other accounts' and remove third-party 'Send As' aliases to prevent conflicting delivery loops.
The evolution of email protocols: Why POP3 is obsolete.
To appreciate why Google is deprecating 'Check mail from other accounts', it helps to understand the history of the Post Office Protocol (POP3). Standardized in 1988 and refined in RFC 1939 (1996), POP3 was designed for an era when personal computers connected to the internet intermittently over dial-up modems. The protocol's primary design goal was downloading unread messages from a remote mail server to a local hard drive and deleting them from the server.
In a modern multi-device world where users read email across laptops, smartphones, tablets, and smartwatches, POP3 is fundamentally broken. It does not synchronize read states, sent folders, draft messages, or server-side flags. When Gmail on the web fetches mail via POP3, it essentially acts as a batch client, polling remote mail servers every 15 to 60 minutes. This introduces unpredictable delivery delays for time-sensitive customer communications.
Furthermore, POP3 connections authenticate using static, unencrypted or basic TLS-wrapped username and password strings. Google has been systematically deprecating 'Less Secure Apps' across its entire ecosystem in favor of modern OAuth 2.0 token-based handshakes with hardware-backed WebAuthn passkey support. Shutting down the web POP3 fetcher eliminates a massive vector for credential stuffing and brute-force authentication attacks.
Why the Gmail mobile app behaves differently than webmail.
A common point of confusion among founders is why the Gmail app on iPhone or Android continues to work with external accounts while Gmail on desktop browsers is losing the capability. The reason lies in protocol architecture.
When you add an external email account to the Gmail mobile app, the mobile app acts as a local IMAP client on your device. Your phone connects directly to your external email host over port 993, synchronizes messages in real time via IMAP IDLE, and dispatches outbound replies directly through your host's SMTP server over port 465 or 587. Google's central servers are never in the middle of the transport connection.
In contrast, 'Check mail from other accounts' on Gmail web operates server-to-server: Google's cloud infrastructure logs into your external mail server, downloads messages into Google's data centers, and stores them in your Google database. It is this server-side proxying of unauthenticated external mail that Google is terminating in January 2027.
Historical message archiving and data sovereignty.
Before Google deactivates POP3 fetching in January 2027, founders should verify that all historical correspondence is safely archived. When using POP3, messages downloaded into Gmail web generally remain stored in your Google account. However, if your external mail server had a 'delete from server after download' rule enabled, your external host may hold zero historical records.
Before cutting over DNS records, perform a full Google Takeout export of your Gmail archive in standard MBOX format. Modern email hosts like Folio allow you to import existing mailbox history directly over IMAP, ensuring that years of client threads, attachments, and invoices transfer seamlessly into your new multi-domain inbox without missing a single conversation. Once imported, your entire email archive becomes instantly searchable across all your domains without relying on Google\'s cloud.
Future-proofing your email infrastructure for the next decade.
Rather than scrambling to find another temporary hack or third-party forwarding proxy when Google terminates POP3 in January 2027, founders should view this deadline as an opportunity to establish permanent, professional email infrastructure.
Modern businesses require dedicated domain identity, authenticated cryptographic signing (2048-bit DKIM), and responsive multi-domain triaging. Moving away from consumer Gmail workarounds eliminates the constant anxiety that a platform policy shift or authentication update will suddenly break your client communication channels.
To compare features and daily workflows across providers, review our Folio vs. Gmail aliases comparison and our guide on custom domain email without Google Workspace. For multi-domain cost breakdowns, explore the multi-domain email price index, or view full plan capabilities on Folio's pricing page.
Questions readers ask
What exactly is Google retiring in Gmail web in January 2027?
Google is retiring the 'Check mail from other accounts' feature in Gmail on the web, which uses POP3 to fetch messages from external email providers. Google is also tightening third-party 'Send As' configurations that rely on unaligned external SMTP servers.
Will Google Workspace alias domains stop working in 2027?
No. Native Google Workspace user alias domains and secondary domains managed inside the Google Workspace Admin Console are unaffected and will continue to function normally.
Does the January 2027 change affect the Gmail mobile app on iOS and Android?
No. The Gmail mobile app connects to external email providers using modern IMAP and standard mobile protocols, which are not being deprecated. Only the webmail-based POP3 fetcher in desktop browsers is shutting down.
How can I keep receiving and replying from custom domains without POP3?
Move your custom domains to a modern email host that provides native multi-domain webmail or full IMAP support. Folio provides a single inbox that hosts multiple domains natively with automatic reply-From matching and per-domain DKIM signing.
Sources & further reading
§ Google Search
Make Folio a preferred source.
If you read Folio often, add it as a preferred source. Google can then mark our writing as preferred in Top Stories, AI Overviews, and AI Mode for you.
Change or remove it any time in Google’s source preferences.