We'd love to hear about it! Click here to go to the product suggestion community
I have the Google Suite and scanning incoming and outgoing emails. Both direction mail flow is working fine but When an outside user is sending mail on Google Group ID then this mail is delivering on the Google platform and Google is putting in forwarding pipe and the same time it is getting failed/bounced with below error on the Google Gsuite:
BouncedGoogle tried to deliver your message, but it was rejected by the server for the recipient domain <a href="relay-us-east-2.prod.hydra.sophos.com" target="_blank">relay-us-east-2.prod.hydra.<wbr>sophos.com</a> [188.8.131.52]. The error that the other server returned was: 550 5.7.1 Command rejected BouncedGoogle tried to deliver your message, but it was rejected by the server for the recipient domain <a href="relay-us-east-2.prod.hydra.sophos.com" target="_blank">relay-us-east-2.prod.hydra.<wbr>sophos.com</a> [184.108.40.206]. The error that the other server returned was: 550 5.7.1 Command rejected
What is happening in the background:
Outside User sending a mail to Group ID firstname.lastname@example.org -----> Mail received and scanned on the Sophos Central------->mail delivered on the group----> mail Forwarded from group: email@example.com to Individual recipients of this group as firstname.lastname@example.org (at this point the mail getting bounced)
We noticed an error message on the Sophos central as:
Sender local part <email@example.com> could not be validated for domain <mydomain.com> (as Mail sender).
After a long search on the internet, I found
1). This behavior was changed from Google sometime before to fight with DMARC “P=Reject” policy from various domains/email providers.
2). As Sophos is following RFC 5322 for incoming and outgoing emails but here looking that Google is violating this RFC ( I am not gone through the complete RFC).
Here, Google is saying that this is normal behavior of Google's group and it will rewrite mail header with a random ID as <firstname.lastname@example.org>. And this issue belongs to the Sophos central.
Looking expert guide to resolving the issue.
Hi Deepak Verma,
My apologies for this inconvenience. I would advise raising a support case and attaching the bounce email as a file attachment, for further investigation by our team.
Please also PM me with your case number and details so I can follow up accordingly.
In reply to FloSupport:
I had booked a case and we worked more than 4 months with Sophos. Finally, Sophos as accepted that this limitation of Sophos Central as
We use google groups for distribution lists. This sends the email out and then back in through the gateway. It looks like its coming externally, which will trip the header anomaly feature. We have our settings configured to reject header anomalies. so these wont even get delivered. Subaddressing is a common tactic used in google mail. Google allows you to give different variants of your email address to different third parties, and thus know who leaked your address to spammers. and block it if you want. for example; google will consider email@example.com the same as firstname.lastname@example.orgCurrently, central is blocking sending from subaddressed mailboxes. this has caused an issue with google customers.
More details are mentioned in the PM.
In reply to Deepak Verma:
This is related to the improvement ID XGE-9910, to include support for subaddressed mailboxes.
This improvement is continually being evaluated by our product team for future inclusion into the roadmap.