@fbartels
Thank you for your help. Goal is to get it working on the test enviroment by the end of this week :) or I will call you next week ;).

Ok Kidm is running.

is the FQDN: https://SVGWMA-DEBI-01 <- This is what i defined at the installation? This is all for testing. Or do I need to add also the domain so: https://SVGWMA-DEBI-01.MYDOMAINNAME.DE ?

Now I have a already a Kopano running and I need to restore this database. How do I need to create the users for the existing users in the database?

@diederikdezee
Did you try the version I sent you via chat?

@fbartels said in Kopano One and Univention:

Hi @ichi123,

are you referring to the distributions listed in https://kopano.com/downloads-demo/ ? What ist listed directly on the .com domain is mostly marketing and does not necessarily reflect actual availability.

It is true however that we are working on a new app for ucs that includes Kopano One. Since Kopano One requires a subscription to e.g. create stores this app will not be a direct upgrade of the existing one(s), but rather a separate installation with an upgrade path.

We are discussing internally how to best convert users from the old app to the new one. More on that when the app will be available (but first there will be a 8.7.20 update to prepare for UCS 5.0).

The first release of an Univention 5.0 Beta is now nearly a year ago.
Kopano is currently in version 8.7.22.

You promised that Kopano 8.7.20 will prepare UCS 5.0

What happend so far?
Whats the Status?
UCS 4.4 will be EOL soon!
b19af9e6-6ccf-4916-b60f-c7531d180bc8-image.png

@hispeed I cannot give an eta at the moment. work has not yet started and we are busy with some customer projects already.

@mcdaniels said in License:

Do I just have to use the “lowest” subscription available?

Yes

@hispeed said in Restore Kopano V.10 Database into Kopano ONE:

Import the database means just restore it or is it a special process?

just a restore with the mysql cli (assuming you used mysqlbackup to create the dump).

@hispeed said in Restore Kopano V.10 Database into Kopano ONE:

Is Kopano ONE not based on the same Core? You said I make a downgrade so Kopano ONE is at the moment based on Kopano Core 9.X?

It is based on the same software, just uses a different version. The nightly downloads come from the main development branch, whereas proper releases come from their individual releases branches. For Kopano One we decided to use a build from the 9.x branch, which technically is a downgrade.

@mjdevilla said in Installation Help for Kopano One:

context canceled

I think this is rather a symptom, than the cause of your login troubles. But since you already have a support case open my recommendation would still be to follow this up directly with the Kopano support.

@mjdevilla said in Kopano One installed in Debian 10 but not launching webapp in browser:

however the port 443 is already in used by another service.

on the same machine? Port 443 is the default port when it comes to services being available through https. For any other port you would need to specify it when opening the address, which negatively impact the user experience.

@mjdevilla said in Kopano One installed in Debian 10 but not launching webapp in browser:

For example: in apache it is located in /var/www folder and will need to just setup /etc/apache2/config to be able to run the web app. How does it work for Kopano One? Please help to advise.

Kopano One delivers its own webserver to simplify the process of securely serving the WebApp. When following the instruction you have configured it in “11. Configure Kweb”. You could change the port of kweb in https://stash.kopano.io/projects/KGOL/repos/kweb/browse/scripts/kwebd.cfg?at=4323c71be30#50,55 (which also means that you would need to change the port in other places, such as server.cfg to open the right discovery document), but as said before then your users would need to remember a port on top of a domain name.

Generally speaking Kopano One should be installed on a new system, I am not sure if other applications running on the same server is a supported scenario.

Hi @Martin,

@martin said in Better documentation for Kopano ONE installation?:

I also found an error in the instructions.

actually the man page of the hostname utility recommends to use -f over -d:

-d, --domain Display the name of the DNS domain. Don't use the command domainname to get the DNS domain name because it will show the NIS domain name and not the DNS domain name. Use dnsdomainname instead. See the warnings in section THE FQDN above, and avoid using this option. -f, --fqdn, --long Display the FQDN (Fully Qualified Domain Name). A FQDN consists of a short host name and the DNS domain name. Unless you are using bind or NIS for host lookups you can change the FQDN and the DNS domain name (which is part of the FQDN) in the /etc/hosts file. See the warnings in section THE FQDN above und use hostname --all-fqdns instead wherever possible.

@stan23 said in Migration path from nightly builds to Kopano ONE:

The last line shows revision as 118, right?

Yes, that is correct.

Here is the same table from my Kopano One testsystem:

root@felix-kopano-one:~# mysql -e "select * from kopano.versions" +-------+-------+-------+----------+------------------+---------------------+ | major | minor | micro | revision | databaserevision | updatetime | +-------+-------+-------+----------+------------------+---------------------+ | 9 | 0 | 0 | 0 | 118 | 2020-11-27 15:01:19 | | 9 | 0 | 12 | 0 | 118 | 2020-11-27 15:01:19 | | 9 | 0 | 13 | 0 | 118 | 2020-12-22 15:25:08 | +-------+-------+-------+----------+------------------+---------------------+ root@felix-kopano-one:~# dpkg -l | grep kopano-server ii kopano-server 9.0.13.0.1c83ba69f-0+debian10~17.1 amd64 Server component for Kopano Core

Hi @thomash,

repositories for Ubuntu 20.04 are still in the works but expected rather soon.

The commands you need are the following:

kopano-admin -L -> list known groups kopano-admin --details my-group --type group -> get details (such as members) of your group kopano-admin --sync -> update user information in Kopano from your ldap

Hi @the_cranberries,

from the posted messages it is not directly clear what the issue is, further input could be found in the javascript console of your browser (maybe the time between your client and the server is not in sync?) or in the logging of Kopano Konnect (the OpenID Provider).

PS: since you have a subscription for Kopano One the recommended approach to get support is to directly open a ticket with the Kopano helpdesk. This place is just a forum for the community and not an official support channel.

Hi @bmann,

similar to how it is with our general release (the packages that you were referring to are the nightly builds), the packages of Kopano One can only be fully used by Kopano customers with a valid subscription.

You can install the software without a valid subscription but the server will prevent you from creating users until a license file has been supplied.

Hi @shwb,

@shwb said in integrate Amavis directly into Fetchmail:

Is it possible to integrate Amavis directly into Fetchmail?

I think it was possible to integrate Spamassassin directly into fetchmail so that it processes mails before passing them on to kopano-dagent.

But to avoid the problem of mail domains not being know locally you can also configure fetchmail to deliver the mail to a specific local user, this is done with the is user@domain here in fetchmail.

@hispeed Thank you… most welkom :-)

@fbartels Ok, got it. Thanks!

@fbartels said in What happens if the subscription runs out?:

Hi @grl,

@grl said in What happens if the subscription runs out?:

What happens if the subscription to kopano one runs out?
Its clear that there won’t be any updates - but will it stay usable at the current state?

You can easily simulate what happens when you remove your license key and restart the kustomerd process (a restart may not be necessary as the service was afaik design to detect changes license files directly).

And the hard version
deactivate the autostart customer service
(systemctl disable kopano-kustomerd.service)
reboot the server and open the web app
No more work possible;)