Christian thank you for detailed answer, I changed Zimbra webmailer charset to UTF8 for my user,and bingo there is no issue on Sogo webmail. My issue is resolved.
But I sent same mail with same settings(charset=windows-1254) also to gmail,and any issue with charset. Here is raw original and mail itself.Maybe this info will help in your research. --=_57f4fec5-485a-4223-8736-b20996434c81 Content-Type: text/plain; charset=windows-1254 Content-Transfer-Encoding: 8bit ���i�� ������ �yi �al��malar. --=_57f4fec5-485a-4223-8736-b20996434c81 Pazartesi, Ağustos 15, 2022 19:01 +03 tarihinde, "Christian Mack" ([email protected]) <[email protected]> şunu yazdı: Hello Am 15.08.22 um 10:53 schrieb "Hafiz Rafiyev" ([email protected]): > Pazartesi, Ağustos 15, 2022 10:38 +03 tarihinde, "Christian Mack" > ([email protected]) <[email protected]> şunu yazdı: > >> Hello >> >> Please open a bug report for this at https://bugs.sogo.nu/ >> And could you provide the raw source of that email too? >> >> >> Kind regards, >> Christian Mack >> >> Am 13.08.22 um 19:30 schrieb "Hafiz Rafiyev" ([email protected]): >>> Cumartesi, Ağustos 13, 2022 14:14 +03 tarihinde, "\"Hafiz Rafiyev\"" >>> ([email protected]) <[email protected]> şunu yazdı: >>> >>>> Hello, >>>> Have installed sogo with mailcow,everything working fine,only having >>>> charset/turkish character issue on sogos webmail side. >>>> Mails with Turkish characters seen as in picture attached. >>>> Subject is ok, only mail body has issue. >>>> Mobil iOS client(ActiveSync) also has't any issue,having problem only on >>>> sogos webmail. >>>> Here is some problematic turkish characters, >>>> ------------ >>>> öçşiğü İ >>>> ------------ >>>> >>>> Best regards,thanks in advance. >>>> Hafiz. >>> >>> Update to my own issue: >>> ------------------------------ >>> problem occurs with only HTML mail body, there is no issue with plain text >>> mail body. >>> Regards, >>> Hafiz. >>> >> >> > > > > Hello Christian , > Thank you for quicke response. > Just created account(expertaz) on https://bugs.sogo.nu/,but I haven't > suffcient permission to open bug(Limited Access Level), > I can attach raw source as txt. > Please see attached raw.txt . > > Best regards, > Hafiz. Problem is, in email plain text part: " [...] --=_ae3b2ffd-380d-4f64-ad53-6922b8d5cd42 Content-Type: text/plain; charset=windows-1254 Content-Transfer-Encoding: 8bit ýöçþýðü ÖÇÞÃÃÃœ Ãyi çalýþmalar. --=_ae3b2ffd-380d-4f64-ad53-6922b8d5cd42 [cut] " It says, that this text is written in charset=windows-1254 (Windows Turkish), but the characters actually are in UTF-8. Therefore SOGo can not display this correctly. The HTML part of this email on first glance seems correct. This seems to be a problem within Zimbra Mailer, which created this false plain text part. So in short the sender should fix his webmailer. In SOGo you see the HTML part, if there is one in the email, and the plain text part if there is no HTML part. Therefore you see the correct HTML part when receiving this broken email in web interface. When you create a new mail you can do so in plain text or in HTML (with additional plain text part). Standard setting in SOGo is using plain text. If you reply or forward an email, then SOGo will use the plain text part of the email to reply or forward. Because of this it seems as if SOGo is breaking this text, but in reality the email was broken before. You could switch in SOGo to send HTML emails. Then it would use the HTML part of the email when forwarding or replying. Hope this explanation was understandable. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre, Infrastruktur 78457 Konstanz +49 7531 88-4416
