Google has confirmed that Gmail will stop supporting the “Send as” feature for third-party email addresses beginning January 2027, ending a long-standing workaround that let users send mail from Yahoo, Outlook, or custom-domain accounts without ever leaving their Gmail inbox.
What’s changing
“Send as” lets a Gmail user verify ownership of an outside address and then compose messages that appear to come from that address, even though they’re sent through Gmail’s interface. Starting in January 2027, that will no longer work for non-Google addresses, on either the web version of Gmail or the Android and iOS apps.
The change also affects two related features:
- Gmailify, which let Gmail apply its spam filtering and inbox organization tools to mail pulled in from outside providers
- Web-based POP fetching, the “Check mail from other accounts” feature that imported messages from third-party inboxes into Gmail
Google says the decision comes down to maintenance cost, describing the affected features as requiring “disproportionate” engineering resources to keep running securely.
What isn’t affected
The rollback is limited to personal Gmail accounts using genuinely external addresses. A few things stay exactly as they are:
- Google Workspace users — anyone on a paid Workspace plan keeps full “Send as” functionality, including for external domains
- Gmail-to-Gmail aliases — sending as another Gmail address you own, or a Workspace alias, is unaffected
- Receiving mail — messages already imported into Gmail remain there, and the mobile app will still let users check third-party accounts; only sending and new syncing are cut off
- SMTP itself — the underlying protocol Gmail used to send on a user’s behalf isn’t going away, so desktop clients like Outlook or Thunderbird, or the third-party provider’s own app, remain unaffected alternatives
Rollout timeline
Google is phasing the change in over roughly six months rather than switching it off all at once:
- Now through late 2026 — in-product notices are going out to affected users, and Google has already blocked anyone from setting up a new “Send as” configuration for a third-party address
- Through the rest of 2026 — existing configurations keep working as before
- January 2027 — third-party “Send as,” Gmailify, and web-based POP fetching stop working entirely for personal accounts
Why it matters
For years, Gmail functioned as a free, unified front end for people juggling several email identities — an old Hotmail address, a side-business domain, a personal Yahoo account — all sent and received from one inbox. That convenience disappears for anyone not paying for Workspace. Users who want to keep sending from a non-Gmail address after January 2027 will need to move to a dedicated mail client, use the provider’s own web app or app directly, or upgrade to a paid Google plan.
Reaction since the announcement has been largely negative among longtime “Send as” users, particularly small business owners and people managing multiple personal domains through a single free Gmail account, many of whom say the change forces an unwanted migration or a move to a paid plan.
What affected users should do
Google’s guidance is straightforward: don’t set up any new “Send as” configuration for a third-party address, since new setups are already restricted ahead of the deadline. Existing configurations will keep working until January 2027, giving current users time to plan a move to a desktop email client, the provider’s own app, or a Google Workspace subscription before the cutoff.
