Google is sunsetting core Gmail features by January 2027, eliminating the “Send As” function for external addresses and halting POP synchronization for non-Google accounts. According to reporting from DroidApp and Tweakers, users who rely on Gmail as a centralized hub for multiple external email providers must reconfigure their workflows before the deadline.
The Technical Anatomy of the Deprecation
For decades, power users exploited Gmail’s architectural flexibility to ingest mail from disparate servers via Post Office Protocol (POP) and relay outbound messages through third-party Simple Mail Transfer Protocol (SMTP) relays via the “Send As” feature. Google has confirmed in its official documentation that this era of multi-provider consolidation is drawing to a close. New users lost the ability to add external POP accounts after the first quarter of 2026, while existing configurations face a hard cutoff in January 2027.
The decision targets features that demand continuous server-side polling and protocol maintenance.
What Remains: Mobile IMAP and Automatic Forwarding
The elimination of server-side POP syncing does not mean users must abandon their secondary mailboxes entirely, though the underlying data flow changes fundamentally. According to DroidApp, the mobile Gmail app for Android, iOS, and iPadOS will continue to support multiple external accounts—such as Outlook or Yahoo—by managing them via standard Internet Message Access Protocol (IMAP) connections. Unlike the legacy POP system, IMAP keeps the mailbox states tethered directly to the remote server without ingesting the bulk message store into the primary Gmail database.
For users committed to keeping their desktop web interface centralized, Google points toward automated forwarding. Users can configure external mail providers to instantly push incoming messages directly to a primary Gmail address. However, this workaround splits the pipeline: incoming mail can be forwarded, but replying natively from the Gmail web client using an external domain as the sender will break once the “Send As” functionality for external domains is officially retired.
Migration Paths for Professional and Custom Domain Users
The structural changes hit professionals and custom domain holders hardest. Anyone running a personal brand or small business on an independent domain routed through Gmail must audit their mail architecture now. Existing historical archives remain untouched; Google explicitly notes that previously synchronized emails will not be scrubbed from storage, and a one-time import utility remains available for migrating old archives and contacts.
Enterprise IT administrators and independent power users now face three distinct paths forward:
- Migrate entirely to the native webmail client of the external domain provider.
- Transition to a dedicated desktop or mobile mail client capable of unifying multiple IMAP and SMTP streams locally.
- Set up server-side forwarding rules to push inbound mail to Gmail while accepting that outbound routing must happen elsewhere.
With the January 2027 deadline approaching, the multi-account aggregation model that defined Gmail’s utility for power users is officially yielding to a more siloed ecosystem architecture.
