The message header is parsed!

As the fix sets encoding="utf8", does this mean all messages are utf-8 encoded here?

Packaging fix: https://obs.kolabsys.com/request/show/3324

Proposed fix in D4959.

This file opening problem again caused wallace to crash on my server, resulting in the failure to deliver emails to the end recipient.
Searching though the wallace directory I found the following instances

Same file opening problem exists in /usr/lib/python3.9/site-packages/wallace/module_invitationpolicy.py - line 270 :-

Patch merged.

Seems to be fixed by D3692 and rPbd3a9e74745461089d7afc4e51a39c21958907bf.

Fixed by D3851.

Patch submitted as D4625.

Old. Not enough info.

@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.

I think this got fixed in the python3 migration. Please reopen if you run into this issue again on a python3 system (>= Debian 11)

imap.user_mailbox_create() always returns a string, so this should be fine. Is there a command-line way to reproduce this issue?

D3692 and D3710 should fix this
I ran into same error, when testing for Python 3

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.

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.

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.

Any thoughts about how to fix this issue?

Closing Ticket. Change has been merged

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