Google is changing how Gmail works with email accounts hosted outside Google. Starting January 2027, Gmail will stop letting you send mail from a third-party address — such as a custom-domain business address hosted elsewhere, or a Yahoo or Outlook.com account — through Gmail’s own interface, on the web and in the mobile apps. Google is also discontinuing Gmailify and web-based POP fetching for external accounts.
If you only ever use a @gmail.com address, this change won’t touch you. But if your business uses Gmail as the everyday inbox for mail that actually lives on another provider, it’s worth reading the fine print now rather than in December 2026.
It also raises a bigger question than which setting to change: how much control does your business actually have over its email infrastructure?
What Is Gmail’s Third-Party “Send As”?
“Send as” lets a Gmail user send mail from another address they own, using Gmail’s compose window, after verifying it once via SMTP credentials. A common pattern:
- sales@company.com
- support@company.com
- name@company.com
If that business email is actually hosted elsewhere — a hosting panel, an old provider, another mailbox platform — Gmail can be configured to send as that address anyway. It’s a convenient way to run several identities from one inbox. That convenience for third-party accounts is what’s being retired.
What’s Actually Changing
Google has confirmed three changes, all tied to third-party (non-Google) accounts:
1. “Send As” Ends — on Web and Mobile
From January 2027, Gmail will no longer send mail from third-party accounts, whether you’re composing on gmail.com or in the Android/iOS app. This is the detail worth flagging: some early coverage of this change implied mobile was untouched. It isn’t — only sending as a third-party address stops everywhere. You can still add a non-Google account to the Gmail mobile app to read it; you just can’t reply from it as that address.
2. Gmailify Is Discontinued
Gmailify let a connected external account borrow Gmail’s spam filtering and inbox organization. That bridge is going away along with “Send as.”
3. Web-Based POP Fetching Ends
The “Check mail from other accounts” feature, which pulls messages from a third-party account into Gmail over POP, stops working in the Gmail web interface. The Android app keeps this POP-fetch feature for now. Already-imported mail stays put either way — Google says nothing gets deleted.
None of this touches the third-party mailbox itself. Point a desktop client such as Outlook or Thunderbird directly at that account’s own IMAP or POP server — not routed through Gmail — and it keeps working exactly as before, because it was never part of Gmail’s feature set to begin with.
Who Should Pay Attention
The impact depends entirely on how your organization currently handles email. Take a closer look if:
- Employees send from a company address hosted elsewhere, through Gmail.
- Several third-party mailboxes are managed through one Gmail account.
- Gmail is the de facto primary interface for externally hosted business email.
- Teams rely on Gmail’s web interface to send and receive on external accounts.
If your organization runs on Google Workspace, this specific change doesn’t apply the same way — Workspace “Send as” and Gmail-to-Gmail aliases are unaffected. The businesses most exposed are the ones using free consumer Gmail as an unofficial front end for mail hosted somewhere else entirely.
Why This Is Bigger Than a Settings Change
Business email isn’t just an inbox — it carries customer communication, sales, finance, HR, vendor relationships and internal operations. If your team depends on Gmail to manage externally hosted mail, this forces a new workflow: your provider’s own webmail, a desktop client, or a different platform altogether. For a two-person team that’s an afternoon of reconfiguration. For a larger organization it’s user training, credential changes, security testing and IT support hours.
That’s really the useful part of this announcement. It’s a prompt to ask a question most businesses don’t revisit often enough: where does your business email actually live, and who controls it?
A company can own its domain — company.com — while its mailboxes sit on someone else’s infrastructure, accessed through yet another company’s interface. That’s not one dependency, it’s a stack of them. Worth asking directly:
- Where are our mailboxes actually hosted?
- Who administers our email infrastructure day to day?
- Where does the mail data — and the backups — physically sit?
- What security controls (encryption, DLP, admin policy) do we actually have available?
- What happens to our workflow if a provider discontinues a feature we depend on, the way Gmail just did?
- If we had to move, how easily could we?
Owning a domain isn’t the same as controlling the email environment behind it. Google’s change is a low-stakes way to find out where the gaps are before a higher-stakes one does it for you.
What to Do Before January 2027
No need to panic — Q3–Q4 2026 is a transition window, not a cliff edge. But it’s worth working through a short checklist:
1. Audit your current setup
List every third-party account connected to Gmail via “Send as,” Gmailify or POP fetch, and document who on your team relies on it.
2. Identify the critical mailboxes
Sales, support, finance, HR, leadership — flag which of these depend on the Gmail workflow that’s ending.
3. Review your actual email host
Check whether the provider that hosts that mail — not Gmail — gives you the webmail, security, administration and storage your business actually needs. If Gmail was carrying the UX for a weak underlying host, this is the moment that becomes visible.
4. Test the alternative before you’re forced to
Try your provider’s own webmail, a desktop client over IMAP/SMTP, or a dedicated business email platform — before January 2027, not during the outage week.
5. Plan migration in phases for larger teams
Audit → Test → Pilot → Migrate → Monitor. A phased rollout catches configuration issues on one team before they hit the whole company.
Why Dedicated Business Email Hosting Is Worth Considering
A platform built around your domains, your users and your administrative requirements — rather than one you’re borrowing a compose window from — typically gets you:
- Centralized, multi-domain user administration
- Custom business domains as first-class, not bolted-on
- Email security controls: SPF, DKIM and DMARC enforcement
- Encryption and S/MIME
- Data loss prevention (DLP)
- Backup and recovery under your policy
- A choice of cloud, private cloud, sovereign cloud or fully on-premise deployment
Which of these matter most depends on your size, industry, regulatory exposure and IT strategy — but “Gmail happened to make this convenient” is not a strategy.
How XgenPlus Helps
For organizations reviewing this now, XgenPlus is a dedicated enterprise email platform built for exactly this kind of control: custom-domain business email with cloud, private cloud, sovereign cloud or on-premises deployment, an in-house PKI/Certificate Authority for S/MIME, DLP, centralized multi-domain administration, and 25+ years in email infrastructure across 50M+ mailboxes — including Indian government, PSU and BFSI deployments, where control of the infrastructure is a compliance question, not a preference.
XgenPlus also supports AI Compose, multilingual email and true IDN/EAI addresses (email in Indian scripts), so switching off a Gmail workaround doesn’t mean giving up modern compose and inbox features — it means getting them from the platform that actually hosts your mail, with a proper webmail and admin console instead of a borrowed one.
If Gmail’s change is forcing you to look at this anyway, it’s a reasonable moment to check whether the mail should just live — and be sent from — a platform designed to be the primary interface in the first place.
Frequently Asked Questions
What is Gmail’s “Send as” feature for third-party accounts?
It lets a Gmail user send mail from another address they own — such as a custom-domain business address hosted by a different provider — through Gmail’s own compose window, after a one-time SMTP verification. It’s what lets someone run sales@company.com through their personal Gmail inbox even though company.com’s mail is hosted elsewhere.
When exactly does Gmail stop supporting third-party “Send as”?
Google began in-product notices in Q3 2026. Existing setups keep working through the rest of 2026, with new configurations already being restricted. Full removal is set for January 2027, after which you can no longer send as a third-party address from Gmail on the web or in the mobile apps.
Does this affect the Gmail mobile app, or only Gmail on the web?
Both. Sending as a third-party address stops on web and mobile alike. What survives on mobile is read access — you can still add a non-Google account to the Gmail app to receive its mail — but you can’t reply or compose as that address from either surface after the change.
Does this affect Google Workspace or Gmail-to-Gmail aliases?
No. Google Workspace’s own “Send as” and Gmail-to-Gmail aliases are unaffected. This change targets only free consumer Gmail acting as a front end for accounts hosted on entirely separate, non-Google platforms.
What should a business do before January 2027?
Audit which mailboxes and employees rely on Gmail’s “Send as,” Gmailify or POP fetch for externally hosted mail; check whether your actual email host’s own webmail or a desktop client (IMAP/SMTP) meets your needs; and, for larger teams, migrate in phases — audit, test, pilot, migrate, monitor — well before the cutoff.
Final Thoughts
Ending “Send as” for third-party accounts is a small line item in Gmail’s changelog and a real disruption for any business that quietly depended on it. More usefully, it’s a forcing function to ask where your business email actually lives, who administers it, and how much you’d have to scramble if that provider changed the rules tomorrow.
With January 2027 on the calendar, the businesses that come out ahead are the ones that treat this as a planning exercise now rather than a fire drill in December 2026.
- Compare XgenPlus vs Gmail, Google Workspace, Microsoft 365 and Zoho — features, security and pricing side by side.
- Start a free XgenPlus trial and test your migration path before the deadline.
- Talk to our team about a phased migration plan for your domains and mailboxes.
