Gmail drops third-party 'Send as' support in January 2027

Google has announced the discontinuation of Gmail’s "Send as" feature for third-party email addresses, including custom domains and non-Google providers like Yahoo or Outlook. The change takes effect in January 2027 and will not impact Google Workspace aliases or other Gmail addresses owned by the user.

The feature currently allows users to send emails from up to 99 different addresses, including external accounts, by configuring SMTP settings. After January 2027, users will no longer be able to send messages from non-Google email addresses through Gmail’s interface. Google Workspace users sending from their organization’s domain or Gmail aliases will continue to have this functionality.

What is changing

The removal of third-party "Send as" support means users will no longer be able to send emails from external addresses—such as those tied to custom domains or other email providers—directly through Gmail. The feature’s discontinuation does not affect sending from other Gmail addresses or Google Workspace aliases, which will remain operational.

Users who attempt to send from an unsupported address after the cutoff will receive a bounce notification. Google has advised users to remove any invalid or unwanted aliases from their Gmail settings before the change takes effect. For those who need to reverify an address, the process requires deleting and re-adding the alias.

Impact on users

The change primarily affects individuals and small businesses that rely on Gmail to manage multiple email accounts, particularly those using custom domains. Users who currently send from external addresses will need to transition to alternative methods, such as using their email provider’s native interface or a third-party email client that supports SMTP.

For recipients, the change may alter how sender information is displayed. Some email services, like Outlook, currently show messages sent via Gmail’s "Send as" feature with a "on behalf of" notation. After January 2027, recipients will no longer see this notation for third-party addresses, as the feature will no longer be available.

Google has provided guidance for users who encounter errors when configuring SMTP settings, such as "Couldn’t reach server" or "TLS Negotiation failed." The company recommends ensuring the correct port number, authentication type, and outgoing mail server are used, and that the third-party provider supports SSL or TLS with a valid certificate. Common secure configurations include SSL on port 465 or TLS on port 25 or 587. If a provider does not support these protocols, users can opt for an unsecured connection on port 25, though this is not recommended due to the lack of encryption.

What to watch

Users who currently rely on the "Send as" feature for third-party addresses should begin exploring alternative solutions before January 2027. Options include:

• Migrating to a dedicated email client that supports multiple accounts and SMTP configurations.
• Using the native interface of their email provider for sending messages.
• Transitioning to Google Workspace for custom domain support, if applicable.

Google has not indicated whether it will introduce a replacement feature for third-party sending. Users are advised to monitor updates from Google for any changes to the timeline or additional guidance.