Change Details

Just installed guam from Winterfell repo: guam-0.8-5.3.el7.kolab_wf.x86_64 If I setup guam to use frontend servers in Cyrus Murder cluster, folder filter doesn't work - it just lists all the folders no matter what. If I change /etc/guam/sys.config and point guam to use backend server (of course I point to the server where my testing mailbox lives) then guam filters out groupware folders.

Cyrus IMAP Murder frontends are given a command similar to the following: ``` . GETMETADATA (DEPTH infinity) "*" "/shared/*" ``` They will still (hard-coded) use `GETANNOTATION` against backends, yielding untagged responses such as: ``` * ANNOTATION "Calendar" "/vendor/kolab/folder-type" ("value.shared" "event" "shared.size" "5" "value.priv" "event.default" "priv.size" "13") ``` A configuration item in `/etc/imapd.conf` of `suppress_capabilities: METADATA` will prevent client applications from using `GETMETADATA` and `SETMETADATA`, and therefore issue `GETANNOTATION` and `SETANNOTATION` commands, with untagged responses `ANNOTATION`. However, when a client application does issue `GETMETADATA`, the response in a discrete Murder topology will yield untagged `ANNOTATION` responses -- that the client application may not parse. The client application in question here is #guam, which has never been developed against the (now legacy) ANNOTATEMORE RFC draft -- it uses `METADATA`, even if the capability is suppressed. In contrast, suppressing the `METADATA` make #roundcube and #kde_pim use `ANNOTATEMORE` and `ANNOTATEMORE2` (if available). This results in the following options: * Make #guam use `ANNOTATEMORE` rather than `METADATA`, so a discrete Murder topology's frontends can use their (hard-coded) `GETANNOTATION` and `SETANNOTATION`, * Change everything over to `METADATA` and drop `ANNOTATEMORE` altogether. This would include; * Changing #cyrus_imap to use `METADATA` internally, and * Working around the lack of `METADATA` support in Python's imaplib (through cyruslib, shipped as part of #pykolab), updating calls to `getannotation()` and `setannotation()` functions used internally by #pykolab, and * Optionally, dropping support for `ANNOTATEMORE` and `ANNOTATEMORE2` from clients including #roundcube, #roundcube_kolab_plugins and #kde_pim and #kube.

Just installed guam from Winterfell repo:Cyrus IMAP Murder frontends are given a command similar to the following: ``` guam-0.8-5.3.el7.kolab_wf.x86_64. GETMETADATA (DEPTH infinity) "*" "/shared/*" If I setup guam to use frontend servers in Cyrus Murder cluster``` They will still (hard-coded) use `GETANNOTATION` against backends, folder filter doesn't work - it just lists all the folders no matter what.yielding untagged responses such as: ``` If I change /etc/guam/sys.config and point guam to use backend server (of course I point to the server where my testing mailbox lives) then guam filters out groupware folders* ANNOTATION "Calendar" "/vendor/kolab/folder-type" ("value.shared" "event" "shared.size" "5" "value.priv" "event.default" "priv.size" "13") ``` A configuration item in `/etc/imapd.conf` of `suppress_capabilities: METADATA` will prevent client applications from using `GETMETADATA` and `SETMETADATA`, and therefore issue `GETANNOTATION` and `SETANNOTATION` commands, with untagged responses `ANNOTATION`. However, when a client application does issue `GETMETADATA`, the response in a discrete Murder topology will yield untagged `ANNOTATION` responses -- that the client application may not parse. The client application in question here is #guam, which has never been developed against the (now legacy) ANNOTATEMORE RFC draft -- it uses `METADATA`, even if the capability is suppressed. In contrast, suppressing the `METADATA` make #roundcube and #kde_pim use `ANNOTATEMORE` and `ANNOTATEMORE2` (if available). This results in the following options: * Make #guam use `ANNOTATEMORE` rather than `METADATA`, so a discrete Murder topology's frontends can use their (hard-coded) `GETANNOTATION` and `SETANNOTATION`, * Change everything over to `METADATA` and drop `ANNOTATEMORE` altogether. This would include; * Changing #cyrus_imap to use `METADATA` internally, and * Working around the lack of `METADATA` support in Python's imaplib (through cyruslib, shipped as part of #pykolab), updating calls to `getannotation()` and `setannotation()` functions used internally by #pykolab, and * Optionally, dropping support for `ANNOTATEMORE` and `ANNOTATEMORE2` from clients including #roundcube, #roundcube_kolab_plugins and #kde_pim and #kube.