Thanks for your mail.

Can you elaborate further on what you mean by chain body?

Unfortunately missed this for 0.9.6, so I'll pick it up in the next release.

This has been resolved in packaging as far as I know.

Here's an example of a more complex tls_config I use on my servers (using certbot + letsencrypt):

You need to supply Guam with a valid X.509 certificate (issued by Let's Encrypt, for example) and adapt the tls_config section of /etc/guam/sys.config accordingly.

Guam should be listening on port 993, so please check if the Guam service is up and running.

Worked fine, I could't reproduce the issue. Closing this.

Closing Ticket. Change has been merged

Patch seems to work. I haven't seen this issue after applying the patch. Thanks a lot!

PHP >= 7.1 compat. issue. Fixed.

Closing this task then.

Additionally I get the following traceback:

2019-12-23 14:05:25,670 pykolab.auth ERROR [21425] An error occured using _paged_search: NameError("global name 'LDAP_CONTROL_PAGED_RESULTS' is not defined",)
2019-12-23 14:05:25,670 pykolab.auth ERROR [21425] Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/pykolab/auth/ldap/__init__.py", line 3168, in _search
    secondary_domains
  File "<string>", line 10, in <module>
  File "/usr/lib/python2.7/dist-packages/pykolab/auth/ldap/__init__.py", line 2940, in _paged_search
    if c.controlType == LDAP_CONTROL_PAGED_RESULTS
NameError: global name 'LDAP_CONTROL_PAGED_RESULTS' is not defined

Hi all

This happend on a Debian 10 system with most recent pykolab package

• pykolab 0.8.17-0~kolab2
• python-ldap 3.1.0-2

Hi all

Sorry,
i found the solution myself.

ups, reopen

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

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.

This is a duplicate of T5692 (i found the same bug). Fix is proposed D871

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.

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.

The individual directories in /run/ are secured, so there's little need to secure the files within them.

Uploaded D847

Uploaded D853

See Debian Bug Entry: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921016