What is the status of the usercert coolsolution?
Hi to the round,
I am still very new here and would like to contribute an app on this topic.
This app would also have to be updated.
Thank You
Version 5.0-1 just released and still no word on Kopano! Is the project dead? According to devs at kopano4ucs, they are waiting on univention…but univention says they are waiting on kopano, what’s going on? Is it time to to start looking for replacements, again!
1 Like
Hello!
With regard to Kopano, we are very concerned and, unfortunately, forced to prepare a plan for a possible short-term switch to alternative products (in this case: goodbye OSS, hello M$ CSS).
After Zarafa, Kopano, the “Kopano One” pipe-cracker, the lost domains and the expired certificates, we are somewhat unnerved.
It already got off to a bad start in 2021:
(German article, use automated translation if necessary)
And now here we are:
The last blog entry can be seen positively or negatively. But it is to be feared that the necessary resources are lacking to continue the project with the necessary seriousness.
BR,
TP
1 Like
Okay, unfortunately I’m learning more and more UCS and Kopano won’t work together anymore.
It is of no use to cry abaout that, but to think how to solve the situation.
I like Kopano with UCS because of the easy configuration of my mailing system and because of the easy connection to mobile devices via Z-Push,
Is there an solution with or from UCS for achieving a similar set of functions with another tool?
Is there a way to migrate the data of my users as easy as possible into such a solution?
If you are correct, my first approach would be to try if a standalone kopano installation can be connected to the OpenLDAP of UCS. But can you post some links or explanation why / where things are stuck? I see relatively new versions of kopano-core both in 5.0 and 4.4 in the development app store.
I just tested it and the following happend:
On a 4.4.8 I installed kopano-core, then tried to update to 5.0 => not possible, had to purge kopano.
I updated till 5.1 and looked for kopano in the appcenter - found a kopano-app.
I tried to install it - got an error. Looked in the appcenter again and couldn’t find kopano anymore (I first saw the app as “installed” and also the “Install now”-button, so this was most certainly a misinformation from some cach or whatever).
So for me it doesn’t look like there is a kopano-app for ucs 5.0 (also there was nothing announced officially).
The updated Kopano apps can currently only be found in the test appcenter. By now that should theoretically work for updates and new installations, but have not yet been tested. Feedback is welcome.
How to enable the test appcenter is described at Univention App Center for App Providers. It is not recommended to enable the test appcenter on production systems (especially not without a backup).
So are we right to assume that it’s only a matter of time until 4.x UCS-Kopano users can upgrade to 5.x?
If not, it would be nice just to tell us so we can investigate our options early.
Thank you very much!
Any preferred or most likely to work scenario that should be tested?
I could offer:
- 5.0 primary with mailserver on 4.4 with a fresh install of kopano from the dev app center and later upgrade the mailserver to 5.0 OR
- start with both servers on 5.0 and then install kopano on the mailserver from dev app center OR
- both servers on 4.4 with a working kopano and start upgrading from there
This should be the first step. Seeing if a new installation on 5.0 already works. If that is the case then also upgrade scenarios should work.
I have now tried:
Primary 5.0-1, dedicated mailserver 4.4-8 updated to 5.0-1, App Test Center enabled on both:
Install from gui fails.
2272 actions.install 22-01-11 14:22:52 [ INFO]: The following packages are BROKEN:
2272 actions.install 22-01-11 14:22:52 [ INFO]: * kopano4ucs
2272 actions.install 22-01-11 14:22:52 [ INFO]: * kopano-server-packages`
Tried from command line ‘univention-app install kopano-core’
with errors
W: Das Depot »Index of /univention-repository/5.0/maintained/component kopano-core_20211125115749/all/ Release« enthält keine Release-Datei.
W: Das Depot »Index of /univention-repository/5.0/maintained/component kopano-core_20211125115749/amd64/ Release« enthält keine Release-Datei.
and failing at
Die folgenden Pakete haben unerfüllte Abhängigkeiten:
kopano4ucs : Hängt ab von: python2.6 ist aber nicht installierbar
Next try:
Primary 5.0-1, dedicated mailserver 4.4-8, App Test Center enabled on both:
Tried from command line on mailserver ‘univention-app install kopano-core --do-not-install-master-packages-remotely’ WORKED.
From command line on mailserver ‘univention-app install kopano-core --only-master-packages’ UNSURE if failed or not, maybe worked.
root@p1:~# univention-app install kopano-core --only-master-packages
Resolving dependencies for kopano-core
Going to install Kopano Core (8.7.24.0-1)
Showing License agreement for kopano-core=8.7.24.0-1
Showing README for kopano-core=8.7.24.0-1
Press [ENTER] to continue
Configuring kopano-core=8.7.24.0-1
Registering component for kopano-core=8.7.24.0-1
File: /etc/apt/mirror.list
File: /etc/apt/sources.list.d/20_ucs-online-component.list
File: /etc/apt/sources.list.d/15_ucs-online-version.list
Ign:1 Index of /univention-repository/5.0/maintained/component kopano-core_20211125115749/all/ InRelease
OK:2 https://updates.software-univention.de ucs501 InRelease
Ign:3 Index of /univention-repository/5.0/maintained/component kopano-core_20211125115749/amd64/ InRelease
OK:4 https://updates.software-univention.de errata501 InRelease
Ign:5 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/all/ InRelease
Ign:6 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ InRelease
Ign:7 Index of /univention-repository/5.0/maintained/component kopano-core_20211125115749/all/ Release
Ign:8 Index of /univention-repository/5.0/maintained/component kopano-core_20211125115749/amd64/ Release
Ign:9 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/all/ Release
Ign:10 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Release
Holen:11 Index of /univention-repository/5.0/maintained/component kopano-core_20211125115749/all/ Packages [8.521 B]
Holen:12 Index of /univention-repository/5.0/maintained/component kopano-core_20211125115749/amd64/ Packages [40,2 kB]
OK:13 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/all/ Packages
OK:14 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
Ign:14 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
Ign:14 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
OK:14 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
Ign:14 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
Ign:14 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
Ign:14 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
Ign:14 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
OK:14 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
Es wurden 48,7 kB in 1 s geholt (61,3 kB/s).
Paketlisten werden gelesen…
W: Das Depot »Index of /univention-repository/5.0/maintained/component kopano-core_20211125115749/all/ Release« enthält keine Release-Datei.
W: Das Depot »Index of /univention-repository/5.0/maintained/component kopano-core_20211125115749/amd64/ Release« enthält keine Release-Datei.
W: Das Depot »Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/all/ Release« enthält keine Release-Datei.
W: Das Depot »Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Release« enthält keine Release-Datei.
Paketlisten werden gelesen…
Abhängigkeitsbaum wird aufgebaut…
Statusinformationen werden eingelesen…
Die folgenden zusätzlichen Pakete werden installiert:
kopano4ucs-schema
Die folgenden NEUEN Pakete werden installiert:
kopano4ucs-schema kopano4ucs-udm
0 aktualisiert, 2 neu installiert, 0 zu entfernen und 19 nicht aktualisiert.
Es müssen 3.706 B an Archiven heruntergeladen werden.
Nach dieser Operation werden 18,4 kB Plattenplatz zusätzlich benutzt.
WARNUNG: Die folgenden Pakete können nicht authentifiziert werden!
kopano4ucs-schema kopano4ucs-udm
Authentifizierungswarnung überstimmt.
Holen:1 Index of /univention-repository/5.0/maintained/component kopano-core_20211125115749/all/ kopano4ucs-schema 1.7.5-1 [1.874 B]
Holen:2 Index of /univention-repository/5.0/maintained/component kopano-core_20211125115749/all/ kopano4ucs-udm 1.7.5-1 [1.832 B]
Es wurden 3.706 B in 0 s geholt (18,8 kB/s).
Vormals nicht ausgewähltes Paket kopano4ucs-schema wird gewählt.
(Lese Datenbank … 96848 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von …/kopano4ucs-schema_1.7.5-1_all.deb …
Entpacken von kopano4ucs-schema (1.7.5-1) …
Vormals nicht ausgewähltes Paket kopano4ucs-udm wird gewählt.
Vorbereitung zum Entpacken von …/kopano4ucs-udm_1.7.5-1_all.deb …
Entpacken von kopano4ucs-udm (1.7.5-1) …
kopano4ucs-schema (1.7.5-1) wird eingerichtet …
kopano4ucs-udm (1.7.5-1) wird eingerichtet …
Unregistering component for kopano-core=8.7.24.0-1
File: /etc/apt/mirror.list
File: /etc/apt/sources.list.d/20_ucs-online-component.list
File: /etc/apt/sources.list.d/15_ucs-online-version.list
Ign:1 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/all/ InRelease
OK:2 https://updates.software-univention.de ucs501 InRelease
Ign:3 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ InRelease
OK:4 https://updates.software-univention.de errata501 InRelease
Ign:5 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/all/ Release
Ign:6 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Release
OK:7 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/all/ Packages
OK:8 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
Ign:8 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
Ign:8 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
OK:8 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
Ign:8 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
Ign:8 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
Ign:8 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
Ign:8 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
OK:8 Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Packages
Paketlisten werden gelesen…
W: Das Depot »Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/all/ Release« enthält keine Release-Datei.
W: Das Depot »Index of /univention-repository/5.0/maintained/component letsencrypt_20211006103329/amd64/ Release« enthält keine Release-Datei.
Potential script hook folder is unused: /var/lib/univention-appcenter/apps/kopano-core/local/hooks/post-install.d
Kopano options show up in frontend, also at user options. Will keep testing from this setup.
However, Kopano-Core does not show as installed in the app-center on the mailserver. Funny enough, on the primary it is listed as “installed in domain”.
Thanks for giving it a try @riess82,
these can be ignored as these are only warnings (as indicated by the W:) and not errors. These files are simply not automatically created for repos in the testing appcenter.
The dependency issue should be resolved now as well, upload to the test appcenter is currently running. The new version of the kopano4ucs package is 1.7.6-1.
thanks for the new kopano4ucs, the install on 5.0-1 nearly worked without errors. During the install I see:
Create kopano/repo/password
Module: kopano-cfg
File: /etc/apt/sources.list.d/kopano-core.list
File “”, line 37
except Exception, e:
^
SyntaxError: invalid syntax
Setting mail/antispam/learndaily
Module: kopano-cfg
File: /etc/cron.daily/univention-spamassassin
I haven’t done much python lately, but that syntax is still python 2.x iirc
and nearly at the end another error, probably not related to the first:
Running 70kopano4ucs-udm.inst failed (exitcode: 1)
Well, as fbartels said, it is not recommended to enable test appcenter on production systems.
Don’t get me wrong - I appreciate every step that brings us nearer to a solution but to be honest: Thats not the way to treat subscribers. UCS 5.0 was released on 25.05.2021, so we are talking about over 7 months of delay for the kopano-app in UCS 5 and now we are talking about customers to test it?! Really?
I’ve really been related to Kopano/Zarafa for a long time and advised my customers to use it, although beeing aware of some bugs in calendar, editor and other functions - but now I’m struggling about keeping this position for customers left behind! Soon we have a end of Support for UCS 4.4 and everything we got from Kopano till now is: “You can use the testing repos, but it is not recommended to use it in production…”
Sorry at that point and maybe I got it wrong, but thats not what I expected from Kopano!
1 Like
I fully agree, although I read somewhere in here, that the end of support for 4.4 is not really decided yet. If anyone has a link to that info / that thread, that would be great to have in this thread as well.
The comment of ThePreacher above was a warning for sure, but from what I see at the moment, things don’t look that bad.
I personally doubt the truth of kt1040’s very pessimistic remark at this point in time, as no link or source of info have been given.
1 Like
@riess82 You are absolutely right - Univention is saying here https://wiki.univention.de/index.php/Maintenance_Cycle_for_UCS that they will support UCS 4.4 * at least until the second quarter of 2022…
And I also want to apologize for my further posting, being a little bit emotional 
But again: My problem is, that I am having to tell my customers, that we will have to wait - ok, maybe we have at least time till 2022-02 but we have a lot of customers waiting to be upgraded to 5.0, so we also have to plan the updates and that will also take at least a few weeks…
Nevertheless, I am very hopefull to keep everything on track and looking forward to hear positive news from Kopano!
Thats a good one. I have personally helped out your employer multiple times over the years. And dating back as far as august last year, I have tried to get your company on board to contribute to the integration. Despite multiple meetings, with multiple people within your company and multiple “yes, we want to help” nothing further every came out of it.
1 Like
Since this is a private account, I’m really excited that you remember me in person.
Nevertheless - this is no personal attack on you @fbartels so pls don’t treat it here as an attack!
I am just wondering, as any other customer does, if we will have a solution in a near future…