Gmail Send As Ending 2027: Third-Party Address Removal Guide

For years, one of Gmail's quiet superpowers was that it could pretend to be another mailbox. You added your old @yahoo.com or work @outlook.com address, ticked a box, and suddenly you could sit inside a single Gmail tab and fire off messages that landed in the recipient's inbox looking like they came straight from that other account. That trick has a name — Gmail Send As — and in 2026 Google confirmed it is being switched off for third-party addresses, with full removal scheduled for January 2027.

If you run your whole email life through one Gmail window, this matters more than the average feature deprecation. Gmail Send As is the plumbing behind the "one inbox to rule them all" workflow that power users, freelancers, and small teams have relied on for over a decade. This guide walks through exactly what is changing, the timeline Google has published, what still works, why the company is doing it, and — most importantly — the concrete migration paths so that when the switch flips, nothing in your outbound email quietly breaks.

What Gmail Send As Actually Does

Before you can plan around the change, it helps to be precise about what Gmail Send As is, because it is easy to confuse with two neighboring features. Send As is purely about outbound mail. When you configure it, Gmail lets you pick a "From" address that is not your @gmail.com address — for example, your custom domain, an old provider mailbox, or a shared team address — and route that message out so the recipient sees the alternate address in the From line.

Under the hood, Gmail Send As typically relays the message through the other provider's outgoing (SMTP) server using credentials you supplied when you set it up. That relay is the part Google is retiring for third-party accounts. It is distinct from fetching incoming mail (the "Check mail from other accounts" POP feature) and from Gmailify, which layered Gmail's spam filtering onto a linked account. Those two inbound features are being wound down on a similar schedule, which we covered in our guide to the "Check Mail From Other Accounts" removal and the end of Gmailify and POP. This post focuses on the sending half of that story.

The reason Send As feels indispensable is that it collapses many identities into one workspace. A freelancer can answer a client from their business domain, reply to a family thread from a personal alias, and handle a side project's mail — all without ever leaving Gmail or juggling logins. When people say Google is "breaking multi-account email," the loss of Gmail Send As for outside addresses is the specific thing they mean.

What Is Changing and Who It Hits

Here is the change in one sentence: after January 2027, you will no longer be able to send mail from third-party email accounts inside Gmail on the web or in the Gmail mobile apps. The Gmail Send As option for external addresses is going away, and Google has already begun refusing new Send As configurations for third-party addresses while it winds the feature down.

The people most affected fall into a few clear buckets:

• Consolidators — anyone who funnels an Outlook, Yahoo, iCloud, or old ISP mailbox into Gmail and sends replies from it.
• Custom-domain solo users — freelancers and micro-businesses who point a personal-domain address ([email protected]) through a free Gmail account using Send As rather than paying for hosted email.
• Outbound teams — small sales, support, or outreach operations that used Send As to send from a shared or branded address without buying seats.
• Legacy-identity keepers — people who still send from an address they have had for twenty years but manage day-to-day from Gmail.

If your only "From" address is your @gmail.com address, nothing about your sending changes at all. The removal is strictly about the ability for Gmail Send As to impersonate an external mailbox from within Gmail. That distinction is the single most important thing to internalize before you start planning, because a lot of the online panic conflates it with far broader claims that Gmail itself is closing multi-account support, which is not the case.

The Official Removal Timeline

Google has framed this as a staged wind-down rather than a single hard cutoff, giving users a transition window. Based on Google's published guidance and the reporting around it, the Gmail Send As retirement lines up roughly like this:

The practical takeaway is that you have a real runway, but not an unlimited one. If your outbound email depends on Gmail Send As, the safe posture is to treat late 2026 as your migration deadline and to have the replacement tested well before January 2027 arrives — not on the morning the feature disappears. Businesses in particular should not wait for the in-product warning, because a warning that appears in one admin's inbox can easily be missed across a distributed team.

What Still Works After January 2027

It is just as important to know what is not affected, because the removal is narrower than the headlines suggest. The following keep working:

• Gmail-to-Gmail aliases and the plus trick. Sending as a Gmail alias, or using the [email protected] convention, is untouched. If aliases are new to you, our Gmail aliases guide covers them in depth.
• Google Workspace "Send as." On a paid Workspace account, sending from other addresses within the domain continues to be supported. The retirement targets free consumer Gmail and third-party addresses, not Workspace-managed identities.
• Native mobile multi-account. The Gmail mobile app can still add external accounts by IMAP and manage several mailboxes side by side — you just switch between them rather than sending "as" one from another.
• Third-party clients over IMAP/POP. Reaching your Gmail from Outlook, Thunderbird, or Apple Mail is unchanged. Those desktop clients also keep their own multi-account and send-from-any-address abilities.

In other words, the capability to work across multiple addresses is not disappearing from email — it is disappearing from one specific place, the free Gmail web and app interface, when the "other" address belongs to an outside provider. The workflow survives; where you perform it changes.

Why Google Is Killing It

