From josef.vogl at gmx.de Tue Oct 8 08:40:09 2024 From: josef.vogl at gmx.de (Josef Vogl) Date: Tue, 08 Oct 2024 10:40:09 +0200 Subject: Kolab4 - some Questions Message-ID: Hello everyone, I have some questions about Kolab4: I use fetchmail to receive my mails from my providers and I use a policy to send my mails via my providers (Mittwald, Strato, GMX, Outlook.com). I have a server that is accessible via the internet. Is it possible to integrate this into Kolab4? Can I use Kolab4 for my production environment? I still have a lot to learn about Kubernets/Docker, but it's getting slow. Best regards Josef -------------- next part -------------- An HTML attachment was scrubbed... URL: From tr at erdfunkstelle.de Thu Oct 17 06:43:26 2024 From: tr at erdfunkstelle.de (Reitelbach, Thomas) Date: Thu, 17 Oct 2024 08:43:26 +0200 Subject: Kolab at Debian12 In-Reply-To: <3671581.vuYhMxLoTh@framework> References: <15163099.JCcGWNJJiE@zbook> <51a17c1f07bc37b7c5412f69e4690a69@der-he.de> <10654325.nUPlyArG6x@hornet> <3671581.vuYhMxLoTh@framework> Message-ID: <6f202e1012b68d4716a3746059945c78@erdfunkstelle.de> Hello list, thank you all for your efforts to make Kolab available for Debian 12! I had the time to test the OBS repository for Debian 12 yesterday. All packages do install as expected now, thank you very much. There is an issue with the Signature of the packages, though, but for my testing I ignored it and installed without checking package signatures. But after invoking setup-kolab there is an issue which I have to sort out. The kolab-webadmin is not working for me. After Login with Credentials "cn=Directory Manager" and my password I receive a blank white webpage as result. My investigations show that the command line "kolab lm" does not work, it results in connection errors and the logs do show ssl/tls errors (cert cannot be loaded by cyrus). It seems that the kolab certificates are not beeing generated at all, /etc/ssl/private does only contain the snakeoil cert but nothing kolab related. So, does anyone of you know, at which stage these kolab certificates would normally be generated? I would assume this happens when setup-kolab runs? Do you have any hints how to investigate further? Thank you in advance Thomas Am 27.09.2024 09:33, schrieb Christoph Erhardt: > The Debian_12.0 build was disabled for the following three required OBS > repositories: > * php-sabre-vobject > * pykolab-python3 > * roundcubemail-skin-chameleon > > I've enabled it; now all necessary packages should be available for > Debian 12. > > Best, > Christoph > > On Friday 20 September 2024 10:53:51 CEST Christian Hilberg wrote: >> Am Mittwoch, 18. September 2024, 10:01:10 CEST schrieb hede: >> > Am 17.04.2024 18:02, schrieb ladas at seznam.cz: >> > > ... >> > > At Debian12 I discussed repo problem with my collegue and at the end >> > > we force it work! BUT at repo are missing packages so installation is >> > > not possible. Maybe at Debian11 it can work. Repo seems more complete. >> > >> > The Repo seems still to be incomplete. There is one source package >> > missing: pykolab. This means, several binary packages are missing. >> > >> > But the Packages do build. Branching pykolab into some home repo for >> > Debian 12 does work, pykolab does build. It seems Python3 transition is >> > complete and just the Deb12 build is missing because it is disabled? Can >> > someone enable the build for Deb12 packages? >> >> Let me second this. :) >> >> (Bye)?, >> >> Christian > > > _______________________________________________ > users mailing list > users at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/users From kolab at mechtron.com.au Thu Oct 17 10:04:40 2024 From: kolab at mechtron.com.au (marko) Date: Thu, 17 Oct 2024 21:04:40 +1100 Subject: Kolab at Debian12 In-Reply-To: <6f202e1012b68d4716a3746059945c78@erdfunkstelle.de> References: <15163099.JCcGWNJJiE@zbook> <3671581.vuYhMxLoTh@framework> <6f202e1012b68d4716a3746059945c78@erdfunkstelle.de> Message-ID: <5926041.DvuYhMxLoT@chambourcin> I don't think setup-kolab creates any certificates, but I could be wrong. This article covers using let's encrypt for the certs, but also shows what format is needed for each component. https://kb.kolab.org/2023/03/secure-kolab-with-lets-encrypt/[1] good luck, I'm keen on seeing D12 working marko On Thursday, 17 October 2024 5:43:26 PM AEDT Reitelbach, Thomas wrote: > Hello list, > > thank you all for your efforts to make Kolab available for Debian 12! > I had the time to test the OBS repository for Debian 12 yesterday. All > packages do install as expected now, thank you very much. There is an > issue with the Signature of the packages, though, but for my testing I > ignored it and installed without checking package signatures. > > But after invoking setup-kolab there is an issue which I have to sort > out. > The kolab-webadmin is not working for me. After Login with Credentials > "cn=Directory Manager" and my password I receive a blank white webpage > as result. > My investigations show that the command line "kolab lm" does not work, > it results in connection errors and the logs do show ssl/tls errors > (cert cannot be loaded by cyrus). > > It seems that the kolab certificates are not beeing generated at all, > /etc/ssl/private does only contain the snakeoil cert but nothing kolab > related. > > So, does anyone of you know, at which stage these kolab certificates > would normally be generated? I would assume this happens when > setup-kolab runs? Do you have any hints how to investigate further? > > Thank you in advance > Thomas > > Am 27.09.2024 09:33, schrieb Christoph Erhardt: > > The Debian_12.0 build was disabled for the following three required OBS > > repositories: > > * php-sabre-vobject > > * pykolab-python3 > > * roundcubemail-skin-chameleon > > > > I've enabled it; now all necessary packages should be available for > > Debian 12. > > > > Best, > > Christoph > > > > On Friday 20 September 2024 10:53:51 CEST Christian Hilberg wrote: > >> Am Mittwoch, 18. September 2024, 10:01:10 CEST schrieb hede: > >> > Am 17.04.2024 18:02, schrieb ladas at seznam.cz: > >> > > ... > >> > > At Debian12 I discussed repo problem with my collegue and at the end > >> > > we force it work! BUT at repo are missing packages so installation is > >> > > not possible. Maybe at Debian11 it can work. Repo seems more > >> > > complete. > >> > > >> > The Repo seems still to be incomplete. There is one source package > >> > missing: pykolab. This means, several binary packages are missing. > >> > > >> > But the Packages do build. Branching pykolab into some home repo for > >> > Debian 12 does work, pykolab does build. It seems Python3 transition is > >> > complete and just the Deb12 build is missing because it is disabled? > >> > Can > >> > someone enable the build for Deb12 packages? > >> > >> Let me second this. :) > >> > >> (Bye)?, > >> > >> Christian > > > > _______________________________________________ > > users mailing list > > users at lists.kolab.org > > https://lists.kolab.org/mailman/listinfo/users > > _______________________________________________ > users mailing list > users at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/users -------- [1] https://kb.kolab.org/2023/03/secure-kolab-with-lets-encrypt/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jochen at jochen.org Mon Oct 28 06:42:12 2024 From: jochen at jochen.org (Jochen Kellner) Date: Mon, 28 Oct 2024 07:42:12 +0100 Subject: Kolab on Debian 12 - Package php-christianriesen-base32 Message-ID: <83cyjkd8zf.fsf@jochen.org> Hi, I've recently upgraded my kolab server to Debian 12 (bookworm). Today unattended-upgrades stumbled over php-christianriesen-base32. We have: root at jupiter:~# apt policy php-christianriesen-base32 php-christianriesen-base32: Installiert: 1.2.1-1 Installationskandidat: 1.2.1-1 Versionstabelle: 1.6.0-3 500 500 http://mirror.netcologne.de/debian bookworm/main amd64 Packages *** 1.2.1-1 510 510 https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ Packages 100 /var/lib/dpkg/status I'd hope that we could remove the kolab package and just use the debian one. I'll try running with the newer version... Jochen -- This space is intentionally left blank. From machniak at apheleia-it.ch Mon Oct 28 08:59:11 2024 From: machniak at apheleia-it.ch (Aleksander Machniak) Date: Mon, 28 Oct 2024 09:59:11 +0100 Subject: Kolab on Debian 12 - Package php-christianriesen-base32 In-Reply-To: <83cyjkd8zf.fsf@jochen.org> References: <83cyjkd8zf.fsf@jochen.org> Message-ID: <51f1038a-2c8c-4352-afb6-6bd10b68d610@apheleia-it.ch> On 28.10.2024 07:42, Jochen Kellner wrote: > > Hi, > > I've recently upgraded my kolab server to Debian 12 (bookworm). > Today unattended-upgrades stumbled over php-christianriesen-base32. > We have: > > root at jupiter:~# apt policy php-christianriesen-base32 > php-christianriesen-base32: > Installiert: 1.2.1-1 > Installationskandidat: 1.2.1-1 > This is a dependency of php-spomky-labs-otphp v4 package. However, in kolab-plugins we're using already v10, which does not require php-christianriesen-base32. So, we need to refresh these dependencies. I don't know about Debian, but on RHEL we use composer to manage dependencies, and all these packages aren't needed anymore (as everything is in /usr/share/roundcubemail/vendor folder). -- Aleksander Machniak Senior Software Engineer Apheleia IT AG PGP: 19359DC1 -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 495 bytes Desc: OpenPGP digital signature URL: From mihai at badici.ro Wed Oct 30 19:54:04 2024 From: mihai at badici.ro (Mihai Badici) Date: Wed, 30 Oct 2024 21:54:04 +0200 Subject: chwala invalid session Message-ID: <0441d35b-8fd7-4a5a-939c-7a6707478940@badici.ro> I try to assemble the server from the latest git repo. Working with chwala I found when accessing the web interface the session expire after one minute or so. When I try to access a file I got "invalid session" and I need to logout and logon again. This is also happens when I integrate the service in roundcube: I can login, I can browse files but after one minute the files become unavailable. I'm not sure how this should work; I can see in logs messages like: [30-Oct-2024 19:40:00 +0000]: Session regenerate: 15mnmfo7stpqet5bli0igc12eu -> i3huuadn3cm6klhst0tn0idn2k So somehow I think chwala try to keep the session valid but it not succeed.? Maybe a short description of the process can help me to check. Mihai -------------- next part -------------- An HTML attachment was scrubbed... URL: From mihai at badici.ro Wed Oct 30 20:09:19 2024 From: mihai at badici.ro (Mihai Badici) Date: Wed, 30 Oct 2024 22:09:19 +0200 Subject: chwala webdav with nextcloud Message-ID: <9cb54a90-04b2-4134-a873-1e46faceab41@badici.ro> I remember I had this working in the past. Now Nextcloud made the things complicated because by default it assign to? ldap users some random id's . But in advanced configuration it is still possible to change the id's to user's uid or mail ( seems to be distructive if you already use nextcloud but should work for new installations. After changing the mapping I still have problems because in this config: $config['fileapi_sources'] = array( ?'private-nextcloud' => array( ???????'driver' ??=> 'webdav', ???????'baseuri' ?=> 'http://localhost/cloud/remote.php/dav/files/', ???????'username' => '%u', ???????'password' => '%p', ???), the %u is not expanded in baseuri to the user name. I was able to solve that changing in functioninit() $this->client = newClient(array( 'baseUri'?=> rtrim($this->config['baseuri'], '/') . '/'.$this->config['username'].'/', ? but this need to be removed in functionget_relative_url($url) { $url= $this->client->getAbsoluteUrl($url); // added by me: $url=trim(str_replace($this->config['username'],'',$url),'/'); returntrim(str_replace($this->config['baseuri'], '', $url), '/'); ???} I think this can be useful for accessing private webdav folders so maybe can be added in the official driver, probably the simplest way is to allow wildcards in baseuri, this should keep the driver itself unchanged. Mihai -------------- next part -------------- An HTML attachment was scrubbed... URL: