It's unclear if this applies to third-party email addresses configured to use smtp.gmail.com as the outbound SMTP server or if it only applies to third-party email addresses using actual external 3rd party SMTP servers.
I'm interested in this as well. I would assume all of them from the announcement. I.e. they are removing that functionality altogether from regular Gmail (not Workspace).
I run a self-hosted mail server for a non-profit student association, where we use aliases on our own domain that forward to users personal email accounts. They configure Gmail to send-as via that alias using SMTP. This has worked very well - users are happy about not having to check multiple email accounts.
Sad to see this feature go. Such a short notice, too.
While I dislike the feature getting removed, this argument does not hold up to scrutiny. They will remove using external SMTP servers to send emails from external, third-party addresses. Sending as another Gmail or Google Workspace address will continue to work, but that path is fully Google-internal.
Emphasis mine:
> 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.*
Isn't it because inside a Google Workspace you'll still be able to "Send as" but only from someone from the same Google Workspace (and hence same domain name?). At least that's how I read their article.
Maybe the disproportionate support is about domains outside of the workspace workspace? (I can see why sending as "trollshillingaccount291879@hotmail.com" from a GMail account is potentially lots of maintenance).
It's unclear if this applies to third-party email addresses configured to use smtp.gmail.com as the outbound SMTP server or if it only applies to third-party email addresses using actual external 3rd party SMTP servers.
I'm interested in this as well. I would assume all of them from the announcement. I.e. they are removing that functionality altogether from regular Gmail (not Workspace).
I run a self-hosted mail server for a non-profit student association, where we use aliases on our own domain that forward to users personal email accounts. They configure Gmail to send-as via that alias using SMTP. This has worked very well - users are happy about not having to check multiple email accounts.
Sad to see this feature go. Such a short notice, too.
Gah!
But one of the key benefits of this is obscuring what my actual Gmail address is!
I don’t want to use my Gmail address as my main email address. Even if it’s just for personal usage.
I don’t want people knowing what my Gmail account is.
And what happens if I do use my Gmail for everything and Google decides to lock me out of my account….
So are Google wrecking peoples Gmail account setups just to push people into paying for their Google Workspace product?
This industry wide obsession with squeezing revenue out of every little corner of services is exhausting and exasperating.
They claim disproportionate maintenance and yet state “and Google Workspace “Send as” functionality is not affected. “
Beyond retarded.
While I dislike the feature getting removed, this argument does not hold up to scrutiny. They will remove using external SMTP servers to send emails from external, third-party addresses. Sending as another Gmail or Google Workspace address will continue to work, but that path is fully Google-internal.
Emphasis mine:
> 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.*
> They will remove using external SMTP servers to send emails from external, third-party addresses.
What about using Gmail's own internal SMTP servers(i.e. smtp.gmail.com) to send emails from external, third-party addresses?
This is my current use case.
My reading of what Google are saying is that yes, that feature is going away.
Isn't it because inside a Google Workspace you'll still be able to "Send as" but only from someone from the same Google Workspace (and hence same domain name?). At least that's how I read their article.
Maybe the disproportionate support is about domains outside of the workspace workspace? (I can see why sending as "trollshillingaccount291879@hotmail.com" from a GMail account is potentially lots of maintenance).