On 2013-05-02 07:29, Bron Gondwana wrote:
One of my release goals for Cyrus 2.5 is to be correct in our
implementation of every standard that we claim to support.
This is why I emailed the list last week asking if anyone is using the
intermediate SPECIALUSE representation in git. Since there
On Sun, May 19, 2013, at 08:36 PM, Jeroen van Meeuwen (Kolab Systems) wrote:
On 2013-05-02 07:29, Bron Gondwana wrote:
One of my release goals for Cyrus 2.5 is to be correct in our
implementation of every standard that we claim to support.
This is why I emailed the list last week asking
On Sun, May 19, 2013, at 11:21 PM, Jeroen van Meeuwen (Kolab Systems) wrote:
On 2013-05-19 15:07, Bron Gondwana wrote:
On Sun, May 19, 2013, at 08:36 PM, Jeroen van Meeuwen (Kolab Systems)
wrote:
Should you make the change to allow sub-folders (of the INBOX) to in
fact be created (while
On 2013-05-19 21:45, Bron Gondwana wrote:
On Sun, May 19, 2013, at 11:21 PM, Jeroen van Meeuwen (Kolab Systems)
wrote:
On 2013-05-19 15:07, Bron Gondwana wrote:
On Sun, May 19, 2013, at 08:36 PM, Jeroen van Meeuwen (Kolab Systems)
wrote:
Should you make the change to allow sub-folders (of
Alt External Non-Alt External Internal
Inbox INBOX user.foo
Inbox.sub INBOX.Inbox.subuser.foo.Inbox.sub
INBOX.sub INBOX.INBOX.subuser.foo.INBOX.sub
illegal INBOX.INBOXuser.foo.INBOX
illegal
On Thu, May 2, 2013, at 04:05 PM, Robert Mueller wrote:
A couple of things:
1. Should we block creation of INBOX.sub in the alt namespace mode? In
theory, only the top level [Ii][Nn][Bb][Oo][Xx] is special, but it
*might* confuse some clients that INBOX.sub and Inbox.sub are different
One of my release goals for Cyrus 2.5 is to be correct in our
implementation of every standard that we claim to support.
This is why I emailed the list last week asking if anyone is using the
intermediate SPECIALUSE representation in git. Since there was no
reply, I'm assuming it will be OK :)
