Fixed.

SPAM.

This is no longer an issue on Debian 10 with the upgrade of roundcubemail to 1:1.5.4.11-1~kolab1 and roundcubemail-plugins-kolab to 1:3.5.11-0~kolab1. The context menu is back and I am super grateful.

Any further Developments here?

Very old.

Old. Not enough info.

SPAM.

Packaged and released in 1.5.4.11

On PHP >= 7.3 we're not using the cli tool at all now. So, this shouldn't be a problem with recent installations.

SPAM.

It does not make sense to me.

No feedback.

Latest roundcubemail package on Ubuntu 18.04 is 1.5.4.7-1~kolab1_all.deb, which as far as I can see has Net_SMTP in version 1.10.1 built-in. So, all should be ok, but I don't have Ubuntu system to verify on.

Anything different with Cyrus IMAP v3?

@mollekopf, imap.user_mailbox_create() returns False on error.

Duplicate of T6196.

Works for me.

Duplicate of T6688.

Not enough info.

Works for me.

I think it is better to pass the invitation to Inbox for manual processing.

Sharing is not possible with the database driver. The label has been fixed in git.

Sounds to me like a client issue. We would need more info, including debug logs from syncroton.

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.

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.