On Wed, Apr 27, 2011 at 10:31:40AM +0900, OBATA Akio wrote:
> On Wed, 27 Apr 2011 02:20:51 +0900, Bron Gondwana wrote:
>
> >On Tue, 26 Apr 2011 10:19 -0700, "David Lang"
> > wrote:
> >>I can easily see someone wanting to have INBOX.sub containing
> >>INBOX.sub.folder1
> >>and INBOX.sub.folder2
On Wed, 27 Apr 2011 02:20:51 +0900, Bron Gondwana wrote:
On Tue, 26 Apr 2011 10:19 -0700, "David Lang"
wrote:
I can easily see someone wanting to have INBOX.sub containing INBOX.sub.folder1
and INBOX.sub.folder2 as an organizational mechanism
if you were to create INBOX.sub and the user did
On Tue, 26 Apr 2011 10:19 -0700, "David Lang"
wrote:
> I can easily see someone wanting to have INBOX.sub containing
> INBOX.sub.folder1
> and INBOX.sub.folder2 as an organizational mechanism
>
> if you were to create INBOX.sub and the user didn't want it, could they
> remove
> it without af
On Sat, Apr 23, 2011 at 01:07:00AM +0200, Bron Gondwana wrote:
> 3) add the mailbox if there's a directory, don't require
>cyrus.header.
>
> 4) like (3) - but check that there's at least one cyrus.* file
>OR at least one message file in the directory before
>creating the mailbox. (so
On 2011-04-23 at 10:34, Jeroen van Meeuwen (Kolab Systems) wrote:
> Bron Gondwana wrote:
> > 3) add the mailbox if there's a directory, don't require
> >cyrus.header.
> >
>
> This one has my preference.
Mine as well.
--
Øyvind Kolbu
Postmaster
Universitetet i Oslo
pgpKldR2FjrNv.pgp
Descr