[SOGo] BTS activities for Friday, December 24 2021
Title: BTS activities for Friday, December 24 2021 BTS Activities Home page: https://sogo.nu/bugs Project: SOGo For the period covering: Friday, December 24 2021 idlast updatestatus (resolution)categorysummary 5394 2021-12-24 00:35:02 updated (open) Backend Calendar Double calendar events. 5439 2021-12-24 00:41:32 updated (open) Backend General Endless invitation emails sent -- users@sogo.nuhttps://inverse.ca/sogo/lists
Re: [SOGo] some mails not displayed - regression?
attached is one of those mails that break sogo On 21.12.21 22:12, infoomatic (infooma...@gmx.at) wrote: Hi, I am seeing the same error as in https://www.sogo.nu/bugs/view.php?id=5174 so maybe this is a regression or a new bug. My system is: sogo 5.3.0 and sope-5.3.0 on FreeBSD 13.0 using dovecot 2.3.17. The error log: Dec 21 19:00:00 sogod [85897]: <0x0x2a9be474e088[NGImap4Client]> ERROR(-[NGImap4Client _processCommandParserException:]): catched IMAP4 parser exception NGImap4ParserException: unexpected char expected <(> Dec 21 19:00:00 sogod [85897]: [ERROR] <0x0x2a9bf87a82e8[NGImap4Connection]> Error fetching 3 uids for url: imap://u...@imap.jail:144/defunct/?tls=NO&tlsVerifyMode=default Dec 21 19:00:00 sogod [85897]: [WARN] <0x2a9be6c63588[SOGoMailFolder]:defunct> IMAP connection is broken, trying to reconnect... A folder with thousands of mails does not display even one mail when it contains one "defunct" mail. However, I have sorted out the mails that SOGo has problems with: those are mails that I have received locally injected from postfix complaining about something (non-delivery of a message), admin's well known MAILER-DAEMON sender, see headers (redacted) in [1]. Hope this is useful for the devs, I can provide more info if needed. Thanks for your great work! Robert [1] Return-Path: <> Delivered-To:u...@mydomain.com Received: from mail.mydomain.com by mailjail with LMTP id CNXlLTFJhmGRHgAAwzozfg (envelope-from <>) for; Sat, 06 Nov 2021 10:21:53 +0100 Received: by mail.mydomain.com (Postfix) id B0D1CE092E; Sat, 6 Nov 2021 10:21:53 +0100 (CET) Date: Sat, 6 Nov 2021 10:21:53 +0100 (CET) From:mailer-dae...@mydomain.com (Mail Delivery System) Subject: Undelivered Mail Returned to Sender To:u...@mydomain.com Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="85317E02FB.1636190513/mail.mydomain.com" Content-Transfer-Encoding: 8bit Message-Id:<20211106092153.b0d1ce0...@mail.mydomain.com> This is a MIME-encapsulated message. -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists--- Begin Message --- This is the mail system at host mail.mastersite.com. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system : host mx.dca.untd.com[64.136.44.37] said: 550 adm...@mysite.com is not a valid user (in reply to RCPT TO command) : host mx.dca.untd.com[64.136.44.37] said: 550 adm...@mysite.com is not a valid user (in reply to RCPT TO command) binXnbo6Z7u6S.bin Description: Delivery report Finished: test-unsubscribed Description: Message attachment --- End Message ---
[SOGo] Activesync stop syncing on iphone with underlying imap error
Hello, I have a couple iphone devices which Activesync can't sync after Apr 01 2021 (can't display messages after that date). The only thing in common is that see this kind of error on sogo.log: Dec 22 22:24:02 sogod [7639]: [ERROR] <0x0x55c464e4a2f0[NGImap4Connection]> could not fetch url: imap://USER@imap/INBOX/77538?tls=NO&tlsVerifyMode=default I tried resetting the device sync with sogo-tool, rebuilding dovecot indexes, but no luck. Any suggestions? -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] some mails not displayed - regression?
The error also occurs on Sogo 5.3.0 on Linux, however, it seems version 3.2.10 can cope with those mails On 21.12.21 22:12, infoomatic (infooma...@gmx.at) wrote: Hi, I am seeing the same error as in https://www.sogo.nu/bugs/view.php?id=5174 so maybe this is a regression or a new bug. My system is: sogo 5.3.0 and sope-5.3.0 on FreeBSD 13.0 using dovecot 2.3.17. The error log: Dec 21 19:00:00 sogod [85897]: <0x0x2a9be474e088[NGImap4Client]> ERROR(-[NGImap4Client _processCommandParserException:]): catched IMAP4 parser exception NGImap4ParserException: unexpected char expected <(> Dec 21 19:00:00 sogod [85897]: [ERROR] <0x0x2a9bf87a82e8[NGImap4Connection]> Error fetching 3 uids for url: imap://u...@imap.jail:144/defunct/?tls=NO&tlsVerifyMode=default Dec 21 19:00:00 sogod [85897]: [WARN] <0x2a9be6c63588[SOGoMailFolder]:defunct> IMAP connection is broken, trying to reconnect... A folder with thousands of mails does not display even one mail when it contains one "defunct" mail. However, I have sorted out the mails that SOGo has problems with: those are mails that I have received locally injected from postfix complaining about something (non-delivery of a message), admin's well known MAILER-DAEMON sender, see headers (redacted) in [1]. Hope this is useful for the devs, I can provide more info if needed. Thanks for your great work! Robert [1] Return-Path: <> Delivered-To:u...@mydomain.com Received: from mail.mydomain.com by mailjail with LMTP id CNXlLTFJhmGRHgAAwzozfg (envelope-from <>) for; Sat, 06 Nov 2021 10:21:53 +0100 Received: by mail.mydomain.com (Postfix) id B0D1CE092E; Sat, 6 Nov 2021 10:21:53 +0100 (CET) Date: Sat, 6 Nov 2021 10:21:53 +0100 (CET) From:mailer-dae...@mydomain.com (Mail Delivery System) Subject: Undelivered Mail Returned to Sender To:u...@mydomain.com Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="85317E02FB.1636190513/mail.mydomain.com" Content-Transfer-Encoding: 8bit Message-Id:<20211106092153.b0d1ce0...@mail.mydomain.com> This is a MIME-encapsulated message. -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] ANN: SOGo v5.4.0 released!
On Tuesday 21 of December 2021 20:36:54 Jordi Mallach wrote: > Hi! > > El dj. 16 de 12 de 2021 a les 15:08 -0500, en/na SOGo Reporter va > > escriure: > > Minor release, but many bug fixes. Download it now! > > NEW RELEASE > > ANNOUNCEMENT > > SOGo v5.4.0 > > Thanks for the new release! > > There's something wrong in the repo regarding the release. > > master doesn't currently have the 5.4.0 commit (just see the contents > of the Version file in the root of the > repo: https://github.com/inverse-inc/sogo/blob/5300bb71b795c2923e7b7aabd >dc8cd94883892ab/Version ), and commit > https://github.com/inverse-inc/sogo/commit/e59ff94de0349b8773a3bf68dfcb2 >87362dd2b2f which has the 5.4.0 tag doesn't appear to be in any branch. > > Jordi > > -- > Jordi Mallach Hi Jordi, yes, I also encountered this problem when I went to build deb packages published for the community. You can use git fetch for a specific commit: git fetch origin e59ff94de0349b8773a3bf68dfcb287362dd2b2f ...and consequently, you can then get the missing git tag: git fetch --tags Cheers -- Slávek signature.asc Description: This is a digitally signed message part.
RE: [SOGo] SOGo 2.4.0 - EAS does not support Reply-To?
So it's not implemented either in the current version (5.4)? Is there a reason (some problem to be expected)? It's kind of strange as this is a commonly used header field. Kai-Uwe Rommel From: users-requ...@sogo.nu On Behalf Of "Thomas Fuehrer" Sent: Thursday, December 23, 2021 8:12 AM To: users@sogo.nu Subject: AW: [SOGo] SOGo 2.4.0 - EAS does not support Reply-To? Hello, this is not yet implemented. There are some code-lines (commented) in SOGoMailObject+ActiveSync.m which gives a rough idea about what it takes to implement the "reply-to": SOGoMailObject+ActiveSync.m: // Reply-To - FIXME //NSArray *replyTo = [[message objectForKey: @"envelope"] replyTo]; //if ([replyTo count]) // [s appendFormat: @"%@", [addressFormatter stringForArray: replyTo]]; Regards Thomas Von: users-requ...@sogo.nu Im Auftrag von Kai-Uwe Rommel - ARS Gesendet: Dienstag, 21. Dezember 2021 12:25 An: users@sogo.nu Betreff: [SOGo] SOGo 2.4.0 - EAS does not support Reply-To? Hello, I'm still running an old SOGo 2.4.0 server for our family, on top of Dovecot and Postfix. We are using EAS to connect a couple of mobile devices to it. My son an I have now noticed that when we receive e-mail messages that contain Reply-To fields, then these are shown and honored in the web client (and of course when using e.g. Thunderbird to access the mailbox directly on Dovecot) but not on the mobile clients via EAS. We are using the "Nine" and "BlueMail" apps on Android. In both the Reply-To fields do not show up. Of course when we then reply to such a message, the reply goes to the original sender and not to the address in Reply-To. Is this a known limitation of the SOGo EAS implementation? Is it still present in SOGo 5.4? Kai-Uwe Rommel ARS Computer und Consulting GmbH, www.ars.de ein Unternehmen der TIMETOACT Group Garmischer Straße 7, 80339 München, Deutschland ARS - The Art of Software Engineering Software Engineering, Technologieberatung, IBM Software, IBM Lizenzmanagement Services Handelsregister München, HRB 101829, USt-ID: DE 155 068 909 Geschäftsführer: Joachim Gucker, Stefan Schäffer, Michael Arbesmeier Datenschutzerklärung: https://web.ars.de/datenschutz/ -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] confirm issue 5443 not resolved
I just ran into the same problem as reported in issue 5443. The save button does appear if you are creating a vacation auto-response, however, if there is an existing vacation forward in place, the button does not appear. So this issue is not resolved in 5.4.0. Steve -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] SOGo database schema
Good morning, all. OK, SOGo is the only working CalDAV / CardDAV server with an acceptable level of quality, at least to me, in the standard Debian repository. The two absolute requirements for me are LDAP authentication and a working user interface over https. So I have to use it, fair enough. By the way, if right now, when reading this, your mind comes up with nice repositories on GitHub or somewhere else, where I can download xxx or yyy, just stop and read again. I want to stick to a standard Debian compatible repository, this is not negotiable. Unfortunately, every time I have a look into the database schema, it is a shame, and I don't see any improvements over the years. First, the tables prefixes - seriously, what is the point of this, remove it. The tables should not be named sogo_xxx ? We are not any more in the 80s, when you were only able to use one database on a hosting provider. At least, make this an option, and not the default case. Second, the column prefixes - Why all the columns are called c_xxx, there is no point behind this except it is annoying and reduce queries readability. Do you have a dinosaur programmer in your team that advertise this as a poor way to avoid errors ? For these two "features", trust unit test, static code analysis and continuous integration to detect errors, not programming practices from the 70s. Third, why the table sogo_folder_info replicates the credentials of the database in each record ? (columns c_location, c_quick_location, c_acl_location) Even if you wanted to have multiple database, the credentials should not be stored in clear text in the database. This is both a security issue and the worst database design I have seen so far...just remove this feature. Fourth, in the same table, what are the columns c_path1, c_path2, c_path3 ??? If your database was properly designed, you wouldn't need these artefacts. For 2022, can you hire a database administrator to redesign your database schema ? Otherwise, I wish the whole team a happy new year. Andre Rodier. -- users@sogo.nu https://inverse.ca/sogo/lists
