Hi @okami,

since you have a supported version: can you get in contact with our support to properly reproduce and investigate? Thanks

ok, thanks. I will report this to my customer and see, if they want to upgrade or wait a bit more.

regards
Andre

@mclu said in Install failed. Nightly build Ubuntu 16.04 on missing dependency python3-vobject:

Is there somewhere a list of packages and a short purpose description of those?

Well each package has meta data which can be viewed with the corresponding packaging tools - ideally that should be enough.

nevermind - i found an old post from @fbartels and kopano-fsck is not intended for use with mails, just contacs and appointments, taks and so on.

Anyone ideas why i only see the mails in WebApp? I might go and try the DeskApp, but in that it will work i’m sure.

//entire

Thank you very much for the reply. The Ubuntu repository currently has the 8.6.2 as the installable version. I was able to remove the broken installation by using just the repository.
I was able to get it installed, but had an existing mysql database installed and the default options was to uninstall mysql.

root@nextcloud:~# apt-get install kopano-core Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libcgi-fast-perl libcgi-pm-perl libevent-core-2.1-6 libfcgi-perl libhtml-template-perl mysql-server-core-5.7 Use 'apt autoremove' to remove them. The following additional packages will be installed: kopano-backup kopano-common kopano-dagent kopano-gateway kopano-ical kopano-libs kopano-monitor kopano-search kopano-server kopano-spooler kopano-utils mariadb-client-10.1 mariadb-client-core-10.1 php-mapi python-kopano python-mapi Suggested packages: kopano-webapp Recommended packages: mariadb-server | default-mysql-server The following packages will be REMOVED: mysql-client-5.7 mysql-client-core-5.7 mysql-server mysql-server-5.7 The following NEW packages will be installed: kopano-backup kopano-common kopano-core kopano-dagent kopano-gateway kopano-ical kopano-libs kopano-monitor kopano-search kopano-server kopano-spooler kopano-utils mariadb-client-10.1 mariadb-client-core-10.1 php-mapi python-kopano python-mapi 0 upgraded, 17 newly installed, 4 to remove and 6 not upgraded. Need to get 0 B/13.8 MB of archives. After this operation, 30.3 MB disk space will be freed. Do you want to continue? [Y/n] n

I ran it with

root@nextcloud:~# apt-get install kopano-core --no-install-recommends Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libconfig-inifiles-perl libdbd-mysql-perl libdbi-perl libjemalloc1 libterm-readkey-perl mariadb-common Use 'apt autoremove' to remove them. The following additional packages will be installed: kopano-backup kopano-common kopano-dagent kopano-gateway kopano-ical kopano-libs kopano-monitor kopano-search kopano-server kopano-spooler kopano-utils php-mapi python-kopano python-mapi Suggested packages: kopano-webapp Recommended packages: mariadb-server | default-mysql-server The following NEW packages will be installed: kopano-backup kopano-common kopano-core kopano-dagent kopano-gateway kopano-ical kopano-libs kopano-monitor kopano-search kopano-server kopano-spooler kopano-utils php-mapi python-kopano python-mapi 0 upgraded, 15 newly installed, 0 to remove and 6 not upgraded. Need to get 0 B/3,414 kB of archives. After this operation, 14.0 MB of additional disk space will be used. Do you want to continue? [Y/n] y

and was successful!

Hi @lukistellar,

@lukistellar said in WebApp und PHP 7.3:

Why are you not including newer versions of the mapi.so module into your installers? For me it would make more sense to include modules for supported php versions, also if they are not the main version of the distribution.

We are using a local installation of https://build.opensuse.org/ to build and package Kopano for the individual distributions. This essentially means that when we are building packages for e.g. Debian 9 only packages that this distributions provides from its own repository can be pulled in as build dependencies (additionally its also not [easily] doable to pull in additional packages during build as build roots do not have access to the internet). These circumstances contribute to the fact that we cannot simply provide additional mapi.so for any given distribution, but have restricted ourselves to the php version that the distribution provides by default.

Also your postinstall script places the config files in the folder for the newest version of php on the system - this doesn’t make sense for me.

Yes, the postinst is not really beautiful, but allows us to use the same postinst for all our debian packaging.

All in all:

If you want to use a newer php version than the one that your distribution provides -> pick another distribution that provides this version by default Are you running an additional application on the same host as your Kopano, that requires a very specific version of php -> make use of virtualization and/or containerization to properly separate these two systems.

Hi @sgieschen,

does this still occur with the latest nightly?

@q5616417 sure, just send it to feedback at Kopano dot io.

@Robert

Do you want download this on the server side?
If so you have 2 options to do this.

You can create a dagent plugin this will check every incoming mail.
This is a example that move larger items then x to a different folder but you can use at as a base https://nextcloud.kopano.com/index.php/s/tMmyYmHfmCTYcQa
Please keep in mind that this script was written for Zarafa so probably you need to change some code and for Kopano you can use python-kopano and this make the script a lot easier

The other option is to use the ICS handler in Kopano to track the changes from a user.
See the documentation for python-kopano https://documentation.kopano.io/kopano_python_kopano/synchronization.html#ics

But in your first example you already specified a path that looked like a user backup, therefore I did not say anything about this.

I used the single user in my example, because a backup of all users would take too long. So I tested it with just mine. The backup script runs everyday with all users.

If someone is interested how to iterate through every user, here my snippet

for D in /mnt/backup/*; do [ -d "${D}" ] && kopano-backup -l debug --purge 0 $D; done

@boospy like a website within the app from where you can install plugins? If yes, then no there isn’t.

All the official plugins are packages and available from our repository.

For external integrations there is https://github.com/Kopano-dev/projects-and-resources (but it’s not a 100% compete list).

It works now really fine. I don’t really know the solution. It was fixed by an colleague. He have done something with postfix and LDAP. I asked him if he had time to post the solution here.

Is it safe to run the command “kopano-dbadm usmp” twice?

On first run, it seems that it was stopped somewhere in between with a timeout.

Recompiled 8.7.3 with vmime 0.9.2k1 - same result.

forwarded to https://github.com/kisli/vmime/issues/220

I could remedy the situation by a simple

touch /etc/kopano/admin.cfg

Now the cache was cleared and it seems everything works as expected.

Hi,
Iam experiencing the same issue and was unable to fix it so far.

I’ve installed Kopano using docker (repo: https://github.com/zokradonh/kopano-docker) as described in this article and pointed subdomain the Ocean droplet which I have created for this purpose.

I’ve accepted most of the default options but the FQDN and self_signed (as per screen shot).
The login page (webapp/?logon) is accessible via the subdomain as expected, however the error message “Cannot connect to Kopano Core.” appears when I try to login as demo user1.

running docker-compose ps shows most of the services (unhealthy)
docker-compose logs -f kopano_server shows errors

Can you please take a look at screen shots attached and advice?
Thank you!
kopanoScreenClip.png kopano23-ScreenClip.png

Hey Folks
I can confirm the problem with the umlauts in Outlook attachments.
Example Mail

Ever since years this problem has been showing up with 1 out of 10 Kopano software updates on our mailserver. It started with Zarafa 5 as we become part of the Zarafa family and it is still present today with Kopano 8.7.3
Luckily it gets fixed within a few days, however it is becoming really really frustrating over the time.