Hi,
I'm running into an issue where the CRM isn't picking up the real sender's email address.
I use Google Workspace and have my CRM fetch emails from an inbox that subscribes to a Google Group. Because of strict DMARC policies, Google automatically rewrites the sender's address to show as "Sender Name via Group" (e.g., idosell@brandsmanago.pl).
I can't bypass this using routing rules in Google Admin because it would break DMARC/DKIM and cause the emails to bounce.
However, Google always keeps the real sender's address in the X-Original-From and Reply-To headers. Could you update your email parser to check the X-Original-From header first, before defaulting to the standard From header?
Adding this simple fallback would fix the issue completely for anyone using Google Groups.
For now, I can work around this by leaving the Google group and setting up a redirect from the console to that user account—I'll manage somehow
Thanks!
Eryk Jakubik
I'm running into an issue where the CRM isn't picking up the real sender's email address.
I use Google Workspace and have my CRM fetch emails from an inbox that subscribes to a Google Group. Because of strict DMARC policies, Google automatically rewrites the sender's address to show as "Sender Name via Group" (e.g., idosell@brandsmanago.pl).
I can't bypass this using routing rules in Google Admin because it would break DMARC/DKIM and cause the emails to bounce.
However, Google always keeps the real sender's address in the X-Original-From and Reply-To headers. Could you update your email parser to check the X-Original-From header first, before defaulting to the standard From header?
Adding this simple fallback would fix the issue completely for anyone using Google Groups.
For now, I can work around this by leaving the Google group and setting up a redirect from the console to that user account—I'll manage somehow
Thanks!
Eryk Jakubik

Comment