Re: DECISION: what reconstruct -f should do

2011-04-27 Thread Joost Roeleveld
On Wednesday 27 April 2011 09:49:05 Bron Gondwana wrote: > On Wed, 27 Apr 2011 08:19:10 +0200 > > Joost Roeleveld wrote: > > Would a second flag, for instance "--full-dir-tree" (or similar), to > > change the behaviour to create the directory regardless work? > > It would, but we don't do long f

Re: DECISION: what reconstruct -f should do

2011-04-27 Thread Bron Gondwana
On Wed, 27 Apr 2011 08:19:10 +0200 Joost Roeleveld wrote: > In my experience, most IMAP-mail clients have problems inserting the > "INBOX.sub" folder. In these cases we'd probably need to do this manually > using cyradm. I think at this point it comes down to "what is most likely" - remember th

Re: DECISION: what reconstruct -f should do

2011-04-26 Thread Joost Roeleveld
On Tuesday 26 April 2011 10:19:36 David Lang wrote: > On Tue, 26 Apr 2011, Bron Gondwana wrote: > > 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'

Re: DECISION: what reconstruct -f should do

2011-04-26 Thread Bron Gondwana
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

Re: DECISION: what reconstruct -f should do

2011-04-26 Thread OBATA Akio
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

Re: DECISION: what reconstruct -f should do

2011-04-26 Thread Michael D. Sofka
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 didn't want it, could th

Re: DECISION: what reconstruct -f should do

2011-04-26 Thread David Lang
On Tue, 26 Apr 2011, 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 di

Re: DECISION: what reconstruct -f should do

2011-04-26 Thread Bron Gondwana
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

Re: DECISION: what reconstruct -f should do

2011-04-26 Thread David Lang
On Tue, 26 Apr 2011, Bron Gondwana wrote: > 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

DECISION: what reconstruct -f should do

2011-04-26 Thread Bron Gondwana
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