Google has not shipped a single tidy explanation, but the reasoning that fits the facts comes down to three pressures. First, security and abuse: the SMTP-relay mechanism behind Gmail Send As requires storing and using outside credentials, and letting one account send "as" arbitrary external addresses is exactly the kind of capability that phishing operations and spam farms love. Tightening it reduces a genuine abuse surface. We have written before about how these features get weaponized in pieces like our breakdown of fake security-checkup scams.

Second, maintenance cost: supporting outbound relays to every third-party SMTP server on earth, each with its own quirks, authentication rules, and failure modes, is a perpetual engineering tax on a free product. Retiring it removes a fragile, low-visibility system that Google has to keep patching.

Third — and this is the part users are angriest about — monetization pressure. Removing free Gmail Send As nudges the exact audience that most values it (custom-domain solo users and small teams) toward paid Google Workspace, where sending from your own domain is a first-class, supported feature. Whether you read that as a reasonable cost-recovery move or a squeeze depends on your seat, but it is unquestionably part of the picture. Either way, understanding the motive helps you pick a migration path that will not simply be deprecated again in two years.

How to Check If You Rely on Send As

Do not assume you know. Plenty of people set up Gmail Send As years ago and forgot. Here is how to audit your account in a couple of minutes:

1. Open Gmail on the web and click the gear icon, then See all settings.
2. Go to the Accounts and Import tab (in Workspace it is Accounts).
3. Look under Send mail as. Any address listed there that is not your @gmail.com address is a third-party Send As that may stop working.
4. Note whether each entry says it sends "through Gmail" or "through" an external SMTP server. Entries routed through an external server are the ones most clearly in scope for removal.
5. Check the Check mail from other accounts section on the same page — if you also fetch mail there, your inbound flow is changing too, and you should read our Gmail sending troubleshooting guide for related quirks.

Write down every external "Send mail as" address you find, who uses it, and how often. That list is your migration checklist. If it is empty, you are done — the change does not touch you. If it has even one entry, keep reading, because the right replacement depends on what that address is and how important it is.

Your Migration Options Compared

There is no single correct replacement for Gmail Send As — the best choice depends on whether the address is a hobby alias or your business identity. Here are the realistic paths, with their trade-offs.

Notice the honest limitation of the free routes: none of them perfectly reproduces the old magic of sitting in gmail.com on the web and sending as your external address. The closest free-on-desktop replacement is a client like Thunderbird; the closest "keep everything Google" replacement is Workspace. Pick based on how much the exact web-Gmail experience matters to you versus keeping the alternate identity working.

Adding a Third-Party Account by IMAP

For many people the cleanest free path is to stop leaning on Gmail Send As for the other account and instead add the other account to a client that natively owns it. On the Gmail mobile app this is well supported:

1. Open the Gmail app, tap your profile picture, then Add another account.
2. Choose the provider (Outlook, Yahoo, iCloud) or Other for a custom domain.
3. Enter the address and password, and if prompted, the provider's IMAP and SMTP server settings.
4. Once added, you switch to that account inside the app and send genuinely from it — no impersonation relay involved.

On desktop, a free client such as Mozilla Thunderbird does the same job and keeps a single window: add each mailbox by IMAP, and Thunderbird will send from whichever account you compose in. This is the setup most former Gmail Send As power users end up preferring, because it is provider-neutral and cannot be deprecated by Google. The trade-off is simply that you are running a separate app instead of a browser tab, and you handle updates yourself.

One tip: when you add the account, make sure you use an app-specific password if the provider requires one for IMAP/SMTP, and confirm two-factor authentication is on for that mailbox. Consolidating identities is a good moment to also tighten security, a theme we return to often — see our overview of Gmail passkeys and passwordless sign-in.

The Google Workspace Route

If the address you are losing is a custom domain that represents your business or brand, the path Google most wants you to take is Google Workspace. On Workspace, sending from your own domain is native, supported, and not subject to this removal. You also get admin controls, better deliverability tooling, and the ability to add real send-from aliases within the domain.

The obvious downside is that it is a paid subscription rather than a free trick, and for a hobby address that can feel like overkill. But for anyone whose income depends on a professional-looking From address, moving off the fragile free Gmail Send As relay onto a first-class hosted mailbox is arguably an upgrade that was overdue. It also future-proofs you: a supported, paid feature is far less likely to be retired than a free consumer convenience. If you are weighing Gmail versus Workspace for outbound work generally, our comparison of Gmail accounts vs Google Workspace for cold email lays out the deliverability and cost math in detail.

Whichever hosted route you choose, migrate the mailbox properly: set up the domain's authentication records, import old mail if you want it in the new home, and update the address anywhere it is published so replies keep flowing. Rushing a domain migration in the last week before the deadline is how people end up with bounced business mail.

Deliverability Gotchas When You Migrate

Switching how you send is not just a UI change — it can quietly affect whether your mail lands in inboxes. A few things to watch:

