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.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
- 1Switching to a Google Workspace paid accountDid this help you?
- 2Using alternative email services like Fastmail via IMAPDid this help you?
- 3Accessing external accounts through their own separate web interfaces or mail clientsDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, 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
- 5Buyer entered the wrong shipping address after checkout
- 7Why do self-hosted emails keep going to spam?
- 2Why won't my seller account update my email address?
- 2How to stop bad emails from entering CRM workflows
- 4How to manage company email signatures centrally
- 8Why are wedding invitations taking weeks or months to arrive in the mail?