Feature
Gmail is discontinuing three features for third-party (non-Google) email accounts on the web — "Send as" (sending from a non-Google address like an @outlook.com or @yahoo.com account), Gmailify, and POP fetching of external mail into the Gmail web interface — with full removal in January 2027. Google-hosted addresses (Gmail and Workspace) and the Gmail mobile app are not affected.
departs 1 Jan 2027
Quick answers
- Is it true that Gmail removes "Send as", Gmailify and POP for third-party accounts on the web in January 2027?
- Yes. Google has officially announced it, effective 1 Jan 2027. For years Gmail on the web has let you wire up a non-Google email account — an @outlook.com, @yahoo.com, or work address on another provider — and treat Gmail as the front end for it: send outgoing mail so it appears "from" that address ("Send as"), pull that account's messages into your inbox over POP, and get Gmail's spam and inbox features applied to it (Gmailify).
- When does it take effect?
- 1 Jan 2027. Verified against the vendor's own announcement.
- What should I use instead?
- Google names three alternatives for keeping access to a third-party account once the web features are gone.
What this means for you
For years Gmail on the web has let you wire up a non-Google email account — an @outlook.com, @yahoo.com, or work address on another provider — and treat Gmail as the front end for it: send outgoing mail so it appears "from" that address ("Send as"), pull that account's messages into your inbox over POP, and get Gmail's spam and inbox features applied to it (Gmailify). Google is removing all three of those for third-party accounts on the web. Per its support page the rollout is staged: in Q3 2026 affected users get an in-product notification; across Q3–Q4 2026 Gmail may stop allowing new configurations of these features and encourages people to migrate; and in January 2027 the features are fully removed. Who this hits: anyone who runs a non-Google mailbox through Gmail's web interface — people who reply from an old ISP or work address inside Gmail, or who consolidate several external accounts into one Gmail tab. What it does NOT touch: "Send as" for Gmail or Google Workspace addresses and aliases keeps working; the Gmail mobile app for Android, iPhone and iPad can still add and use non-Google accounts as before; other clients (Outlook, Thunderbird, Apple Mail) can still reach your Gmail over IMAP/POP; and forwarding from a third-party provider into Gmail is unaffected. The change is specifically about sending from, and fetching into, Gmail on the web for non-Google accounts.
Where to go
Google names three alternatives for keeping access to a third-party account once the web features are gone. Simplest is to use that provider's own website or app directly for sending and reading its mail. If you want everything in one desktop client, set the account up over IMAP/SMTP in a mail app such as Outlook, Thunderbird, or Apple Mail — those protocols are unaffected. And the Gmail mobile app still supports adding non-Google accounts, so a phone or tablet can keep the consolidated-inbox experience the web is losing. Before January 2027, take an inventory: open Gmail's Settings → "Accounts and Import" and note every "Send mail as" entry and POP account that points at a non-Google address, since those are the ones that stop working on the web. If you rely on sending "from" an external address, decide now whether you'll move that sending into the provider's own service or a desktop client, and update any saved filters or workflows that assume the mail flows through Gmail on the web.
- The third-party provider's own website or app — Google's first suggested path for sending and reading that account's mail directly
- A desktop mail client (Outlook, Thunderbird, Apple Mail) configured over IMAP/SMTP — unaffected by this change
- The Gmail mobile app — still supports adding and using non-Google accounts
Gmail on the web is dropping support for running a non-Google email account through it. On its official Gmail Help page, Google says three features will be removed for third-party (non-Google) accounts: “Send as” — sending outgoing mail that appears to come from an external address like an @outlook.com or @yahoo.com account; Gmailify — applying Gmail’s spam filtering and inbox features to an external account; and POP fetching of that account’s mail into the Gmail web interface.
The timeline
Google describes a staged rollout rather than a single cut-off:
- Q3 2026 — affected users receive an in-product notification.
- Q3–Q4 2026 — Gmail may stop allowing new configurations of these features; Google encourages migrating during this window.
- January 2027 — the features are fully removed for third-party accounts.
Google gives the month, not a specific day, so treat “January 2027” as the horizon rather than a precise deadline. The countdown on this entry uses the start of that month.
Who this affects — and who it doesn’t
This hits people who use Gmail on the web as the front end for a mailbox that lives somewhere else: replying from an old ISP or work address inside Gmail, or pulling several external accounts into one Gmail inbox.
It does not affect:
- “Send as” for Gmail or Google Workspace addresses and aliases — those keep working.
- The Gmail mobile app (Android, iPhone, iPad) — it can still add and use non-Google accounts.
- Reaching your Gmail from other clients (Outlook, Thunderbird, Apple Mail) over IMAP/POP — unaffected.
- Forwarding from a third-party provider into Gmail — unaffected.
The change is narrowly about sending from, and POP-fetching into, Gmail on the web for non-Google accounts.
What to do
Google points to three alternatives. Use the third-party provider’s own website or app directly; set the account up in a desktop mail client over IMAP/SMTP; or use the Gmail mobile app, which still supports non-Google accounts. Before January 2027, open Gmail’s Settings → “Accounts and Import” and note every “Send mail as” entry and POP account pointing at a non-Google address — those are the ones that stop working on the web — then move that sending or fetching into one of the alternatives and update any filters or workflows that assumed the mail flowed through Gmail on the web.
This entry tracks Google’s official Gmail Help page; if Google names a specific day or changes the plan, the entry will be updated with a changelog note.
Entry changelog
- — last reviewed.
- — Entry created from Google's official Gmail Help page ("Learn about changes to third-party email account support in Gmail"). Google states the three affected features (Send as for third-party accounts, Gmailify, and POP on the web) are fully removed in January 2027, preceded by an in-product notification in Q3 2026 and possible restriction of new configurations across Q3–Q4 2026. Google gives the month (January 2027) but not a specific day, so this entry records the start of that month (2027-01-01) as the sunset date for the countdown and states the month-level precision here and in the body — the day is not inferred (Constitution §3.2). Not machine-detectable in a code repo (a Gmail account-settings feature, no package/image/text fingerprint), so no detect fingerprint added.
Put this countdown in your README
Building on Google? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/gmail-third-party-account-features-removal)Spot an error or a changed date? Tell us and it’s corrected the same night.