Why can't I send emails from a custom domain in Gmail anymore?
Email providers are dropping support for free external SMTP services, which forces users to abandon their unified inboxes. To keep sending mail from a non-Gmail domain, you are pushed into paying for Google Workspace, destroying your integrated workflow and trapping you in an overcrowded, disjointed platform.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
- 1Switching to a Google Workspace paid account
- 2Using alternative email services like Fastmail via IMAP
- 3Accessing external accounts through their own separate web interfaces or mail clients
In their words
Unedited, most upvoted first, each linked to the thread it came from.
“At this point, it seems like doing a Google Workspace paid account may be the best solution for continuity of experience, but you break all the commingling and integration.”source ↗
“From the perspective of someone who uses the free SMTP service of Google to send emails from a not gmail domain where there is no SMTP, well it's uncomfortable.”source ↗
“Workspace is the Google+ of SaaS. Nobody asked for it or likes using it. Full of undiscoverable, poorly designed features, a privacy nightmare, too much unrelated stuff bundled together.”source ↗
Where this came up
People with this problem also raised
- 2Buyer entered the wrong shipping address after checkout
- 2Why do self-hosted emails keep going to spam?
- 2How to stop bad emails from entering CRM workflows
- 3Why are wedding invitations taking weeks or months to arrive in the mail?
- 3Why is accounting software automatically emailing my clients?
- 7Why am I getting DMARC and SPF errors when emails deliver fine?