It looks to me it's rather CentOS7 issue. And it's old.

Old.

Not enough info. Guam works for me.

This is old.

Patch merged.

This can be found in preinst and postinst scripts and should be copied to prerm script.

reload_apache()
{
    if apache2ctl configtest 2>/dev/null; then
        invoke-rc.d apache2 $1 || true
    else
        echo "Your apache2 configuration is broken, so we're not restarting it for you."
    fi
}

@conathan I hesitate to merge this patch. Without it it works for me with Cyrus v3 DAV service as well as with standard Kolab DAV service (e.g. at kolabnow.com).

The sound is played if the event has an alarm of type "AUDIO" set. So, you can disable this per event, but I suppose a global option might make sense.

I recompiled and installed libkolabxml1v5 1.2.1-0~kolab3 but apache crashes now :

@nagifep aye, I did that to our own local servers (at the time I opened the ticket), working fine so far with the change. Apologies for not providing a update earlier.

The sending error might be related to T7133

Debian OS version doesn't matter.

I did apply the workaround patch and it did resolve the problem for my test case,
but i have not tested any other 8BITMIME Mails with non-UTF-8 charsets e.g. "ISO-8859-15" or "UTF-16"

Thanks for the patch @rledisez !

The referenced ticket T7247 discusses a Kolab installation on Debian 11 (and the various issues that arise).

You should only install the roundcubemail >= 1.5 package, which includes the contents of the roundcubemail-plugins-kolab package, so this is expected. I suppose something in the debian upgrade path doesn't quite work as expected.

Looks like a duplication.

Duplicated see T7247

Confirmed. The following patch seems to help even though I don't see BODY=8BITMIME to be used. So, it might be an incomplete solution.

--- a/wallace/modules.py
+++ b/wallace/modules.py
@@ -153,6 +153,10 @@ def _sendmail(sender, recipients, msg):
     if conf.debuglevel > 8:
         smtp.set_debuglevel(1)

a little feedback from my side. While using https://mirror.apheleia-it.ch/repos/Kolab:/16:/Testing/Ubuntu_22.04 as source, I was able to install the kolab-packages. So the dependencies are solved. Only one strange thing comes up: the 389-ds package depends on cockpit-389-ds and therefore enforces cockpit to be installed... but this seems to comes from upstream

I tested against a cyrus imap service we had, and it was showing no calendars. (Working with radicale, failing on Cyrus)

Tested this out against radicale, and now working as expected without the patch I mentioned in the ticket.

quoted-printable encoded utf-8 mails are delivered without a problem

It seems that the issue you're encountering is related to the 'ctag' column in the 'kolab_folders' table when trying to connect to Radicale. The error message indicates that the data you're trying to store is too long for the column, which is currently set to accommodate only 40 bytes.

Old. Not enough details.

Discovery bug fixed in 84ef4ac9e3c2. The other issue fixed in b7dc093954bdb6.

Fixed in git-master.

I just double-checked: the fix is published, but apparently the package version didn't get bumped.

sadly, the iRony Debian 10 package ist still not published:(

Looks like we can close this one. Thanks @mroland for the analysis and patch!

That is not an option I am afraid, as apt will then propose to downgrade roundcubemail and remove chwala, irony, etc.
This is actually what I meant with the ticket... there is a new package called 'roundcubemail-plugins-kolab' that seems to supersede all individual previous plugins.

you could try direct with apt install
it is in repository!
https://obs.kolabsys.com/repositories/Kolab:/16/Debian_10.0/all/roundcubemail-plugin-contextmenu_3.0-0~kolab13_all.deb

My Linux distribution is Debian 10, the roundcubemail-plugin-contextmenu package is no longer available for installation using apt, after you upgraded roundcube from 1:1.4.13-0~kolab3 to 1:1.5.3-1~kolab3 (before it was available and it was actually automatically installed during the kolab installation).

Distribution?
Manually tried to install the package? (apt yum dnf...)
It's definetly not a bug, it's a feature request (plugin).
It shouldn't be installed automatically, but mentioned as recommended.