It is still being tested…

But it definitely makes a difference if Kopano has always and exclusively been installed from the Univention repositories or if Kopano was also updated from the Kopano repositories under UCS 4.4.

When upgrading to UCS 5.0, Kopano core, Kopano webapp, z-Push and univention-appcenter-docker are removed. Kopano can then “mostly” also no longer be installed via the UMC. Only after “apt-get install univention-appcenter-docker” has been executed, the Kopano and Z-Push apps can be installed again.

After that everything should run and work again.

Would be great if someone could test this.

I do have the same problem using the latest nightly builds.

Does anyone already have a solution to this?

Regards
Richard

@hooge exactly like you describe it. A whitelist is necessary.
Users are allowed by default, but any new device is a risk because you don’t know if the device belongs to the correct user or an attacker who got hold of the user’s credentials.
You’ll get the id with the initial connection attempt, and from there you allow the ids or not.
That would be an ideal solution and could be done with z-push-admin.

if you are asking for a final repository for Kopano One…

Ah yes apologies. I only recently starting using Kopano so still a bit confused about what everything is called. From what I understand there is no more Kopano One but there is Kopano Groupware.

Final repositories for Debian 11 Bullseye are available in the supported tree and therefor only available with a valid subscription.

Thanks also for claritying. I thought that would be the case, because when I looked for files here:

https://download.kopano.io/community/core%3A/

I only found these:

Debian 10 Ubuntu 18.04 and Ubuntu 20.04 RHEL 8

So far unfortunately we only have one client that had typical shared hosting IMAP email and we were about to loose them to due to lack of calendar sharing when someone suggested Kopano open-source. So we managed to put together an Ubuntu 20.04 installation using public information on the internet. The client has practically no budget.

@klipp Same problem here.
My clients are Microsoft Outlook 365 on Windows and the Nine/Nine Folders-App on Android using z-push.

It’s nice to have kopano back on track with UCS 5, but after the upgrade the plugins won’t install from the repos.
I do have a valid serial (pro, 20 users) but the upgrade hits a wall every time I try to complete it.

I already opened a case with kopano, but except from a whole lot of silence I get - silence.
Anybody any idea?
TIA
WL

Are you using the jodit html-editor plugin?
There are known, fixable issues related to drop-down controls in webapp.
++umgfoin.

Bumping my old thread, hoping someone with more skill than I has found a way to remove the default themes, or can help with the plugin option. Now that UCS5 and Kopano is working I am working on setting up the webapp again.

I’ve been asked to set a single, default and non-configurable theme for all users.

Is this possible yet? I tried looking at the plugin option, but I don’t know nearly enough to code it myself.
Thanks!

I found out that the email text is shown correct (in arial) for example if the receipient uses Outlook oder any other webservice like gmx.de.
but if the receipient uses also Kopano it is shown wrong (times new roman).

Hm… I’m not so happy with this.

@drauer d05de7c5-abac-4514-b86d-6c1e3b279a4a-image.png

production system updated as of today :)

Thank you!

We needed to fix another issue with this specific build and release job, since today noon the MDM package is back online.

Fixed: problem was user_safe_mode = yes

Hi,

last week we ran into this again. Last time we didn’t need to integrate the workaround Manuel mentioned, today we did. Let’s see if things get better. Is this a known bug?

Greets
Stephan

Hi @mhope ,
this seems to be an issue with recent versions of rocket.chat when viewed in outdated browsers.
I had this happen to me too, when trying to open it in an ancient version of opera, even without the kopano plugin (looked exactly like your screenshot).
You could still open channels using the search, but the list was broken.

Kind regards,
Geri

Hi,

case closed.
Deleting all permissions for shared calendar and also deleting permission “folder visible” for the mailbox folder.
Restart of complete kopano server and create the appropriate permissions it works.

Ulrich

I was able to test in 8.7 as well and this still exists in Kopano Core 8.7.