Gmail Send As Alternative: What to Use Before January 2027

If you forward a custom domain into personal Gmail and use "Send mail as" to reply from it, you now need a Gmail Send As alternative with a deadline attached. Google has confirmed that starting January 2027, Gmail will no longer let you send mail from a third-party address, on the web or in the mobile apps. New configurations are already being restricted and existing ones keep working until the cutoff. Most of the alarm about this gets the scope wrong, so before you go shopping: what Google is removing, the longer list of things it is not touching, and the four replacement routes with the trade-off each one carries.

What Google is removing in January 2027

Google's help page on the change is blunt about the mechanism: "The 'Send as' feature will no longer be available. This feature allows you to send email from a third-party address, such as @hotmail.com, @yahoo.com, and others."

One point of precision nobody else is flagging. Google's page names only free consumer providers and never uses the words "custom domain." Send As is a single feature over any address you have verified, so an address on a domain you own is a third-party address as far as Gmail is concerned, and every outlet covering the change reads it that way. Android Authority names custom domains outright. Plan as though your domain is included, but do not quote Google as having said so.

Two neighbouring features go on the same schedule: Gmailify, which applies Gmail's spam filtering to a third-party account, and POP fetching of other accounts into Gmail on the web. Google's separate page for those two puts them on a staggered clock, with no new users after the first quarter of 2026 and existing users kept until January 2027. If you have seen a "January 2026" date attached to Gmailify, that is where it comes from, and it refers to new signups rather than the shutdown.

Google's stated reason, repeated across the coverage, is that it retires features which "require disproportionate maintenance resources."

What is not changing, which is most of it

This is the part the panic posts skip, and skipping it leads people to rip out setups that were never at risk.

• Forwarding is untouched. Google says so directly: "You can configure your third-party provider to auto-forward messages to your Gmail address. This is independent of Gmail's 'Send as' feature and does not affect it." If your domain forwards into Gmail today, it still will in 2027.
• Google Workspace keeps Send As. If you pay for Workspace, none of this applies to you. It is the consumer Gmail feature that is going.
• Gmail-to-Gmail aliases are fine. Sending from your other Google addresses works as before.
• Third-party clients over IMAP and SMTP are fine. Outlook or Thunderbird talking to Gmail is a different path and is unaffected. App passwords are not the thing being removed here either.
• The Gmail mobile app can still hold a third-party account. This looks like a contradiction with "Send As dies on mobile," so here is the reconciliation: sending as a third-party address from your Gmail account is what goes away. Adding that third-party account to the app as its own account, which authenticates against that provider's own SMTP server, is a different mechanism and stays.

So what actually breaks is one half of one very common free stack. Forwarding carries mail from your domain into Gmail, which keeps working, and Send As carries your reply back out as the domain, which does not. It is the setup we call Route 4 in send email from multiple domains, and the second half of the standard Cloudflare setup, where Cloudflare Email Routing can't reply on its own and people bolt Send As on to close the gap. You keep the inbox and lose the reply button.

Worth saying plainly: that reply button has been half broken since 2024 anyway. Mail sent through Gmail's SMTP claiming to be from your domain fails DMARC alignment for that domain, so a share of those replies were already being filtered silently. How to reply to email from a custom domain covers the SPF, DKIM and DMARC mechanics. January 2027 turns a silent failure into a loud one, which is arguably an improvement.

Picking a Gmail Send As alternative

Four routes, and Google itself suggests the first three.

Use the provider's own webmail if you have exactly one custom domain and a mailbox already sitting on it. Zero setup, zero extra cost, and replies authenticate properly because they leave from the provider that owns the domain. The price is a second tab you have to remember to check.

Use a desktop client over IMAP and SMTP if you want everything in one window. Thunderbird is free, Outlook works, and both let you add each domain's mailbox as its own account with its own outgoing server, which is why the replies pass authentication. This is Google's headline suggestion and it is a fair one. Two caveats: it is a desktop app, so it fits badly if you answer mail on your phone, and it does not reduce the number of mailboxes you pay for. Five domains is still five mailboxes and five SMTP configurations.

Move to Google Workspace and Send As survives, since the deprecation is consumer-only. Least disruptive, most expensive. Workspace bills per user, and one real mailbox per domain means one paid seat per domain. We did that arithmetic in Google Workspace multiple domains pricing: around $84 a year per domain on the annual Business Starter rate, which stings for a domain that gets four support emails a month. Adding domains is free, the seats to read them are not.

Use a multi-domain inbox if the count is what hurts. This only makes sense past two or three domains, where the per-domain options stop being annoying and start being a second job.

One thing none of these four is: a Send As clone. If a tool promises to keep sending third-party mail from inside Gmail after January 2027, be careful. Google's own page warns that replacement tools "often require access to your email credentials or OAuth tokens," and it has a point. The feature is being removed at the Gmail end, so anything that appears to restore it is working around Google rather than with it.

Where Mailyond fits

Mailyond is for the fourth row of that table, and only for it. If you own one domain and it lives on Gmail, use the desktop client or the provider's webmail and stop reading here.

The case it is built for is the one where forwarding into Gmail was never really working: several domains, modest mail on each, and a reply that has to go out as the right brand. Connecting a domain is one 5-minute DNS setup with three records, a DKIM TXT, a Return-Path CNAME and an MX. Your DNS stays where it is, with no nameserver move. After that, mail to every connected domain lands in one inbox tagged by domain, and the reply button sends authenticated as the address the message arrived at, so replies pass DMARC instead of getting filtered. A REST API covers the transactional half from the same connected domains.

Pricing counts domains rather than seats: $10 a month for five domains, $40 for thirty. Where it is not the answer: high sending volume, where Resend or Postmark are priced better for exactly that, and full mailbox suites with calendars and drive storage, which Workspace does properly and email forwarding service sets against the free routes. It is live with 7 days free, and plans are on the pricing page.

The short version

Gmail is removing Send As for third-party addresses in January 2027, along with Gmailify and web POP fetching. Forwarding into Gmail, Workspace Send As, Gmail-to-Gmail aliases and IMAP or SMTP clients all keep working, so this is narrower than the headlines suggest. What breaks is the free stack where a custom domain forwards into personal Gmail and Send As carries the replies back out, and that half was already failing DMARC for a lot of people. Your Gmail Send As alternative is the provider's own webmail for one domain, a desktop client if you want one window, Workspace if you would rather pay per seat than change anything, or a multi-domain inbox if the domain count is the real problem. You have until January, and no reason to leave it until December.