Any updates when this will land?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 18 2023
May 10 2022
Mar 26 2022
Here's the documentation to the current web api parameters for file uploads:
https://download.seafile.com/published/web-api/v2.1/file-upload.md
Sep 2 2021
Sep 1 2021
Jun 7 2020
double diff
Removed double Alias
Apr 29 2020
Apr 15 2020
Apr 14 2020
Apr 7 2020
- always send unsigned int32
- change error-id to the an integer
Apr 6 2020
- one more typo in json protocol
You're right. I've fixed the typo and replaced the msxml errorcode with one that a real exchange server sends outs. Just in case something weird could happing.
- switch to an error code a real ms server sends out on invalid request
Apr 2 2020
Mar 30 2020
Here's an example of a more complex tls_config I use on my servers (using certbot + letsencrypt):
Mar 7 2020
Feb 8 2020
Feb 7 2020
- autodiscover.xml now requires basic authentication
- whitespace fix
- tab/whitespace fix
- reupload after pushing the wrong working copy
- tab/whitespace fix
Feb 2 2020
Start an unauthenticated autodiscover request with a known email address
- whitespace fix
- autodiscover.xml now requires basic authentication
Feb 1 2020
- added missing charset
- updated author name
Jan 27 2020
Jan 17 2020
Closing Ticket. Change has been merged
Sidenote: when the inetDomainBaseDN of the hosted domain changes, kolabd will not detect the domain as primary_domain anymore and therefore stops creating new mailboxes for all hosted domains under hosted_domain_rootdn. It's important that inetDomainBaseDN doesn't get modified by accident.
Fixed whitespace
Jan 8 2020
Dec 23 2019
Hope this is correct from the documentation and examples about ldap paging search
- fix check for page control result
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
Dec 22 2019
This happend on a Debian 10 system with most recent pykolab package
- pykolab 0.8.17-0~kolab2
- python-ldap 3.1.0-2
Dec 6 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
Nov 23 2019
Yes. These values are enforced. If they don't exists, kolabd recreates them.
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.
Nov 21 2019
This diff fixes issue T5671
Nov 19 2019
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. """) )
Nov 16 2019
Uploaded D847
Uploaded D853
Nov 15 2019
See Debian Bug Entry: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921016