Google has set a date for one of the biggest changes to hit the Gmail ecosystem in years. According to the company’s own support documentation, starting in January 2027 Gmail will stop supporting three features that millions of people use to manage third-party email from a Gmail interface: the Send as feature for non-Google addresses, Gmailify, and Check mail from other accounts, which pulls messages into Gmail over POP.
The change does not touch Gmail to Gmail aliases or Google Workspace Send as for Google hosted identities. It also leaves the Gmail mobile app alone, so third-party accounts added on Android, iPhone and iPad keep working through standard IMAP connections. External clients such as Outlook, Thunderbird and Apple Mail can also keep reaching Gmail over IMAP, POP and the Gmail API. What disappears is the ability to run a non-Google mailbox from Gmail on the web.
What Google is removing and when
The timeline published by Google runs in three steps. In the third quarter of 2026 the announcement period began and affected users received an in-product notification. Through the third and fourth quarters of 2026 the features keep working, but Gmail may restrict new configurations, and Google encourages affected users to migrate during this window. In January 2027 the removal becomes final for Send as with third-party accounts, Gmailify and POP fetching.
Google lists the affected pieces precisely. Send as let a Gmail user send mail from an address such as hotmail.com or yahoo.com, or from a work alias hosted elsewhere. Gmailify applied Gmail features like spam protection, inbox categories and advanced search operators to a third-party account. Check mail from other accounts fetched messages from an external mailbox into Gmail using POP.
Two reassuring points also come straight from the documentation. Messages already imported into Gmail stay in the mailbox, and automatic forwarding from a third-party provider into Gmail keeps working, because it is configured on the provider side. For businesses that relied on Send as, Google recommends moving to the provider’s own interface, a desktop client connected over IMAP and SMTP, or the Gmail mobile app, and for custom domain sending it points to Google Workspace.
Google also issues a warning worth quoting in every security briefing: third-party tools and browser extensions that promise to replicate Send as often demand access to email credentials or OAuth tokens, and Google cannot vouch for their safety. That is a standing invitation for account takeover, not a migration path.
Why this is quietly good news for deliverability
For email marketers and domain owners, the shutdown closes a pattern that has damaged sender reputation for years. When someone sends a message from a Gmail account but stamps a different domain in the From header, the underlying SMTP submission comes from Google’s infrastructure, not the domain owner’s. That breaks the alignment between the From domain and the SPF or DKIM signatures that DMARC checks, so the message either fails the domain’s DMARC policy or gets classified on signals other than clean authentication.
In practice this created a strange split. A domain could publish a strict DMARC policy with p=reject, pass every test run by its actual sending infrastructure, and still see confused or spoofed looking mail emerging from personal Gmail accounts that claimed to be its staff, support desk or founder. Removing third-party Send as from Gmail on the web pushes senders toward setups where the From address and the authenticating domain agree, which is exactly the direction Gmail, Yahoo and Microsoft have been driving the entire industry since the bulk sender requirements landed.
If you operate a brand, treat January 2027 as an audit trigger. Inventory every person, team or agency that currently sends as your domain from a personal Gmail inbox. Move those sends to infrastructure that actually belongs to your domain, with SPF, DKIM and DMARC alignment verified, and to a provider where you control the authentication. Then read your DMARC aggregate reports to confirm that after the migration nothing is still sending as your domain from unexpected places.
The same audit applies in reverse for inbound teams. After January 2027, expect fewer legitimate messages arriving through POP fetched accounts, and make sure your help desk does not mistake the disappearance of a familiar sending pattern for suspicious behavior.
Excello Mail helps you bring every sending source for your domains under control, verify SPF, DKIM and DMARC alignment, and monitor aggregate reports so you know exactly who is sending as you before Gmail’s January 2027 deadline arrives. Sign up for free to Excello Mail and make the migration on your own terms.