Gmail Is Retiring Third-Party 'Send As': What Outbound Teams Must Move Before January 2027
Google has published a removal date. From January 2027, Gmail will no longer send mail from a third-party address, which ends the arrangement where a mailbox hosted at Zoho, Titan, Hostinger, or any non-Google provider gets operated from inside a Gmail window. The Gmail Help notice covers three features at once: "Send as" for non-Google addresses, Gmailify, and POP fetching of third-party mail.
For a typical Gmail user this is a minor inconvenience about a dormant Hotmail account. For an outbound team it can quietly break the reply side of a live campaign, because the domain that sends and the inbox a rep actually watches are frequently not the same system.
What Google Is Removing
| Feature | Status from January 2027 | What it does today |
|---|---|---|
| "Send as" for third-party addresses | Removed on web and in the mobile apps | Lets a Gmail account send mail that appears to come from a non-Google address you own |
| Gmailify | Removed | Applies Gmail spam filtering and inbox organisation to a third-party account |
| Check mail from other accounts (POP) | Removed | Pulls messages from a third-party mailbox into your Gmail account |
| Adding or syncing a third-party account on the web | Already removed | Previously announced, and still available in the Gmail mobile app |
What Keeps Working
Three things survive, and they decide how big the migration actually is.
Google-hosted identities stay exactly as they are today. "Send as" continues for other Gmail addresses and for aliases attached to a Google Workspace account, which is the configuration most Workspace-based outbound teams already run for their primary domain.
The Gmail mobile apps keep third-party account access. You can still add and read a non-Google account on Android, iPhone, and iPad. You cannot send as that address from there once the change lands, since the sending restriction applies to mobile as well as web.
IMAP, POP, and the Gmail API remain fully supported for reaching a Gmail account from somewhere else. Outlook, Thunderbird, Apple Mail, and any sequencer connecting over IMAP or SMTP are not touched by this announcement.
Why Outbound Teams Are More Exposed Than Average
A well-run outbound setup owns several secondary domains, each carrying a handful of mailboxes, deliberately hosted away from the primary Workspace tenant so a reputation problem stays contained. The sending itself happens through the sequencer over SMTP, and none of that changes here.
The reply side is where the habit forms. A rep does not want six browser tabs, so somebody wires those third-party addresses into the rep's Gmail with "Send as" and POP fetch, and every reply goes out from one window. That is convenient, invisible on any architecture diagram, and precisely what stops working.
The failure mode is undramatic. Nothing bounces and no alert fires. A rep opens Gmail in January, finds the alias missing from the From dropdown, replies from their own name instead, and a prospect who received four messages from one address gets the fifth from another. Thread continuity breaks and nobody files a ticket, because from the sequencer's side the campaign looks healthy.
The Deadline Before the Deadline
The timeline has two dates, and the earlier one is the harder problem to plan around.
Q3 2026 opens the notice period, with in-product notifications to affected users. Through Q3 and Q4 2026 the features keep working, but Google states plainly that it may restrict new configurations during that window and encourages migration inside it. January 2027 is full removal.
So the ability to add a new third-party "Send as" is expected to disappear before the existing ones stop working. Any plan that involves standing up one more alias in December rests on a feature that may already be closed by then.
Three Migration Paths
Move the domain onto Workspace. If a secondary domain matters enough to keep for years, adding it as a Workspace tenant restores "Send as" for its aliases permanently, because Google-hosted identities are exempt from the change. This costs a licence per mailbox and suits domains that carry a real business identity.
Reply inside the sequencer. Smartlead, Instantly, and every comparable platform ship a unified inbox that connects to the mailbox over IMAP directly. Replies leave from the address that sent them, Gmail is not involved, and the conversation sits next to the campaign record. This is the cleanest fit for pure sending infrastructure and costs nothing extra.
Use a desktop client. Outlook, Thunderbird, or Apple Mail over IMAP and SMTP handles several accounts in one window and does not depend on Google's roadmap at all. Sensible where one person needs a single place for third-party addresses that are spread across different tools.
Choosing between them per mailbox comes down to one question: is this address a business identity or a piece of sending infrastructure. A business identity belongs on Workspace. Sending infrastructure belongs in the sequencer.
Ignore the Extensions
Browser extensions and third-party services will offer to replicate "Send as" after the cutoff. Google's own notice warns about them, and the warning deserves repeating: these tools generally want your credentials or an OAuth token carrying send permission on the mailbox. Giving a deprecation workaround standing send access to your commercial mailboxes swaps a scheduling problem for a permanent security exposure, and does it to solve a migration you could finish in a fortnight.
Every outbound stack collects configurations nobody wrote down, and they all work until a vendor changes a default. The teams that stay out of trouble are the ones who can produce a current list of every mailbox, its host, and its owner on request.
Want an Outbound Stack You Can Actually Inventory?
We build the domains, mailboxes, sequencing, and reply handling inside accounts registered to you, then document what runs where and operate the whole motion against a meeting definition your sales team agrees to. When a provider deprecates something, the migration becomes a scheduled task rather than an incident, because the map already exists.
Frequently Asked Questions
A strong positive reply rate for B2B cold email is 1.5–3%. Top-performing campaigns with tight targeting and personalized copy can hit 4–5%. If you're below 1%, it usually signals a deliverability or messaging problem — not a volume problem.
The safe range is 30–50 emails per inbox per day for warmed inboxes. That's why outbound systems use multiple inboxes (we use 80) — to reach 40,000+ monthly sends while keeping each inbox well within safe limits. Sending more than 50/day from a single inbox risks spam folder placement.
Yes. The CAN-SPAM Act permits unsolicited commercial email as long as you include a physical address, an unsubscribe mechanism, accurate headers, and non-deceptive subject lines. Unlike GDPR in Europe, the US does not require prior opt-in consent for B2B cold outreach.
Domain warm-up typically takes 2–3 weeks. During this period, sending volume gradually increases while the email warm-up tool generates positive engagement signals (opens, replies) to build sender reputation. Skipping or rushing warm-up is the most common cause of deliverability problems.
Cold email is targeted, relevant outreach to a specific person based on their role, industry, or company — with a clear business reason. Spam is untargeted mass messaging with no personalization or relevance. The distinction matters legally (CAN-SPAM compliance) and practically (deliverability depends on relevance signals).
Dimitar Petkov
Co-Founder of LeadHaste. Builds outbound systems that compound. 4x founder, Smartlead Certified Partner, Clay Solutions Partner.