We'd love to hear about it! Click here to go to the product suggestion community
If the email it will often be garbled, and the email title will also be garbled. After many tests, this situation will be caused by MTA mode.
The official said fix it in mr-4 2 months ago, but I didn't fix it. It's crazy
Please fix this problem as soon as possible. This problem has a great impact on the email
Email Like This:
Content-Type: text/plain; charset="gb2312"
Content-Type: text/html; charset="gb2312"
I have the exact same problem with SFOS 17.5.4 MR-4-1 on Sophos XG 135 device with MTA mode. Random messages will come through garbled and corrupt looking very similar to the above.
[#8783646] Web support query
In reply to Louis Swanepoel:
Sorry, I can't solve this problem. It needs to be solved officially. The official said it was solved in MR4, but it was not solved.
In reply to Ben ni:
See this thread: https://community.sophos.com/products/xg-firewall/f/email-protection/112215/some-incoming-messages-end-up-with-mime-content-in-message-body-exchange-2016-xg-17-5-mr4
In reply to Jelle:
I sympathize with you and hope that the authorities can start to solve the problem immediately or give a temporary solution
We are also dealing with this. Its a huge problem and the fact that its still happening after this long is concerning and in the process of finding a new appliance after 7 years of using Astaro/Sophos. We are having to send email straight to office 365 and dangerous amounts of spam and phishing are getting through to users. I cannot just spend the money on another spam filter because budget was already spent on Sophos that I haven't been able to use for months. When do we get our money refunded? Tons of complaints coming from upper management.
In reply to DannyBoy2042:
For months, like you, I have had to deliver mail to third-party services
Hi Ben ni
Apologies for this, our team is currently investigating a related ID (NC-44646). Would it be possible to please raise a support case referencing this ID and sending me your case number for tracking purposes?
In reply to FloSupport:
This ID has been resolved in SFOS 17.5 MR6.