On 12/16/2010 09:33 AM, A.L.E.C wrote:
On 16.12.2010 15:18, Julien Vehent wrote:
I'll ask them. I'm currently reading the RFC of the NAMESPACE extension.
However, how do you explain that Thunderbird can access the shared mailbox just fine (read, write, delete, ...) ?
It is a problem in Roundcube, agreed. We have a few possibilities of fixing this on Roundcube side:
- We could detect such situation and handle folder names correctly.
E.g. when parsing LIST/LSUB response we should check folder prefix if doesn't exists add it to shared namespace (internal) definition. This will not work if personal namespace doesn't use prefix.
- We could make imap_ns_* options (if defined) to overwrite namespace
response from server.
- We could change folder names handling, so personal namespace prefix
will be not removed (could be removed for display only). More work. Probably not backward compatible change.
None will be needed when you fix namespace response.
You can open a ticket in trac pointing to this thread.
I started the discussion on the cyrus mailing list: http://lists.andrew.cmu.edu/pipermail/info-cyrus/2010-December/034249.html
I suppose your second option (overwrite namespace response) would be preferable. Sysadmin are used to configuration options that force a specific behavior, it's less confusing.
I don't know yet if it's roundcube, cyrus or me that is responsible for this problem. I will investigate and file a ticket if necessary. However, if you had a quick patch to overwrite namespace response (or indicate me where to do the change), I'd appreciate.
Thanks, Julien
List info: http://lists.roundcube.net/users/ BT/9b404e9e