3 ms·
Gmail / Google Workspaces don't care about their paying customer's privacy and are too lazy to improve their deliverability. Issues with inbound header handling
by Benjamin_Dobell 4y ago
Gmail / Google Workspaces don't care about their paying customer's privacy and are too lazy to improve their deliverability. Issues with inbound header handling wouldn't surprise me either.
If you use multiple domains with Google Workspaces and noticed your emails not getting through when sent from your non-primary domain; you're not imagining it. Any mail receivers that are properly checking SPF are not going to give you a good deliverability score, no matter what you do. Gmail leaks your primary domain in the Reply-Path rather than specifying the domain you sent the email from. I've reported this to them, they don't give a shit. Fun.
- speleding 4y agoYeah, there are reports of Gmail setting the Return-Path to the primary domain going back a decade ago. That makes the alternative domain pretty useless if you want to get SPF passing. Fastmail does the right thing FWIW, they switch the Return-Path to the alternative domain when you send from there.