Anything different with Cyrus IMAP v3?

there is also a similar issue with group_base around line 1483
while the multidomain support is non-existent for "ldap_member_base"

This depends on Cyrus configuration. The way how Kolab uses Cyrus IMAP does not allow for subfolders under INBOX.

Correcting the priority from 60/40 to Normal

I can confirm that. In my test it does not find messages even if they use UTF-8/8bit encoding, i.e. no decoding is required. Maybe squatter handles that better, I don't know.

Transferred to https://bifrost.kolabsystems.com/T9049 on Oct 27 2016.

The upstream issue has been fixed.

got new Version here

Of course the correct version including the fix is: cyrus-imap.2.5.10

This ticket is superseded by the new Bifrost#T9079 ticket.

would you like to change the status of this to some other Status than open? As far as I see now a kolab package for 2.5.9 exists right now.

I agree, looks like a cyrus ACL problem.
The first MOVE "<f78gclud>" results in a "COPYUID" but needs to be rejected as the second one "<04c9c116>" is/was.

"the implementation" here is cyrus.

Since I'm not sure if roundcubemail does that already cyrus may not be the source of the umlauts problem.

I think that's something related to Jeroen...

This is an upstream Cyrus IMAP problem more so than a Kolab problem.

Are we likely to see SPECIAL-USE (RFC 6154) working and enabled on Kolab Now, as it is currently not enabled. This would definitely make email client setup easier and there would be no effort required for the non-technically inclined user. I reckon this would add some value to Kolab Now.

Back-ported https://git.cyrus.foundation/rI67bac5df9c1f667d1632b4f7bb57fb00873975aa from master.

I still can't get guam work with Cyrus Murder, although it is not clear if that depends on if guam is talking to Murder or standalone server. Guam configuration is:

So it looks like the '*' wildcard doesn't work in a mixed version murder environment (backend 2.5.6 and frontend 2.5.7) doesn't work. When all cyrus-imapd instances are of the same version - no more segfaults.

In T1062#16492, @vanmeeuwen wrote:

In T1062#16491, @adomaitis wrote:

If I run

. GETMETADATA (DEPTH infinity) "*" (/shared/vendor/kolab/folder-type)

Against 2.5.7:

Protection error: Connection reset by peer

messages log file shows:

kernel: proxyd[17138]: segfault at 7ffffff8 ip 00007f0ef1d5dab4 sp 00007ffca2cf2aa0 error 4 in libc-2.17.so[7f0ef1d15000+1b6000]

I cannot reproduce this, but I'm running this on Santiago, and you are running Maipo.

In T1062#16491, @adomaitis wrote:

I can't confirm the issue with guam still displaying groupware folders from Cyrus Murder is fixed.
Detailed description:
I have murder cluster running with cyrus-imapd-2.5.6-8.1. Frontends and Backends have commented suppress_capabilities: METADATA config option.

I can't confirm the issue with guam still displaying groupware folders from Cyrus Murder is fixed.
Detailed description:
I have murder cluster running with cyrus-imapd-2.5.6-8.1. Frontends and Backends have commented suppress_capabilities: METADATA config option.
I have added yet another frontend cyrus-imapd-2.5.7-8.1 to the cluster (from Winterfel repositories). Guam service is running on port 9143 on this new machine as well.

The fix for this is in https://git.cyrus.foundation/D86

It is the frontend that proxies a GETANNOTATION command to the backend, even though the original command is GETMETADATA.

Accepted during yesterday's meeting.

Code submitted upstream as https://git.cyrus.foundation/D84

Code changes submitted as https://git.cyrus.foundation/D84

Roundcube 1.2 uses the same LIST command. It's possible to disable SPECIAL-USE in Roundcube too.

Set priority to low, because the Thunderbird issue can be worked around by just not advertising SPECIAL-USE support.

We know SPECIAL-USE extensions to LIST commands are not being proxied from frontends (that do not have the SPECIAL-USE folder information) to backends (that do have the SPECIAL-USE folder information).

Attaching to parent ticket.