[SOGo] ***Solved***Re: Sogo webmail turkish character issue
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" (christian.m...@uni-konstanz.de) şunu yazdı: Hello Am 15.08.22 um 10:53 schrieb "Hafiz Rafiyev" (ha...@bulutek.net): > Pazartesi, Ağustos 15, 2022 10:38 +03 tarihinde, "Christian Mack" > (christian.m...@uni-konstanz.de) ş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" (ha...@bulutek.net): >>> Cumartesi, Ağustos 13, 2022 14:14 +03 tarihinde, "\"Hafiz Rafiyev\"" >>> (ha...@bulutek.net) ş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
Re: [SOGo] Sogo webmail turkish character issue
Hello Am 15.08.22 um 10:53 schrieb "Hafiz Rafiyev" (ha...@bulutek.net): Pazartesi, Ağustos 15, 2022 10:38 +03 tarihinde, "Christian Mack" (christian.m...@uni-konstanz.de) ş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" (ha...@bulutek.net): Cumartesi, Ağustos 13, 2022 14:14 +03 tarihinde, "\"Hafiz Rafiyev\"" (ha...@bulutek.net) ş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 smime.p7s Description: S/MIME Cryptographic Signature
Re: [SOGo] ANN: official transfer to Alinto
Dear users, The signing issue on rpm packages shall now be fixed. Sébastien Le Samedi, Août 13, 2022 16:46 CEST, Jürgen Echter (j.ech...@echter-kuechen-elektro.de) a écrit: Am Montag, August 08, 2022 21:24 CEST, schrieb "Francis Lachapelle" (flachape...@inverse.ca) : > Dear community users, > > In the upcoming days, we will officially transfer the ownership of the SOGo > open source project to Alinto. There will be two major impacts to this > transfer: > > - Members of this mailing list will need to resubscribe. The mailing list > address won't change (users@sogo.nu), but the infrastructure will moved to a > new server (https://mailing.sogo.nu/) with no data migration. > - Binary packages of SOGo and SOPE will be available from a different URL > (https://packages.sogo.nu). The installation instructions on the Website will > be updated accordingly. > > Let me know if you have any question. > > Thank you, > > Francis > -- > users@sogo.nu > https://inverse.ca/sogo/lists Hi, i guess the new repos should already work, but it seems the packages are not signed right now (RockyLinux 8). Package sogo-5.7.1.20220813-1.el8.x86_64.rpm is not signed Package sogo-tool-5.7.1.20220813-1.el8.x86_64.rpm is not signed Package sope49-cards-5.7.1.20220813-1.el8.x86_64.rpm is not signed Package sope49-gdl1-contentstore-5.7.1.20220813-1.el8.x86_64.rpm is not signed Greetings and thanks for all your hard work. Juergen
Re: [SOGo] Sogo webmail turkish character issue
Pazartesi, Ağustos 15, 2022 10:38 +03 tarihinde, "Christian Mack" (christian.m...@uni-konstanz.de) ş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" (ha...@bulutek.net): > > Cumartesi, Ağustos 13, 2022 14:14 +03 tarihinde, "\"Hafiz Rafiyev\"" > > (ha...@bulutek.net) ş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. > > > > > -- > Christian Mack > Universität Konstanz > Kommunikations-, Informations-, Medienzentrum (KIM) > Abteilung IT-Dienste Forschung, Lehre, Infrastruktur > 78457 Konstanz > +49 7531 88-4416 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. Return-Path: Delivered-To: ha...@bulutek.net Received: from posta.bulutek.net ([172.22.1.253]) by 4281976300a9 with LMTP id 2HkdHd4E+mLumAEAZKZm+g (envelope-from ) for ; Mon, 15 Aug 2022 11:33:34 +0300 Received: from mx02.cantekstil.com.tr (mx02.cantekstil.com.tr [212.174.240.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by posta.bulutek.net (buluTek) with ESMTPS id D643BFFDE1 for ; Mon, 15 Aug 2022 11:33:26 +0300 (+03) Received: from mx02.cantekstil.com.tr (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 29BAC66058 for ; Mon, 15 Aug 2022 11:33:13 +0300 (+03) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cantekstil.com.tr; s=mailsec; t=1660552393; bh=78nzVGlXpynm6V20blHL7oXtJLwlhWcBz97UEolnPM8=; h=Date:From:To; b=cOmAWPayM7LVWYYvVOospwGgtZks8PIrWNRDDOlDwQ8LByNYc2hLSIisctHxxtJWx C7645uLpAMUTD3EWwxidYgkqVPBykPO7eC00OjlGwUjMMNwoeE6C11T9WXQUyPEUVu 5XDAvvmC8ruc7fjeGW2moWTp9Su1EQRJPc0sIRLE= X-IMSS-DKIM-Authentication-Result: mx02.cantekstil.com.tr; sigcount=0 Received: from mx02.cantekstil.com.tr (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 12D5F66050 for ; Mon, 15 Aug 2022 11:33:13 +0300 (+03) Received: from fabmail.cantekstil.com.tr (unknown [192.168.0.7]) by mx02.cantekstil.com.tr (Postfix) with ESMTPS for ; Mon, 15 Aug 2022 11:33:12 +0300 (+03) Received: from localhost (localhost.localdomain [127.0.0.1]) by fabmail.cantekstil.com.tr (Postfix) with ESMTP id AC7DC5AE4831 for ; Mon, 15 Aug 2022 11:33:12 +0300 (+03) X-Virus-Scanned: amavisd-new at fabmail.cantekstil.com.tr Received: from fabmail.cantekstil.com.tr ([127.0.0.1]) by localhost (fabmail.cantekstil.com.tr [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id wunfluep2HqC for ; Mon, 15 Aug 2022 11:33:12 +0300 (+03) Received: from fabmail.cantekstil.com.tr (localhost.localdomain [127.0.0.1]) by fabmail.cantekstil.com.tr (Postfix) with ESMTP id 8C1795AE475C for ; Mon, 15 Aug 2022 11:33:12 +0300 (+03) Date: Mon, 15 Aug 2022 11:33:12 +0300 (EET) From: Hafiz Rafiyev To: hafiz Message-ID: <1120256124.4079226.1660552392526.javamail.zim...@cantekstil.com.tr> Subject: =?windows-1254?B?9uf+afD8?= MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_ae3b2ffd-380d-4f64-ad53-6922b8d5cd42" X-Mailer: Zimbra 8.8.15_GA_4173 (ZimbraWebClient - GC104 (Win)/8.8.15_GA_4177) Thread-Index: 0jShvD3QKUIA5nNLSa8xIaqCt0GwWQ== Thread-Topic: =?utf-8?B?w7bDp8WfacSfw7w=?= X-TM-AS-GCONF: X-TM-AS-SMTP: 1.0 ZmFibWFpbC5jYW50ZWtzdGlsLmNvbS50cg== aGFmaXpyQGNhbnRla3N0aWwuY29tLnRy X-TM-AS-ERS: 192.168.0.7-127.9.0.1 X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-27078.006 X-TM-AS-User-Approved-Sender: Yes X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-27078.006 X-TMASE-Result: 10--1.975700-10.00 X-TMASE-MatchedRID: 7qa34l9RQDnYlcmKh74KH1ICmG2RRehovO61PPXizylOaDdl7pggvfcw yVYGZr7IY1mVlKjrUUw6webmdkR8JfNVxHvQsvu65BgEdUqqANR9LQinZ4QefPKK1/oD8TJz8m+ hzBStanuMdqa93A5e7bBw13yf7RsBphvBXNoP5VBBZnq4bdckGxXiB/yVN7qN0UCXaMjOtY8= X-IMSS-DKIM-White-List: No X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0 ARC-Seal: i=1; s=dkim; d=bulutek.
Re: [SOGo] Which database schema for SOGo 5.7? - Danke
Hallo Christian, wollte nur kurz als Rückmeldung Danke für die Erklärung mit dem SOGo-Datenbank-schema sagen (und auch die vielen hilfreichen Kommentare in der Vergangenheit). Wir werden dann wohl aufgrund der genannten Vorteile die Datenmigration über ein Backup via sogo-tool beim Quellsystem und Import via sogo-tool in das neuere 9T-Schema beim Zielsystem bewerkstelligen (*). (*) Unter der Berücksichtigung von möglichen Memcached-Seiteneffekten (https://www.mail-archive.com/users@sogo.nu/msg26765.html). Viele Grüße aus Hamburg Dirk -- Dr. Dirk Schäfer Technische Universität Hamburg - Rechenzentrum - Am Schwarzenberg-Campus 3 D-21073 Hamburg +49 40 42878 2730 www.tuhh.de/rzt
Re: [SOGo] Sogo webmail turkish character issue
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" (ha...@bulutek.net): Cumartesi, Ağustos 13, 2022 14:14 +03 tarihinde, "\"Hafiz Rafiyev\"" (ha...@bulutek.net) ş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. -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre, Infrastruktur 78457 Konstanz +49 7531 88-4416 smime.p7s Description: S/MIME Cryptographic Signature
Re: [SOGo] Feature-Request: Add UnifiedPush / OpenPush
Hello This is the user mailinglist, not the support one ;-) You should open two bug reports at https://bugs.sogo.nu/ with severity feature request. There you can provide all infos needed for each of those interfaces. Kind regards, Christian Mack Am 13.08.22 um 11:47 schrieb "The User" (public-mb@shayan.digital): Dear Support, I would be quite happy if you would integrate UnifiedPush in your application and (as soon as it is also available) OpenPush. This is an important milestone towards independence from the BIG-TECH cloud services like Google and Microsoft. The community would certainly appreciate this feature! UnifiedPush: UnifiedPush is a set of specifications and tools that lets the user choose how push notifications* are delivered. All in a free and open source way. Further information: https://unifiedpush.org/ OpenPush: The OpenPush project aims to create a free and open source self-hosted replacement for Android Push Notifications usually sent through Google's proprietary Firebase Cloud Messaging platform. This started as a PrototypeFund project. Development is still ongoing. Further information: https://bubu1.eu/openpush/ With kind regards, The User -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre, Infrastruktur 78457 Konstanz +49 7531 88-4416 smime.p7s Description: S/MIME Cryptographic Signature
