From ladas at seznam.cz Wed Apr 3 11:43:31 2024 From: ladas at seznam.cz (ladas at seznam.cz) Date: Wed, 03 Apr 2024 13:43:31 +0200 Subject: wallace not start Message-ID: <23457066.6Emhk5qWAg@zbook> Hi everybody, since this morning cca 2:00 wallace at our server stop to work. After service restart I get only usable message: *wallace.service: main process exited, code=exited, status=2/INVALIDARGUMENT* I checked configuration at other running server and did not find any difference. Can somebody give me an advice, where to start to dig? Or is it possible to go over wallace at all and deliver the message without check? We use email gateway so it is not theoretically necessary. Thank you very much for any advice. Kolab16 runs at CentOS7, last updates installed -- Greetings, ladas -------------- next part -------------- An HTML attachment was scrubbed... URL: From ladas at seznam.cz Tue Apr 9 08:37:50 2024 From: ladas at seznam.cz (ladas at seznam.cz) Date: Tue, 09 Apr 2024 10:37:50 +0200 Subject: Secure Kolab server Message-ID: <2246590.OBFZWjSADL@zbook> Hi everybody, I installed new Kolab server at Alma9. At Knowledge Base the article Secure Kolab with Let?s Encrypt is signed as [Obsolete]. Where can I find actual version? -- Greetings, ladas From ladas at seznam.cz Wed Apr 10 17:37:58 2024 From: ladas at seznam.cz (ladas at seznam.cz) Date: Wed, 10 Apr 2024 19:37:58 +0200 Subject: Guam listener not working at clean installation Message-ID: <5458921.Sb9uPGUboI@zbook> Hi everybody, I installed clean server at Alma9 and by log file there is some problem with GUAM listener since the beginning. Log /var/log/guam/log/error.log is full of this lines: 2024-04-10 19:02:11.342 [error] <0.529.0>@kolab_guam_listener:init:46 Supervisor kolab_guam_sup had child imap started with kolab_guam_listener:start_link(imap, [{port,143},{imap_server,imaps},{rules,[{filter_groupware,[]}]},{tls_config,[{certfile,"/etc/pk..."},...]}]) at undefined exit with reason no match of right hand value {error,eafnosupport} in kolab_guam_listener:init/1 line 46 in context start_error 2024-04-10 19:02:11.342 [error] <0.530.0>@kolab_guam_listener:init:46 CRASH REPORT Process <0.530.0> with 0 neighbours crashed with reason: no match of right hand value {error,eafnosupport} in kolab_guam_listener:init/1 line 46 2024-04-10 19:02:11.343 [error] <0.527.0> CRASH REPORT Process <0.527.0> with 0 neighbours exited with reason: {{shutdown,{failed_to_start_child,imap,{{badmatch,{error,eafnosupport}},[{kolab_guam_listener,init,1,[{file,"/home/abuild/rpmbuild/BUILD/guam-0.9.13/apps/kolab_guam/src/kolab_guam_listener.erl"},{line,46}]},{supervisor,init,1,[{file,"supervisor.erl"},{line,330}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,851}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,814}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]}}},{kolab_guam,start,[normal,[]]}} in application_master:init/4 line 142 Guam daemon is running but server do not listen at 143 and 993 ports. Can somebody help, please? -- Greetings, ladas From laskov at festa.bg Thu Apr 11 08:30:51 2024 From: laskov at festa.bg (Valentin Laskov) Date: Thu, 11 Apr 2024 11:30:51 +0300 Subject: Guam listener not working at clean installation In-Reply-To: <5458921.Sb9uPGUboI@zbook> References: <5458921.Sb9uPGUboI@zbook> Message-ID: <6c2b5460-60d8-4834-bb91-ae5469121e61@festa.bg> Hi ladas, as a temporary workaround you can stop guam and set cyrus-imapd to listen to standard IMAP ports ? imap?? cmd="imapd"??? listen="imap"? prefork=5 ? imaps? cmd="imapd -s" listen="imaps" prefork=5 instead of ? imap?? cmd="imapd"??? listen="127.0.0.1:144" prefork=5 ? imaps? cmd="imapd -s" listen="0.0.0.0:9993"? prefork=5 or whatever you have there in /etc/cyrus.conf You may need to set cert files in /etc/imapd.conf The purpose of guam is to hide special folders as Calendar and others in kolab. You can set guam ( /etc/guam/sys.config ) to listen to other ports and continue debugging . You must set mail client appropriately to use new guam ports. Regards! V. Laskov ?? 10.4.2024 ?. ? 20:37, ladas at seznam.cz ??????: > Hi everybody, > > I installed clean server at Alma9 and by log file there is some problem with GUAM listener since the beginning. Log /var/log/guam/log/error.log is full of this lines: > > 2024-04-10 19:02:11.342 [error] <0.529.0>@kolab_guam_listener:init:46 Supervisor kolab_guam_sup had child imap started with kolab_guam_listener:start_link(imap, [{port,143},{imap_server,imaps},{rules,[{filter_groupware,[]}]},{tls_config,[{certfile,"/etc/pk..."},...]}]) at undefined exit with reason no match of right hand value {error,eafnosupport} in kolab_guam_listener:init/1 line 46 in context start_error > 2024-04-10 19:02:11.342 [error] <0.530.0>@kolab_guam_listener:init:46 CRASH REPORT Process <0.530.0> with 0 neighbours crashed with reason: no match of right hand value {error,eafnosupport} in kolab_guam_listener:init/1 line 46 > 2024-04-10 19:02:11.343 [error] <0.527.0> CRASH REPORT Process <0.527.0> with 0 neighbours exited with reason: {{shutdown,{failed_to_start_child,imap,{{badmatch,{error,eafnosupport}},[{kolab_guam_listener,init,1,[{file,"/home/abuild/rpmbuild/BUILD/guam-0.9.13/apps/kolab_guam/src/kolab_guam_listener.erl"},{line,46}]},{supervisor,init,1,[{file,"supervisor.erl"},{line,330}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,851}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,814}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]}}},{kolab_guam,start,[normal,[]]}} in application_master:init/4 line 142 > > Guam daemon is running but server do not listen at 143 and 993 ports. Can somebody help, please? > > -- > Greetings, ladas > > > > _______________________________________________ > users mailing list > users at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From ladas at seznam.cz Thu Apr 11 12:13:19 2024 From: ladas at seznam.cz (ladas at seznam.cz) Date: Thu, 11 Apr 2024 14:13:19 +0200 Subject: Guam listener not working at clean installation Message-ID: <9313137.rMLUfLXkoz@zbook> Hi Valentin, thank you very much for your fast answer. I know it is possible to bypass guam. I have one server without guam and it works well. I just would like to report problem and ask if it is bug or some configuration trouble to know where to dig. I tried to ask directly to Christian Mollenkopf, but I have no answer yet. -- With best regards, ladas Dne ?tvrtek 11. dubna 2024 10:30:51 CEST, Valentin Laskov napsal(a): > Hi ladas, > > as a temporary workaround you can stop guam and set cyrus-imapd to > listen to standard IMAP ports > > imap cmd="imapd" listen="imap" prefork=5 > imaps cmd="imapd -s" listen="imaps" prefork=5 > > instead of > imap cmd="imapd" listen="127.0.0.1:144" prefork=5 > imaps cmd="imapd -s" listen="0.0.0.0:9993" prefork=5 > > or whatever you have there in /etc/cyrus.conf > > You may need to set cert files in /etc/imapd.conf > > The purpose of guam is to hide special folders as Calendar and others in > kolab. You can set guam ( /etc/guam/sys.config ) to listen to other > ports and continue debugging . You must set mail client appropriately to > use new guam ports. > > Regards! > V. Laskov > > ?? 10.4.2024 ?. ? 20:37, ladas at seznam.cz ??????: > > Hi everybody, > > > > I installed clean server at Alma9 and by log file there is some problem with GUAM listener since the beginning. Log /var/log/guam/log/error.log is full of this lines: > > > > 2024-04-10 19:02:11.342 [error] <0.529.0>@kolab_guam_listener:init:46 Supervisor kolab_guam_sup had child imap started with kolab_guam_listener:start_link(imap, [{port,143},{imap_server,imaps},{rules,[{filter_groupware,[]}]},{tls_config,[{certfile,"/etc/pk..."},...]}]) at undefined exit with reason no match of right hand value {error,eafnosupport} in kolab_guam_listener:init/1 line 46 in context start_error > > 2024-04-10 19:02:11.342 [error] <0.530.0>@kolab_guam_listener:init:46 CRASH REPORT Process <0.530.0> with 0 neighbours crashed with reason: no match of right hand value {error,eafnosupport} in kolab_guam_listener:init/1 line 46 > > 2024-04-10 19:02:11.343 [error] <0.527.0> CRASH REPORT Process <0.527.0> with 0 neighbours exited with reason: {{shutdown,{failed_to_start_child,imap,{{badmatch,{error,eafnosupport}},[{kolab_guam_listener,init,1,[{file,"/home/abuild/rpmbuild/BUILD/guam-0.9.13/apps/kolab_guam/src/kolab_guam_listener.erl"},{line,46}]},{supervisor,init,1,[{file,"supervisor.erl"},{line,330}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,851}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,814}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]}}},{kolab_guam,start,[normal,[]]}} in application_master:init/4 line 142 > > > > Guam daemon is running but server do not listen at 143 and 993 ports. Can somebody help, please? > > > > -- > > Greetings, ladas > > > > > > > > _______________________________________________ > > users mailing list > > users at lists.kolab.org > > https://lists.kolab.org/mailman/listinfo/users ----------------------------------------- From ladas at seznam.cz Thu Apr 11 16:24:40 2024 From: ladas at seznam.cz (ladas at seznam.cz) Date: Thu, 11 Apr 2024 18:24:40 +0200 Subject: WEB GUI folders settings display INBOX only In-Reply-To: <6c2b5460-60d8-4834-bb91-ae5469121e61@festa.bg> References: <5458921.Sb9uPGUboI@zbook> <6c2b5460-60d8-4834-bb91-ae5469121e61@festa.bg> Message-ID: <2651614.k3LOHGUjKi@zbook> Hi everybody, at my new Kolab installation I switch guam off (because permanent listener crash) and reconfigure all configuration files with port 9993 to 993. I created new user and try to set his account. I discovered at Settings-Folders can see only INBOX. Even when I create new subfolder at INBOX folder, after refresh it disappeats. The same at special folders settings, only INBOX is seen in menu. Must I allow the display them somewhere? I thing at old versions it worked automaticaly. -- Greetings, ladas From ladas at seznam.cz Thu Apr 11 17:07:30 2024 From: ladas at seznam.cz (ladas at seznam.cz) Date: Thu, 11 Apr 2024 19:07:30 +0200 Subject: Fwd: WEB GUI folders settings display INBOX only Message-ID: <6617578.G0QQBjFxQf@zbook> Hi everybody, at my new Kolab installation I switch guam off (because permanent listener crash) and reconfigure all configuration files with port 9993 to 993. I created new user and try to set his account. I discovered at Settings-Folders can see only INBOX. Even when I create new subfolder at INBOX folder, after refresh it disappeats. The same at special folders settings, only INBOX is seen in menu. Must I allow the display them somewhere? I thing at old versions it worked automaticaly. Just an addition: I checked roundcube log and found is full this errors: [11-Apr-2024 19:04:51,342943 +0200]: PHP Error: required kolabformat module not found (GET /webmail/SKS0wTU52yUlrY25/?_task=settings&_action=folders) I checked installation packages and kolab is installed with all its relations. -- Greetings, ladas -------------- next part -------------- An HTML attachment was scrubbed... URL: From ladas at seznam.cz Fri Apr 12 19:49:09 2024 From: ladas at seznam.cz (ladas at seznam.cz) Date: Fri, 12 Apr 2024 21:49:09 +0200 Subject: Kolab at Debian12 Message-ID: <15163099.JCcGWNJJiE@zbook> Hi everybody, I installed Kolab at Alma9 last week, but up to now It not work properly. Guam listener crash, Folders at settings menu are not displayed, ... So I decided to try Debian12. It is funny story, because here I am not able even set repo to be possible to install Kolab. Is it really so broken? Here is my kolab.source file: Types: deb URIs: https://mirror.apheleia-it.ch/repos/Kolab:/16 Suites: Debian_12.0 Components: all Signed-By: /usr/local/share/keyrings/apheleia-keyring.pgp I downloaded and convert keyring file by: wget -O- https://mirror.apheleia-it.ch/repos/Kolab:/16/key.asc | gpg --dearmor --yes --output /usr/local/share/keyrings/apheleia-keyring.pgp when I try to update repos I get message: Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://security.debian.org/debian-security bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Ign:4 https://mirror.apheleia-it.ch/repos/Kolab:/16 Debian_12.0 InRelease Err:5 https://mirror.apheleia-it.ch/repos/Kolab:/16 Debian_12.0 Release 404 Not Found [IP: 212.103.80.162 443] Reading package lists? Done E: Repository ?https://mirror.apheleia-it.ch/repos/Kolab:/16 Debian_12.0 Release? does not contain a Release file. N: Updating from such a repository cannot be done securely and is therefore implicitly disabled. If I use old style apt source list, kolab.list: deb [signed-by=/usr/local/share/keyrings/apheleia-keyring.pgp] https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0/ ./ after repos update I get message: Hit:1 http://security.debian.org/debian-security bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Downloads:4 https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ InRelease [1?859 B] Err:4 https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ InRelease The following signatures could not be verified because the public key is not available : NO_PUBKEY A01D0CA80038D0DB Reading package lists? Done W: Error GPG: https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ InRelease: The following signatures could not be verified because the public key is not available : NO_PUBKEY A01D0CA80038D0DB E: Repository ?https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ InRelease? is not signed. N: Updating from such a repository cannot be done securely and is therefore implicitly disabled. Can somebody say what is wrong, please? Thak you. -- Greetings, ladas From mail at raptor2101.de Fri Apr 12 21:42:31 2024 From: mail at raptor2101.de (Raptor 2101) Date: Fri, 12 Apr 2024 23:42:31 +0200 Subject: Kolab at Debian12 In-Reply-To: <15163099.JCcGWNJJiE@zbook> References: <15163099.JCcGWNJJiE@zbook> Message-ID: <3292421.aeNJFYEL58@atacama-city> Hello ladas to be honest, I used kolab since roughly 2017 and maintained the current mail server way to long (old Ubuntu 18.04). Tried hard to migrate to something ubuntu 22.04. Tried docker deployment and even Alma9 inside a container, no luck on my side ... I was unable to get a working installation up and running, so I had to migrate to something else. greetings Raptor 2101 Am Freitag, 12. April 2024, 21:49:09 CEST schrieb ladas at seznam.cz: > Hi everybody, > > I installed Kolab at Alma9 last week, but up to now It not work properly. > Guam listener crash, Folders at settings menu are not displayed, ... So I > decided to try Debian12. It is funny story, because here I am not able even > set repo to be possible to install Kolab. Is it really so broken? > > Here is my kolab.source file: > Types: deb > URIs: https://mirror.apheleia-it.ch/repos/Kolab:/16 > Suites: Debian_12.0 > Components: all > Signed-By: /usr/local/share/keyrings/apheleia-keyring.pgp > > I downloaded and convert keyring file by: > wget -O- https://mirror.apheleia-it.ch/repos/Kolab:/16/key.asc | gpg > --dearmor --yes --output /usr/local/share/keyrings/apheleia-keyring.pgp > > when I try to update repos I get message: > Hit:1 http://deb.debian.org/debian bookworm InRelease > Hit:2 http://security.debian.org/debian-security bookworm-security InRelease > Hit:3 http://deb.debian.org/debian bookworm-updates InRelease > Ign:4 https://mirror.apheleia-it.ch/repos/Kolab:/16 Debian_12.0 InRelease > Err:5 https://mirror.apheleia-it.ch/repos/Kolab:/16 Debian_12.0 Release > 404 Not Found [IP: 212.103.80.162 443] > Reading package lists? Done > E: Repository ?https://mirror.apheleia-it.ch/repos/Kolab:/16 Debian_12.0 > Release? does not contain a Release file. N: Updating from such a > repository cannot be done securely and is therefore implicitly disabled. > > > If I use old style apt source list, kolab.list: > deb [signed-by=/usr/local/share/keyrings/apheleia-keyring.pgp] > https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0/ ./ > > after repos update I get message: > Hit:1 http://security.debian.org/debian-security bookworm-security InRelease > Hit:2 http://deb.debian.org/debian bookworm InRelease > Hit:3 http://deb.debian.org/debian bookworm-updates InRelease > Downloads:4 https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ > InRelease [1?859 B] Err:4 > https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ InRelease The > following signatures could not be verified because the public key is not > available : NO_PUBKEY A01D0CA80038D0DB Reading package lists? Done > W: Error GPG: https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ > InRelease: The following signatures could not be verified because the > public key is not available : NO_PUBKEY A01D0CA80038D0DB E: Repository > ?https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ InRelease? is > not signed. N: Updating from such a repository cannot be done securely and > is therefore implicitly disabled. > > > > Can somebody say what is wrong, please? Thak you. > > -- > Greetings, ladas > > > > > _______________________________________________ > users mailing list > users at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/users -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part. URL: From lennart at ackermans.ch Sat Apr 13 12:32:15 2024 From: lennart at ackermans.ch (Lennart Ackermans) Date: Sat, 13 Apr 2024 14:32:15 +0200 Subject: Kolab at Debian12 In-Reply-To: <15163099.JCcGWNJJiE@zbook> References: <15163099.JCcGWNJJiE@zbook> Message-ID: <3eb446a0-cf09-4891-8405-c48c42d9fdfb@ackermans.ch> I can update the repository with the old-style sources.list. Perhaps something went wrong with downloading or saving the key? I think you can save it as is (in .asc armor format), so you don't need to run gpg --dearmor. But it looks like a lot of important packages are still missing for Debian 12: # apt install kolab Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ?kolab : Depends: kolab-cli but it is not installable ???????? Depends: kolab-conf but it is not installable ???????? Depends: kolab-imap but it is not going to be installed ???????? Depends: kolab-mta but it is not going to be installed ???????? Depends: kolab-saslauthd but it is not installable ???????? Depends: kolab-server but it is not installable ???????? Depends: kolab-webclient but it is not going to be installed I'll stay on Debian 10 until we have these packages. Best, Lennart On 12-04-2024 21:49, ladas at seznam.cz wrote: > Hi everybody, > > I installed Kolab at Alma9 last week, but up to now It not work properly. Guam listener crash, Folders at settings menu are not displayed, ... So I decided to try Debian12. > It is funny story, because here I am not able even set repo to be possible to install Kolab. Is it really so broken? > > Here is my kolab.source file: > Types: deb > URIs:https://mirror.apheleia-it.ch/repos/Kolab:/16 > Suites: Debian_12.0 > Components: all > Signed-By: /usr/local/share/keyrings/apheleia-keyring.pgp > > I downloaded and convert keyring file by: > wget -O-https://mirror.apheleia-it.ch/repos/Kolab:/16/key.asc | gpg --dearmor --yes --output /usr/local/share/keyrings/apheleia-keyring.pgp > > when I try to update repos I get message: > Hit:1http://deb.debian.org/debian bookworm InRelease > Hit:2http://security.debian.org/debian-security bookworm-security InRelease > Hit:3http://deb.debian.org/debian bookworm-updates InRelease > Ign:4https://mirror.apheleia-it.ch/repos/Kolab:/16 Debian_12.0 InRelease > Err:5https://mirror.apheleia-it.ch/repos/Kolab:/16 Debian_12.0 Release > 404 Not Found [IP: 212.103.80.162 443] > Reading package lists? Done > E: Repository ?https://mirror.apheleia-it.ch/repos/Kolab:/16 Debian_12.0 Release? does not contain a Release file. > N: Updating from such a repository cannot be done securely and is therefore implicitly disabled. > > > If I use old style apt source list, kolab.list: > deb [signed-by=/usr/local/share/keyrings/apheleia-keyring.pgp]https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0/ ./ > > after repos update I get message: > Hit:1http://security.debian.org/debian-security bookworm-security InRelease > Hit:2http://deb.debian.org/debian bookworm InRelease > Hit:3http://deb.debian.org/debian bookworm-updates InRelease > Downloads:4https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ InRelease [1?859 B] > Err:4https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ InRelease > The following signatures could not be verified because the public key is not available : NO_PUBKEY A01D0CA80038D0DB > Reading package lists? Done > W: Error GPG:https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ InRelease: The following signatures could not be verified because the public key is not available : NO_PUBKEY A01D0CA80038D0DB > E: Repository ?https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ InRelease? is not signed. > N: Updating from such a repository cannot be done securely and is therefore implicitly disabled. > > > > Can somebody say what is wrong, please? Thak you. > > -- > Greetings, ladas > > > > > _______________________________________________ > users mailing list > users at lists.kolab.org > https://lists.kolab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From ladas at seznam.cz Wed Apr 17 16:02:52 2024 From: ladas at seznam.cz (ladas at seznam.cz) Date: Wed, 17 Apr 2024 18:02:52 +0200 Subject: Kolab at Debian12 In-Reply-To: <4566622.LvFx2qVVIh@atacama-city> References: <15163099.JCcGWNJJiE@zbook> <4566622.LvFx2qVVIh@atacama-city> Message-ID: <2233027.KlZ2vcFHjT@zbook> Hi Raptor2101. I would like to report that my Kolab at Alma9 seems to work now. I searched for bad package, but now when I switch GUAM off and install last packages by hand I can see the folders in settings menu too. It seems some dependences are broken. 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. -- Greetings, ladas Dne p?tek 12. dubna 2024 22:46:48 CEST, Raptor 2101 napsal(a): > Hello ladas > > to be honest, I used kolab since roughly 2017 and maintained the current mail > server way to long (old Ubuntu 18.04). Tried hard to migrate to something > ubuntu 22.04. > > Tried docker deployment and even Alma9 inside a container, no luck on my side > ... I was unable to get a working installation up and running, so I had to > migrate to something else. > > greetings > Raptor 2101 > > Am Freitag, 12. April 2024, 21:49:09 CEST schrieb ladas at seznam.cz: > > Hi everybody, > > > > I installed Kolab at Alma9 last week, but up to now It not work properly. > > Guam listener crash, Folders at settings menu are not displayed, ... So I > > decided to try Debian12. It is funny story, because here I am not able even > > set repo to be possible to install Kolab. Is it really so broken? > > > > Here is my kolab.source file: > > Types: deb > > URIs: https://mirror.apheleia-it.ch/repos/Kolab:/16 > > Suites: Debian_12.0 > > Components: all > > Signed-By: /usr/local/share/keyrings/apheleia-keyring.pgp > > > > I downloaded and convert keyring file by: > > wget -O- https://mirror.apheleia-it.ch/repos/Kolab:/16/key.asc | gpg > > --dearmor --yes --output /usr/local/share/keyrings/apheleia-keyring.pgp > > > > when I try to update repos I get message: > > Hit:1 http://deb.debian.org/debian bookworm InRelease > > Hit:2 http://security.debian.org/debian-security bookworm-security InRelease > > Hit:3 http://deb.debian.org/debian bookworm-updates InRelease > > Ign:4 https://mirror.apheleia-it.ch/repos/Kolab:/16 Debian_12.0 InRelease > > Err:5 https://mirror.apheleia-it.ch/repos/Kolab:/16 Debian_12.0 Release > > 404 Not Found [IP: 212.103.80.162 443] > > Reading package lists? Done > > E: Repository ?https://mirror.apheleia-it.ch/repos/Kolab:/16 Debian_12.0 > > Release? does not contain a Release file. N: Updating from such a > > repository cannot be done securely and is therefore implicitly disabled. > > > > > > If I use old style apt source list, kolab.list: > > deb [signed-by=/usr/local/share/keyrings/apheleia-keyring.pgp] > > https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0/ ./ > > > > after repos update I get message: > > Hit:1 http://security.debian.org/debian-security bookworm-security InRelease > > Hit:2 http://deb.debian.org/debian bookworm InRelease > > Hit:3 http://deb.debian.org/debian bookworm-updates InRelease > > Downloads:4 https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ > > InRelease [1?859 B] Err:4 > > https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ InRelease The > > following signatures could not be verified because the public key is not > > available : NO_PUBKEY A01D0CA80038D0DB Reading package lists? Done > > W: Error GPG: https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ > > InRelease: The following signatures could not be verified because the > > public key is not available : NO_PUBKEY A01D0CA80038D0DB E: Repository > > ?https://mirror.apheleia-it.ch/repos/Kolab:/16/Debian_12.0 ./ InRelease? is > > not signed. N: Updating from such a repository cannot be done securely and > > is therefore implicitly disabled. > > > > > > > > Can somebody say what is wrong, please? Thak you. > > > > -- > > Greetings, ladas > > > > > > > > > > _______________________________________________ > > users mailing list > > users at lists.kolab.org > > https://lists.kolab.org/mailman/listinfo/users > >