- Queries
- All Stories
- Search
- Advanced Search
All Stories
Fri, Dec 6
Thu, Dec 5
Wed, Dec 4
Tue, Dec 3
I've updated my kolab installation from Debian 9 to 10. All in all nothing major. Highlights:
Mon, Dec 2
Sun, Dec 1
Sat, Nov 30
Fri, Nov 29
Tue, Nov 26
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.
Mon, Nov 25
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.
Sun, Nov 24
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.
I've seen in OBS that we now build packages for Debian 10.
What's your opinion: Is it probably ready to upgrade my instance?
The only package failing to build is chwala - where I could possiby use the old package...
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.
Thu, Nov 21
This diff fixes issue T5671
Tue, Nov 19
This is especially useful for fully automated setup runs like
setup-kolab \ [...] --mysqlserver=existing \ --mysqlrootpw=unix_socket [...]
--- setup_mysql.py.bak 2019-11-19 00:37:07.398064712 +0100 +++ setup_mysql.py 2019-11-19 00:46:13.000342080 +0100 @@ -143,6 +143,9 @@ _(""" Please supply the root password for MySQL, so we can set up user accounts for other components that use MySQL. + + Use password 'unix_socket' if you're using MariaDBs + unix_socket authentication plugin. """) )
Mon, Nov 18
The individual directories in /run/ are secured, so there's little need to secure the files within them.
Sat, Nov 16
Uploaded D847