· via dev.to (home feed)
Gmail to drop Send Mail As, POP fetching and Gmailify in January 2027
Google will fully remove Gmail's Send Mail As for third-party addresses, POP account fetching and Gmailify by January 2027. Custom-domain users who send business mail from a personal Gmail account will need another route.

What is changing
Google is removing three features that let a personal Gmail account act as the hub for mail hosted elsewhere, according to a write-up on dev.to that quotes Google's Gmail Help pages. The features on the way out are "Send mail as" for addresses not hosted by Google, "Check mail from other accounts", which fetches mail from another server over POP, and Gmailify, which applies Gmail's spam filtering, inbox categories and mobile notifications to a linked third-party account.
Google's documentation, as quoted in the article, says users will no longer be able to send from third-party accounts either in Gmail on the web or in the Gmail mobile apps. The examples given for affected addresses include @hotmail.com and @yahoo.com, along with any custom domain whose mail is not hosted by Google. The Gmailify page lists what linked accounts lose: spam protection, better mobile notifications, inbox categories and faster search with advanced operators.
The timeline
The dev.to article's author says the Google help pages were read on 5 November 2026, and assembles this schedule:
- After the first quarter of 2026, Gmailify and POP stopped supporting new users, while existing users could continue.
- In Q3 2026, the "Send as" announcement and notice period began, with in-product notifications going to affected users.
- Q3 to Q4 2026 is a transition period: all three features still work, but Gmail may restrict new configurations, and Google encourages migration during this window.
- In January 2027, Gmail fully removes "Send as" for third-party accounts, Gmailify and POP.
Google gives quarters and a month, not exact days. The practical point the write-up draws from the transition row is that a current setup keeps working, but the same configuration may not be creatable again later, so any rebuild should happen while the features still function. The same page also notes that adding or syncing a third-party account in Gmail on the web was already announced as ending.
What is unaffected
Several adjacent capabilities survive, according to the same pages:
- Mail already imported from a third-party account stays in the mailbox; nothing is deleted.
- "Send as" for other Gmail addresses and for aliases in a Google Workspace account keeps working.
- A third-party provider can auto-forward mail into Gmail, which Google calls independent of "Send as" and unaffected.
- Non-Google accounts added in the Gmail apps for Android and iOS continue to work as they do today.
- IMAP and POP remain fully supported for reading Gmail from clients such as Outlook, Thunderbird and Apple Mail.
- The one-time "Import mail and contacts" tool still exists, though messages do not sync continuously.
The setup that breaks
The classic arrangement described in the article is mail to an address like hello@yourdomain fetched into Gmail, with replies sent from Gmail carrying the domain address in the From line. After January 2027, mail arriving through POP stops, and the custom address disappears from the From menu.
The failure mode that is easy to miss is quieter than a total outage. An owner who fixes only receiving, by switching to forwarding, will still see mail arrive and hit reply as usual, but replies will go out from the personal Gmail address rather than the business address, the one printed on invoices and every customer thread.
On routing services such as Cloudflare Email Routing, the article notes that Google's pages name no providers. The author's reading is that a domain whose mail is handled outside Google counts as third-party: the forwarding half survives, while the "Send as" half goes.
How to check
In Gmail on the web, open Settings, then "See all settings", then the "Accounts and import" tab, which Google says may be labelled "Accounts" instead. Any address in the "Send mail as" section that is not a Gmail or Google Workspace address means the account is affected, and anything listed under "Check mail from other accounts" is POP fetching, which is also being removed. Receiving has a direct replacement: set the domain's provider to auto-forward into Gmail and remove the POP connection. Sending is the half that requires a decision, since the boundary Google draws is whether an address is hosted by Google.
Why it matters
Plenty of small businesses run their entire email presence inside a free personal Gmail account using exactly these features, and the change forces a migration decision before January 2027. The receiving side is a straightforward swap to forwarding, but the sending side has no like-for-like replacement for third-party addresses, pointing owners toward hosting their domain mail with Google or sending through another service. The danger of inaction is subtle rather than dramatic: mail keeps flowing, but outbound replies silently carry the wrong identity, undermining the professional front a custom domain was meant to provide. Because a setup dismantled after the cut-off may not be rebuildable, the transition window is the time to act.
- #gmail
- #custom-domain
- #small-business