Reddit drafts: Gmail Send As deprecation

Google confirmed on their help center last week: starting January 2027, Gmail is removing "Send as" for third-party addresses (Yahoo, Hotmail, iCloud, custom domains). Gmail-to-Gmail and Google Workspace aliases are unaffected. Google's own words: "Starting January 2027, Gmail will no longer support the Send as feature for third-party email addresses." Also from Google: "You will no longer be able to send mail from third-party email accounts in Gmail on the web or in the Gmail mobile apps." Web AND mobile Send As both stop. Google also warned that new configurations may start being restricted before January 2027, so if you were planning to add a new Send As setup soon, expect friction. What still works after January 2027: - Send As for other Gmail addresses (aliases within Gmail) - Send As for Google Workspace aliases - READING third-party account mail in the Gmail mobile app (add-and-receive continues on Android and iOS) - IMAP/POP access to Gmail from external clients What breaks: - Send As from Gmail web AND Gmail mobile apps for @yahoo.com, @hotmail.com, @icloud.com, and custom domains Anyone here already planning what they'll do? Curious what people are moving to.

Three main paths depending on your setup: 1. **Pay for Google Workspace** ($7/user/mo). Only works if you have a custom domain, doesn't help @yahoo.com or @hotmail.com users. Full Gmail on your domain plus the rest of the Google suite. 2. **Switch to a desktop mail client** (Thunderbird, Outlook, Apple Mail). Leaves Gmail's web UI behind but SMTP is a protocol not a Google feature, so this always works. 3. **Browser extension that intercepts Gmail compose and routes send through your own SMTP.** Keeps you in Gmail. I've been working on option 3 at mailbridge.app (Chrome, Firefox, Edge, Safari, early access right now). Mobile is a separate problem: no browser-extension answer there, working on that too. More context and Google's exact citations: https://mailbridge.app/posts/gmail-send-as-deprecated-january-2027/ (Disclosure: I run MailBridge.)

Google confirmed on their help center that Gmail is ending 'Send as' for third-party email addresses in January 2027. This is separate from (and later than) the 'Check mail from other accounts' POP fetch removal that happened in January 2026. The exact quote from Google: "Starting January 2027, Gmail will no longer support the Send as feature for third-party email addresses, such as @yahoo." Affected addresses: any Yahoo, Hotmail, Outlook.com, iCloud, or custom-domain address configured via Settings → Accounts and Import → 'Send mail as.' Google's statement covers both surfaces: "You will no longer be able to send mail from third-party email accounts in Gmail on the web or in the Gmail mobile apps." Web AND mobile Send As stops. Unaffected: - Send As for another Gmail alias - Send As for Google Workspace aliases - IMAP/POP access to Gmail from external clients - READING third-party account mail in the Gmail mobile app (the receive side continues; only the send-as-a-third-party-address flow ends on mobile) Google also flagged that new configurations may be restricted before the January 2027 cutoff. For anyone whose workflow depends on this (composing in Gmail, sending from a custom or third-party address), the practical desktop options are: Workspace (custom domain only), a desktop mail client, or a browser extension that intercepts Gmail compose and routes the send through your source SMTP. That third approach is what I built (mailbridge.app), currently in early access. Chrome, Firefox, Edge, and Safari supported. Mobile is a separate problem: browser extensions do not run in the Gmail mobile app. MailBridge is working on a mobile solution. Full post with source citations: https://mailbridge.app/posts/gmail-send-as-deprecated-january-2027/ Curious what others plan to do here.

Small heads-up for anyone running a business email through Gmail's 'Send as' feature. Google confirmed on their help center that Gmail is removing 'Send as' for third-party email addresses in January 2027. This is what you use when your @company.com (or personal @yahoo.com, @hotmail.com, @icloud.com) shows up as an option in Gmail's 'From' dropdown when composing. Direct quote from Google: "Starting January 2027, Gmail will no longer support the Send as feature for third-party email addresses." New configurations may start being restricted before the January 2027 cutoff. What this means for your business: - If you have Google Workspace on your domain, nothing changes (Workspace aliases stay) - If you use Gmail free with a Send As for your business @yourcompany.com hosted elsewhere (typical setup), you lose the ability to send from that address in Gmail after January 2027 - Same for @yahoo, @hotmail, @icloud addresses used as business contacts Note: Google's statement covers both web AND mobile Gmail. "You will no longer be able to send mail from third-party email accounts in Gmail on the web or in the Gmail mobile apps." If you send from Gmail on your phone too, this affects you on both surfaces. Options (desktop): 1. Pay for Google Workspace ($84/user/year, requires custom domain) if you want to keep things native 2. Switch to a desktop email client (Thunderbird, Outlook, Apple Mail) 3. Browser extension (Chrome, Firefox, Edge, Safari) that keeps you in Gmail and routes sending through your own SMTP Mobile is a separate problem (browser extensions do not run in the Gmail mobile app). MailBridge is working on a mobile solution for this. Full explainer: https://mailbridge.app/posts/gmail-send-as-deprecated-january-2027/ (I built MailBridge, which offers option 3 in early access on desktop. Mobile solution in progress. Full disclosure.) Anyone here already planning a switch?

Google confirmed that Gmail's 'Send as' feature for third-party email addresses is going away in January 2027 (announcement on their support page). If you run a self-hosted mail server (Postfix, Docker Mailserver, mailcow, etc.) with your custom domain and route send through Gmail's UI via 'Send as' + your source SMTP, that path breaks in January 2027. Google's exact wording: "Starting January 2027, Gmail will no longer support the Send as feature for third-party email addresses, such as @yahoo." Options after the cutoff: 1. Move fully to a desktop client (Thunderbird, Neomutt, etc.) using your self-hosted SMTP. Works but leaves Gmail. 2. Google Workspace on your domain. Defeats the point of self-hosting. 3. Browser extension (Chrome, Firefox, Edge, Safari) that intercepts Gmail compose and routes send through your source SMTP instead of Gmail's. I built the third one (mailbridge.app) as a hosted service, not self-hosted, so probably not many upvotes here. Wanted to flag the approach anyway because the mechanism (extension intercepts compose, calls your own SMTP) is worth considering for anyone who wants to keep Gmail as their client but keep their self-hosted mail server as the send path. Full context: https://mailbridge.app/posts/gmail-send-as-deprecated-january-2027/ Anyone else affected by this? What's your fallback plan?