Live data from Hacker News

Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

support.google.com

31–40 of 139 posts

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#31
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.

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#33
post #24

Earlier quoted context omitted.

Yes, that was my first thought. It's wild to me that GMail would support sending as yahoo.com, outlook.com, etc. in the first place. Google makes lots of questionable decisions and shuts down lots of products uncessarily, but this is not a strange or unwarranted move.

It's not wild at all. It's just behaving like any other MUA but with an extra step. You have to give GMail your SMTP submission credentials for the sending server of the target domain, then prove ownership of the specific address you want to send as. SPF/DKIM/DMARC works fine, as GMail is just submitting your message on your behalf the way any MUA would.

Oh, if they're sending via your provider's SMTP then that makes sense. Still, I can't imagine a lot of people use this feature.

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#34
post #27

Earlier quoted context omitted.

It's not an easy task! I had mine account since gmail beta, so much stuff is going through it. Two years ago I moved to Fastmail(they're great), and pretty much setting up an alias per site/purpose. While I'm happy to see that gmail receives less & less, I still have about 150 entries in 1password that say @gmail.com... maybe one day...

Just do email forwarding and progressively update your accounts?

[deleted]

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#35

> This change does not affect Google Workspace aliases or other Gmail addresses you own. I bet most people complaining about this change don’t even know this feature exists. Right now you can forge email from any email address you can verify ownership. Most of those emails will end up in a spam folder. This doesn’t affect email addresses that Google controls DMARC records for.

Isn't this just using SMTP through whatever mail server you have connected to Gmail?

Either way, this is likely going to stop me from using Gmail as my mail aggregator, I've used this feature for nearly a decade to send and receive from 6 different addresses, Gmail recognizes the to address and automatically sets the from address to the correct account.

Is Thunderbird still decent nowadays? What's a decent mobile + desktop replacement?

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#36

> This change does not affect Google Workspace aliases or other Gmail addresses you own. I bet most people complaining about this change don’t even know this feature exists. Right now you can forge email from any email address you can verify ownership. Most of those emails will end up in a spam folder. This doesn’t affect email addresses that Google controls DMARC records for.

What an odd choice of inflammatory language for a feature that uses standard email headers. It doesn't forge anything since it clearly says it was sent from the GMail account on behalf of the other email address in the headers.

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#37

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.

The moment they turn off automatic forwarding (and I have no doubt they will), my gmail address dies. I'm trying to migrate accounts over whenever possible, but it's quite tedious.

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#38

> This change does not affect Google Workspace aliases or other Gmail addresses you own. I bet most people complaining about this change don’t even know this feature exists. Right now you can forge email from any email address you can verify ownership. Most of those emails will end up in a spam folder. This doesn’t affect email addresses that Google controls DMARC records for.

> Right now you can forge email from any email address you can verify ownership. how can you "forge" something if you verify ownership? when you own something, it's not "forging" to use it. i think the point you're trying to get at is that the mail might fail dmarc requirements?

Because ownership can change. I can still use Gmail to send email from my old university address that I lost access to 15+ years ago. This should not be possible.

Re: Gmail to end support for "Send as" for third-party addresses, such as @yahoo.com

#40
post #19

> we occasionally have the difficult choice to discontinue features that require disproportionate maintenance resources. Am I really expected to believe that the billions of dollars the company makes in pure profit can't sustain this feature? Am I really expected to believe the touted productively gains granted by Google's AI can't sustain this feature?

Keeping the good, bad, and evil aside for a moment, is it possible that the very reason this company makes billions consistently is because they ruthlessly (or stupidly as per "us") drop things they don't want to do, don't need to do, irrespective of whether we think those would have been profitable, or even very nice of them?
Post reply on HN