Hi Felix,
Thank you, it’s work like expected.
Marc

I can trigger this error with Outlook 2019 by setting a reply to within the mail. I have created https://jira.kopano.io/browse/KC-1353 for followup.

@djtremors said in Migration from zarafa:

connect as default

that is a simplification within kopano-client (can’t seem to find the code location for it) to make it easier to get the switch from zarafa, to kopano. “default:” its an alias for the usual file sockets.

For kopano-cli you can configure your desired socket in admin.cfg (which is still the same as it was before with kopano-admin)

fixed mine by changing ${prefix} in the systemd service file to /usr

:before:
root@anuke:~ $ systemctl status kopano-statsd.service
● kopano-statsd.service - Kopano Groupware Core Statistics Daemon
Loaded: error (Reason: Invalid argument)
Active: inactive (dead) since Mon 2018-11-26 17:14:00 AEDT; 1 day 1h ago
Docs: man:kopano-statsd(8)
man:kopano-statsd.cfg(5)
Main PID: 22878 (code=exited, status=0/SUCCESS)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
root@anuke:~ $ vi /etc/systemd/system/multi-user.target.wants/kopano-statsd.service
root@anuke:~ $ systemctl daemon-reload
root@anuke:~ $ systemctl restart kopano-statsd.service

:after:
root@anuke:~ $ systemctl status kopano-statsd.service
● kopano-statsd.service - Kopano Groupware Core Statistics Daemon
Loaded: loaded (/lib/systemd/system/kopano-statsd.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2018-11-27 18:15:26 AEDT; 10s ago
Docs: man:kopano-statsd(8)
man:kopano-statsd.cfg(5)
Main PID: 27440 (kopano-statsd)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/kopano-statsd.service
└─27440 /usr/lib/x86_64-linux-gnu/kopano/kopano-statsd

Nov 27 18:15:26 anuke systemd[1]: Started Kopano Groupware Core Statistics Daemon.
Nov 27 18:15:26 anuke kopano-statsd[27440]: [=======] Starting kopano-statsd 8.7.80 (uid 0)
Nov 27 18:15:26 anuke kopano-statsd[27440]: [=======] Starting kopano-statsd 8.7.80 (uid 998)

Hi Manfred,

I will try to do so. I’ve sent you a mail.

Best Jan

Of course you should always get the latest version of the particular branch. The packages are not for looking at like in an art gallery, they are there to be installed.

I have found a work around: add a secondary emailaddress user2@domain1.net to user2.

In my case I stop kopano-server because I am paranoid hence I take a dump of the database (which indeed happens while kopano-server is running) plus a physical copy of /var/lib/MySQL (which requires the database to be stopped too) and then a physical copy of the disk of the virtual machine.

Paranoia that’s what it is called.

hey @robing,
I am monitoring the RTT value given by the kopano-stats script:

0_1542890608202_a9dbd24e-7b94-4a16-b791-7a6315b54328-image.png

Our cluster has been up for 6 weeks and 3 days. The avarage RTT value is: 11.5 ms The highest RTT value we registered is: 3 795 ms

To sum up: sometimes we see several spikes in the RTT value. These spikes can reach very high values. We do not have any clue about why this is happening.

My questions are:

Is this normal? Is a behaviour you would excpect or we need to change something in our setup?

Thanks

I only know how to delete the individual accounts kopano-admin -d username

Not sure whether you can just delete the email of a user while leaving the account valid.

@chris said in core-8.7.80 breaks LDAP groups on Debian 9 /w OpenLDAP:

Actually no. […] after every core update I had my ldap.openldap.cfg overwritten in /usr/share/kopano

You are conflicting with yourself.

I’ll repeat: you should only make adaptations to your ldap configuration in /etc/kopano, the default file to use there is /etc/kopano/ldap.cfg. This is also a topic in the Kopano admin manual at https://documentation.kopano.io/kopanocore_administrator_manual/configure_kc_components.html#configure-kopano-for-user-management-with-ldap-e-g-openldap-ads. We have recently rewritten this to streamline the configuration process a bit.

Update to kopano 8.6.8.0 was working.
Was a while away from office. So it needed a while to run the update.
Thanks

Just found in my notitions that net-snmp has the same problem. Needs to uninstall the whole pacckage before building

Oh works like a charm! Thank you very much! :)
This Issue can be closed.

@teka74
Hello Thomas,

would you please publish how you had changed the kopano-cleanup.py to work for all users?

I found the other script which print all users of my kopano but i don‘t know to combine both because i don’t know anything about python.

Regards
Heiko