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.