Gmail will drop 'Send as' for third-party addresses in 2027
GMails custom domain "send as" discontinues January 2027
Google has announced that starting January 2027, Gmail will no longer support the 'Send as' feature for third-party email addresses like Yahoo or Outlook. The change doesn't affect Google Workspace aliases or other Gmail addresses. Users can still send from up to 99 addresses they own, but must follow steps to add and confirm them. This update is part of broader changes to third-party email account support in Gmail.
Starting January 2027, Gmail will no longer support the "Send as" feature for third-party email addresses, such as @yahoo.com or @outlook.com.
- anticorporate
I moved all my custom domains to Fastmail five or six years ago and couldn't be happier.
My Gmail only exists to catch legacy messages and Google service notifications. I look forward to the day I can completely migrate out of all their products, but some organizations I work with who use Google for various things have made that a slow slog.
- happyopossum
Current headline on HN is incorrect - it's not custom domains, it's third-party email addresses, such as @yahoo.com or @outlook.com. Domains and other gmail addresses you own can still be used....
- ericpauley
This was the last straw for me. I'm migrating to Apple Mail and cancelling workspace ASAP.
ETA: I said nothing about where I'm planning to host my SMTP server. Apple Mail is a provider-agnostic client-side application, like Thunderbird.
ETA2: Those who read TFA carefully will know that, even though this doesn't affect Workspace aliases, it does affect this feature (Send-As SMTP) for workspace accounts.
- roesel
As someone who uses their personal Gmail account to forward emails from custom domains to (via MXRoute and other email providers), losing the ability to "Send as" from the given adresses from Gmail means I will have to find an entirely new "home base" for email (and paradoxically start forwarding my peronal Gmail emails these instead?), right?
Similarly to losing Inbox many years ago, this really sucks.
- nottorp
Hmm I'm confused. I have my own domain that is totally not hosted on google. However, I use Google's SMTP to send mail as that domain (specifically the one email address that is enabled on my custom domain).
For that I'm authenticating to the SMTP with my google account, and I somehow proved to google i own the email a couple billion years ago when we all had pet dinosaurs.
Are they discontinuing that or something else?
And Q2: if this is what they're discontinuing, are there any other email solutions that would support something like this? I.e. incoming email to my server I control 100% but offering smtp relay?
- occz
I have a domain and a contact email address for that domain that I have exclusively used through GMail, I guess this means I need to figure out a different path forward for that, then?
- jameshilliard
> You can continue to use "Send as" for any Google-hosted identities, including other Gmail addresses or aliases associated with your Google Workspace account. The discontinuation will not impact these addresses, which only applies to third-party, non-Google email accounts.
I have "Send as" accounts that have this configuration:
Mail is sent through: smtp.gmail.com
However the actual email addresses are often custom domains with say both google and cloudflare sfp records with cloudflare handling the incoming emails and forwarding them to gmail with gmail handling outgoing via google's own smtp server directly.
They aren't remotely clear if this use case is considered a third-party, non-Google email account or a Google-hosted identity since the outgoing smtp server being used is still a google server.
It's crazy that they don't actually explain what "any Google-hosted identities" means.
- kimos
Whelp. I’ve been using Gmail since it was invite only. Sending as my personal domain was grandfathered in. This is going to be my push to leave for another service. I wonder if they understand or intend that?