Hi Felix @fbartels ,

thanks for you quick and wide answer.
You bring nice drawbacks about the not really e2e situation!
Perhaps there is an option to integrate such a PDF encryption solution into the DeskApp?

Greetings

@icey one thing that just occurred to me is that since downloads for our customers have remained online you could request a trial key from our homepage and do an initial installation based on them.

Thanks for feedback. Workaround will be funny if you want to this for 300 contacts :) so I guess we need to wait for the implementation as suggested on the ticket you showed me.

@nschoote said in Kopano tabs not showing up after AD Extension Install:

msiexec /log kopano.log /i KopanoADS-1.1-76-noarch.msi

Thanks for replying. Previously i used the 64bit package and this time i used the noarch msi.

Upon executing the install command, windows installer reports an error that it could not open this installation packacge and to check if this is a valid windows installer-package.

Installing normally (double-clicking the file) works but there are still no kopano tabs.

What package should i use?

@dcuser said in REST calls to Kopano:

but it just spams errors about not finding the grapi-socket in the log

Yes, unfortunately the python version in centos/rhel 7 is way too old for he grapi backend, this is why this distribution is currently not supported for our rest api and in extension our new clients like Meet.

@dcuser said in REST calls to Kopano:

Does anyone know how to circumvent this problem and maybe get the rest api working on centos 7?

You could run kapi and grapi in Docker. e.g. with https://github.com/zokradonh/kopano-docker

@dcuser said in REST calls to Kopano:

Does anyone know when kopano core 9.0 will be released?

its still to early to give a concrete date for this.

@taurix There is currently no option to disable shared notifications on a per folder basis (or completely, for that matter). You can tinker around with the polling interval though, if you want to reduce the number of notifications.

https://stash.kopano.io/projects/KW/repos/kopano-webapp/browse/defaults.php#402

Configurable notifications for shared stores has been requested previously and we have a feature request open here: https://jira.kopano.io/browse/KW-2764 - it has not yet made it to the roadmap. If you have a commercial subscription, open a support case through the portal to indicate you are also interested in this.

if the external email accounts are things like @gmail, @yahoo, @Hotmail

you can simply setup redirect from that account to Kopano and then you reply from Kopano.

@kios_gmbh

it looks like your kopano server can’t connect to your MySQL server.

Perhaps MySQL isn’t running or perhaps the permission for the user “kopanoadmin” aren’t set properly.

I think you need to fix this before you attempt the restore of the backup.

The idea to store mails on disk is indeed compelling (especially the larger a message becomes). I have not formulated an idea yet as to what to do with the folder metadata, such as the hierarchy (defines which messages appears in what folder). Any glorious visions?

@compsos I think my colleges prefer when tickets are opened through https://portal.kopano.com/sdtickets. Since you currently do not have a subscription to map this ticket to you could also send a mail to info at kopano dot com and ask them to forward the mail.

I have solved this; the current version of my extra.cfg and config.php can be found below. What helped me solve this was an issue on git for sabre.io/katana.

One question that remains is this:
How do I change my alias / folderish config so that kdav’s folder on the filesystem can be /usr/share/webapps/kopano-kdav/server.php but the service is accessible from https://<FQDN>/kdav/server.php instead? The way it is, my URL ends in kopano-kdav as well which does not look nice but at least it works.

extra.cfg:

alias /kopano-kdav/ /usr/share/webapps/kopano-kdav/ fastcgi2 /kopano-kdav/ 127.0.0.1:9002 php { } folderish /kopano-kdav

config.php

// Location of the SabreDAV server. define('DAV_ROOT_URI', '/kopano-kdav/server.php');

Hi @mborus,

a ready made repository is only available for customers with a valid subscription. In regards to setup you could follow the official documentation and just do not install all packages, but rather just the one I mentioned above.

Of course having a local repository could make the installation easier. I have posted a simple way to generate such a Repo a few times here in the forum already (should turn up in search) one forum member also made a script for this https://github.com/thctlo/Kopano

If you do not want to deal with all the setup steps could could also just use the docker images from https://github.com/zokradonh/kopano-docker. Running docker run --rm -it -v $(pwd):/kopano/path zokradonh/kopano_utils will directly present you with a bash session.

Addendum:

cd /etc/php/7.3/cli/conf.d ln -s /etc/php/7.3/mods-available/mapi.ini

Well, figured it out myself, here’s how to solve it, if someone rans into it, too:

First, check the https-feature of apt with debug: option:

> apt-get update -o Debug::Acquire::https=1

In my case, there have been errors, like “no access to ca_certificates.crt” and so on.
The read/write-permissions of /etc/ssl/certs/ were set propperly, so i did reinstall the certificate_ca and apt-transport-https:

> apt install ca-certificates apt-transport-https

Verifying, with the debug outpout again to see if it got fixed:

> apt-get update -o Debug::Acquire::https=1

The errors are gone, doing an apt-get update

> apt-get update [...] OK:7 http://ftp.de.debian.org/debian stretch Release Ign:8 https://download.kopano.io/supported/core:/final/Debian_9.0 InRelease Ign:2 https://attic.owncloud.com/org/download/repositories/production/Debian_9.0 InRelease OK:9 http://download.owncloud.org/download/repositories/production/Debian_9.0 Release Ign:10 https://download.kopano.io/supported/webapp:/final/Debian_9.0 InRelease OK:11 https://download.kopano.io/supported/core:/final/Debian_9.0 Release OK:12 https://download.kopano.io/supported/webapp:/final/Debian_9.0 Release Paketlisten werden gelesen... Fertig

I stumbled upon the answer:

“The unique user attribute is the mapping between a mailbox in the database and the actual user in LDAP. Make sure this field is never changed as Kopano will perceive that as a user being deleted (and created), and will therefore orphan the user’s store.”

R.

Hi @scaarup,

I am using this kind of configuration on my own system, therefore it should work.

I am using it with lmtp transport, though (which should in any case be preferred). Your log line suggests you are delivering via a pipe.

What is logged at the dagent at time of delivery?

Hi @joja ,

you are indeed not able to open the inbox of an inactive user via imap. You should could use the new rest api (available from 8.7.0 onwards) for this. We have an internal poc for a mail client based on this, so it should generally work, but might be missing features.

Another possibility is to use python-kopano to script this directly, but you won’t be able to do this from windows as python-kopano depends on a few other kopano components. it does not need to run on the same system as your actual kopano installation, any linux system should do (wsl on windows is probably fine as well).

ok thats crazy…
i hate microsoft :-)

I just do not understand, if they ews already no longer support, why the hell then in the mac clients no ActiveSync is implemented. Like at Apple Mail too. For me is ActiveSync one of the best protocol to sync calendar,notes and mails :-(