• SPF, DKIM, and DMARC. If you move a custom domain to a new sending platform, its authentication records must be updated to authorize the new sender, or messages may be marked spam. Getting these wrong is one of the top reasons legitimate mail starts landing in junk — a problem we unpack in our guide on how to stop emails going to spam.
• Reply-address mismatch. If you switch to auto-forwarding and reply from your @gmail.com address, recipients will suddenly see a different From line than they are used to. Warn important contacts, or they may not recognize you.
• Signature and branding drift. Rebuild your signature in the new sending location so outbound mail still looks consistent.
• Sending limits. A new platform has its own daily caps and warm-up expectations; do not assume your old volume transfers cleanly. Our overview of aged and ready-to-use Gmail accounts is worth a look if you are rebuilding an outbound stack and want inboxes with established sending reputation rather than starting cold.

Test before you trust. Send yourself and a couple of colleagues messages from the new setup and check where they land — inbox, promotions, or spam — before you route real business through it.

Mistakes to Avoid Before the Deadline

As the January 2027 cutoff for Gmail Send As approaches, a handful of avoidable errors will trip people up. Skip these:

• Waiting for the feature to break. If you migrate only after Send As stops working, you will have a window where outbound mail from that address simply fails, possibly without an obvious error. Migrate while the old path still works so you can compare.
• Assuming aliases are affected. They are not. Do not tear down Gmail-to-Gmail aliases or Workspace send-as in a panic — only external third-party Gmail Send As is going.
• Forgetting the inbound side. Many Send As users also fetch mail from the same account via POP, which is being retired too. Solve both halves, not just sending.
• Publishing a dead address. If you retire an old mailbox entirely, set up forwarding or an auto-reply so people who still write to it are redirected, rather than silently ignored.
• Over-buying. A casual hobby alias does not need a Workspace subscription; a free IMAP setup is plenty. Match the fix to the address's importance.

Handled early, this is a mildly annoying afternoon of reconfiguration. Handled late, it is a scramble with real risk of missed or bounced business email. The difference is entirely in when you start.

Frequently Asked Questions

Is Gmail Send As being removed completely?

No — only for third-party (external) addresses. Sending as a Gmail alias, and sending as another address within a Google Workspace domain, both continue to work. The removal targets the ability to send from an outside provider's mailbox (like Outlook or Yahoo) from within free consumer Gmail on the web and mobile apps, with full removal set for January 2027.

What exact date does Gmail Send As stop working for third-party accounts?

Google has scheduled full removal for January 2027. Before that, through 2026, new Send As configurations for third-party addresses are already being restricted, and existing users will see in-product warnings during a transition window in the second half of 2026. The safe plan is to have your replacement tested and running well before the January 2027 cutoff rather than on the day itself.

Will I still be able to read mail from my other accounts in Gmail?

Reading is a separate feature. The related "Check mail from other accounts" POP fetch and Gmailify are being wound down on a similar timeline, so if you rely on Gmail pulling in external mail, plan to migrate that too. The most durable replacement is to add the external account by IMAP in the Gmail mobile app or a desktop client, which handles both receiving and sending natively.

Do I have to pay for Google Workspace now?

Only if you want the exact "send from my custom domain inside Google" experience on the web. There are free alternatives: use the provider's own app, add the account by IMAP in the Gmail mobile app or Thunderbird, or set up auto-forwarding and reply from your Gmail address. Workspace is the recommended route mainly for custom-domain business identities where a supported, professional setup is worth the subscription.

Does this change affect Google Workspace users?

Not for domain addresses. Workspace "Send as" for addresses within your own domain remains supported. The retirement is aimed at free consumer Gmail sending from third-party external accounts. If anything, Workspace becomes the officially blessed home for the custom-domain sending that free Gmail is dropping.

What happens to emails people send to my old address after January 2027?

That depends on the account itself, not on Gmail. If the external mailbox still exists, mail keeps arriving there — you just cannot fetch or reply to it from inside free Gmail anymore. Set up forwarding from that account, add it by IMAP to a client, or check it in its native app so incoming mail is not stranded. If you close the mailbox entirely, configure an auto-forward or auto-reply first so senders are redirected.

Migrate Early, Not on Deadline Day

The end of Gmail Send As for third-party addresses is a real inconvenience for the exact people who squeezed the most value out of Gmail — the consolidators, the custom-domain freelancers, the lean outbound teams. But it is also narrower than the panic suggests: aliases survive, Workspace survives, and every affected workflow has a working replacement, whether free via IMAP and desktop clients or paid via Workspace. The only genuinely bad outcome is doing nothing until the feature disappears and discovering your outbound mail has quietly stopped.

Audit your Send mail as list this week, pick the replacement that matches how important each address is, test it while the old path still works, and you will glide through January 2027 without a hiccup. Want Gmail's deprecations, security alerts, and account-management changes explained the moment they land — with the migration steps spelled out before the deadline bites? Join our community on Telegram at t.me/mixgmail. We post the fixes, the warnings, and the workarounds that keep your inbox — and your outbound mail — firmly under your control.