Oct 1 2023
Old. Not enough info.
Sep 27 2023
@mollekopf, imap.user_mailbox_create() returns False on error.
I think it is better to pass the invitation to Inbox for manual processing.
This specific issue may be fixed with:
--- a/pykolab/setup/setup_roundcube.py +++ b/pykolab/setup/setup_roundcube.py @@ -26,10 +26,11 @@ import hashlib import os import random import re +import six import subprocess import sys import time -import six +import urllib.parse
It looks to me it's rather CentOS7 issue. And it's old.
Aug 10 2023
I think this got fixed in the python3 migration. Please reopen if you run into this issue again on a python3 system (>= Debian 11)
Mar 12 2023
Mar 7 2023
imap.user_mailbox_create() always returns a string, so this should be fine. Is there a command-line way to reproduce this issue?
Jul 15 2022
D3692 and D3710 should fix this
I ran into same error, when testing for Python 3
Jul 7 2022
Feb 17 2022
Feb 6 2022
Feb 4 2022
The exception comes from inside cache_update(). See attached the traceback, from the log file that Johannes sent me.
Do you happen to have a log containing a backtrace for the case where the sender column is too short? After skimming the code, I would assume SQLAlchemy throws an exception which then gets caught in bin/kolab_smtp_access_policy.py:1717. That's obviously too late.
Feb 3 2022
According to the log, the script tries to create a user named '@'. That's, well, weird. Unfortunately, I'm not sufficiently familiar with the pykolab codebase to make a qualified guess where this username may have originated from.
Jan 15 2022
May 20 2021
Jan 25 2021
Dec 4 2020
Oct 22 2020
Aug 25 2020
I didn't know that wallace created generate calender placeholder. Do they have an update for this? Hoping that they fix it as soon as possible.
Aug 12 2020
Any thoughts about how to fix this issue?
May 3 2020
Apr 1 2020
Jan 17 2020
Closing Ticket. Change has been merged
Jan 9 2020
Patch seems to work. I haven't seen this issue after applying the patch. Thanks a lot!
Dec 23 2019
Additionally I get the following traceback:
2019-12-23 14:05:25,670 pykolab.auth ERROR  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  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 9 2019
Dec 6 2019
Nov 26 2019
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
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
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.