- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Dec 18 2019
Dec 17 2019
Hi all
Dec 16 2019
Sorry,
i found the solution myself.
Dec 13 2019
Dec 10 2019
Dec 9 2019
Dec 6 2019
Dec 5 2019
Dec 4 2019
Dec 3 2019
I've updated my kolab installation from Debian 9 to 10. All in all nothing major. Highlights:
Dec 2 2019
Dec 1 2019
Nov 30 2019
Nov 29 2019
Nov 26 2019
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
Fixed "try {" typo
LGTM after my misreading of things.
LGTM.
LGTM.
Looks good to me.
Nov 25 2019
If you feel courageous enough, I would say it's ready for field testing. Should you encounter any remaining rough edges, please report them so they can be ironed out.
Nov 24 2019
Nov 23 2019
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.