alt Hacker News> 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.
Replies
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?
> Right now you can forge email from any email address you can verify ownership
I find this sentence confusing. Do you mean “forge” in a technical sense of “this email came from a server unassociated with the domain”? I don’t really get it. I’ve know this feature existed in Gmail for 15+ years and have made regular use of it. Plus I’ve used it to help older relatives keep an old address alive.
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.
>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?