Mon, Dec 9
Fri, Dec 6
Wed, Dec 4
Tue, Nov 26
A workaround could be to move the hosted_root_dn from the [kolab_web] to [kolab] section and make a check for it. If hosted_mode is configured then look for ou=domain,$hosted_root_dn instead of the dc version. Another workaround would be to load all hosted domains into memory to avoid ldap query for every sync run. But we then need to trigger kolabd somehow to reload the domain list when domains have been changed or added
Sat, Nov 23
Yes. These values are enforced. If they don't exists, kolabd recreates them.
I get that you can disable it. But when the records have been created anyway, should they not be removable?
Okay ... first issue (in my case) is that mgmt_root_dn is in the same domain name space ... One issue, but that's not the root cause
You need to disable the autogenerated secondary_mails in /etc/kolab/kolab.conf.
Yepp. the chmod mask was held against the umask and therefore resulted in the wrong chmod mask. After changing this to a correct umask octcal number it's okay.
Fri, Nov 22
does this issue apply to the enterprise version of Kolab 16 as well? We're currently evaluating Kolab (opensource version) to see if it fits our needs, but incomplete ActiveSync would be somewhat of an issue for us.
Mon, Nov 18
The individual directories in /run/ are secured, so there's little need to secure the files within them.
Sat, Nov 16
Fri, Nov 15
See Debian Bug Entry: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921016