Gmail will drop "Send as" support for non-Google addresses in 2027

Starting in January 2027, Gmail will stop letting you send mail from a non-Google address, such as a Yahoo or Outlook account, through its web interface or mobile apps. Google confirmed the change on its own support page, and the removal also covers Gmailify and web-based POP mail fetching.

What is actually going away

Google's support page is specific about what breaks. Google's own wording, cited by both Android Authority and Proton, says you will no longer be able to send mail "from third-party email accounts in Gmail on the web." That includes the Gmail mobile apps too. That covers any alias built on a non-Google address, like a personal domain routed through Yahoo or Outlook.

Two related features go with it. Gmailify, which pulled a third-party inbox into Gmail's interface, is being discontinued. So is adding or syncing a new third-party account for web-based POP fetching.

What still works

Reading mail from an already-connected third-party account inside the Gmail mobile app continues to work, per Google's support page. So does native multi-account support in the Gmail app on Android and iOS, letting you switch between separate accounts rather than merge them.

Two other things are untouched: Gmail-to-Gmail aliases, and Google Workspace's own "Send as" feature for verified organizational domains. Forwarding from a third-party provider into Gmail, and connecting to Gmail itself from another email client over IMAP or POP, both keep working too.

Why Google says it's doing this

Google's stated reason, per its support page, is that these features "require disproportionate maintenance resources." Google frames it as a maintenance and security trade-off, not a push toward a paid product. Still, Workspace's own Send as is one of the features that survives the cut.

What this means for developers

If you or your team send mail from a custom domain through a personal Gmail account's Send as feature, that setup stops working in January 2027. This is a common way to bootstrap a small project's outbound email without paying for Workspace or a dedicated email service, and it will need a replacement before then.

Audit any onboarding docs, support scripts, or notification systems that rely on a Gmail account sending as a different address. The practical replacements: a real transactional email provider like Postmark, SES, or SendGrid. A paid Google Workspace account, which keeps its own "Send as" support. Or a self-hosted mail setup with proper domain authentication.

Don't wait for a deprecation warning inside Gmail itself to notice this. The change is documented now, more than a year out, specifically so teams have time to migrate before sending breaks silently on a production system.