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 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.
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 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.
They claim disproportionate maintenance and yet state “and Google Workspace “Send as” functionality is not affected. “
Beyond retarded.