On 10.8.2010, at 18.10, Thomas Hummel wrote:
> On Tue, Aug 10, 2010 at 12:52:48PM +0100, Timo Sirainen wrote:
>
>> The point of namespace list was for clients to be able to figure out
>> what the namespaces there are. With list=yes and hidden=yes for your
>> only namespace you wouldn't be listin
On Tue, Aug 10, 2010 at 12:52:48PM +0100, Timo Sirainen wrote:
> The point of namespace list was for clients to be able to figure out
> what the namespaces there are. With list=yes and hidden=yes for your
> only namespace you wouldn't be listing any namespaces, so clients
> would think you don't h
On 10.8.2010, at 7.56, Thomas Hummel wrote:
>> But then if you have
>>
>> namespace {
>> prefix =
>> list = no
>> }
>>
>> Now both a and b are exactly the same:
>>
>> ab LIST "" *
>
> You mean it won't list anything, even if I have a mailbox (not a namespace)
> named foo ?
Right. That's w
On Mon, Aug 09, 2010 at 10:56:21PM +0100, Timo Sirainen wrote:
> Because listing mailboxes always starts with the namespace that has no
> prefix. If you have only one namespace with prefix="" and list=no, you
> wouldn't
> have any listable mailboxes anywhere.
> For example if you have:
>
> name
On 9.8.2010, at 20.35, Thomas Hummel wrote:
>> Well .. okay, prefix="" namespace is an exception to the above rule. :)
>
> Why has it to be an exception ? Your previous points still stand, don't they
> ? :
>
> . isn't there a risk that the default namespace gets listed twice then ?
>
> . w
On Mon, Aug 09, 2010 at 06:17:06PM +0100, Timo Sirainen wrote:
> On Mon, 2010-08-09 at 19:12 +0200, Thomas Hummel wrote:
> > > > > I've noticed that Thunderbird (3.0.3) seems to wrongly "repeat" the
> > > > > namespace
> > > > > prefix when selecting the top level maildir of a namesapce.
> > > > >
On Mon, 2010-08-09 at 19:12 +0200, Thomas Hummel wrote:
> > > > I've noticed that Thunderbird (3.0.3) seems to wrongly "repeat" the
> > > > namespace
> > > > prefix when selecting the top level maildir of a namesapce.
> > > >
> > > > hidden = no
> > > > list = yes
> > >
> > > This combinatio
On Wed, Jun 09, 2010 at 06:58:40PM +0200, Thomas Hummel wrote:
> On Tue, May 25, 2010 at 07:04:13PM +0100, Timo Sirainen wrote:
> > On Thu, 2010-04-22 at 15:31 +0200, Thomas Hummel wrote:
> >
> > > I've noticed that Thunderbird (3.0.3) seems to wrongly "repeat" the
> > > namespace
> > > prefix wh
On Fri, Jun 11, 2010 at 05:26:30PM +0100, Timo Sirainen wrote:
> > Correct ?
>
> Yes.
Thanks a lot Timo !
--
Thomas Hummel | Institut Pasteur
| Pôle informatique - systèmes et réseau
On pe, 2010-06-11 at 17:45 +0200, Thomas Hummel wrote:
> On Fri, Jun 11, 2010 at 04:29:07PM +0100, Timo Sirainen wrote:
>
> > Yes. (But with hidden=yes it's not a client-visible namespace so it's
> > ok.)
>
> So, if I do the combinatorics :
>
> a) hidden = no
> list = no
>
> -> the "bes
On Fri, Jun 11, 2010 at 04:29:07PM +0100, Timo Sirainen wrote:
> Yes. (But with hidden=yes it's not a client-visible namespace so it's
> ok.)
So, if I do the combinatorics :
a) hidden = no
list = no
-> the "best" or "cleaner" way to define namespace since it rewards
clients which s
On pe, 2010-06-11 at 17:07 +0200, Thomas Hummel wrote:
> On Fri, Jun 11, 2010 at 04:01:27PM +0100, Timo Sirainen wrote:
>
> > Crossing namespace boundaries means a single LIST command listing
> > mailboxes from more than one namespace.
>
> Ok, so basically, "list=yes" means "when you list my pare
On Fri, Jun 11, 2010 at 04:01:27PM +0100, Timo Sirainen wrote:
> Crossing namespace boundaries means a single LIST command listing
> mailboxes from more than one namespace.
Ok, so basically, "list=yes" means "when you list my parent namespace
content, list my content too". And since all namespace
On pe, 2010-06-11 at 16:52 +0200, Thomas Hummel wrote:
> On Fri, Jun 11, 2010 at 03:41:29PM +0100, Timo Sirainen wrote:
>
> > No. The list=yes means if the parent namespace should include this
> > namespace's mailboxes in its LIST reply, i.e. break namespace
> > boundaries.
>
> Not sure we're tal
On Fri, Jun 11, 2010 at 03:41:29PM +0100, Timo Sirainen wrote:
> No. The list=yes means if the parent namespace should include this
> namespace's mailboxes in its LIST reply, i.e. break namespace
> boundaries.
Not sure we're talking about the same thing.
Let's say I have :
x namespace
* NAME
On pe, 2010-06-11 at 16:38 +0200, Thomas Hummel wrote:
> I thought that hidden=no would provide no means for the client to
> know about the namespace
Right.
> and that list=yes would allow to list mailboxes
> in the namespace only if we somehow know the name of the namespace and
> specify it in
On Fri, Jun 11, 2010 at 03:13:11PM +0100, Timo Sirainen wrote:
> Yes. hidden=no, list=yes configuration breaks the "list doesn't cross
> namespace boundaries". That's why I said it's arguably wrong to use such
> configuration.
I do understand why we don't want to break namespaces boudaries. But I
On pe, 2010-06-11 at 15:56 +0200, Thomas Hummel wrote:
> The thread you pointed insisted on the fact that the list "" * command
> should not cross namespaces boudaries.
Right.
> So how can a client list
> mailboxes of a namespace if it doesn't discover the namespace name first
> ?
It couldn't.
> Original Message
>From: Timo Sirainen
>To: "Thomas Hummel"
>Cc: "Dovecot Mailing List"
>Sent: Fri, Jun 11, 2010, 21:49 PM
>Subject: Re: [Dovecot] Thunderbird namespace handling
>
>On to, 2010-06-10 at 18:18 +0200, Thomas Hummel wrote
On Fri, Jun 11, 2010 at 02:48:57PM +0100, Timo Sirainen wrote:
> On to, 2010-06-10 at 18:18 +0200, Thomas Hummel wrote:
> > > See this thread:
> > > http://mailman2.u.washington.edu/pipermail/imap-protocol/2010-May/001076.html
> > >
> >
> > I've read it but I still don't get the point :
> >
> >
On to, 2010-06-10 at 18:18 +0200, Thomas Hummel wrote:
> > See this thread:
> > http://mailman2.u.washington.edu/pipermail/imap-protocol/2010-May/001076.html
> >
>
> I've read it but I still don't get the point :
>
> I thought "hidden = no" would advertise this namespace for clients
> which sup
On Wed, Jun 09, 2010 at 06:17:49PM +0100, Timo Sirainen wrote:
> On ke, 2010-06-09 at 18:58 +0200, Thomas Hummel wrote:
> > On Tue, May 25, 2010 at 07:04:13PM +0100, Timo Sirainen wrote:
> > > On Thu, 2010-04-22 at 15:31 +0200, Thomas Hummel wrote:
> > >
> > > > I've noticed that Thunderbird (3.0.
On ke, 2010-06-09 at 18:58 +0200, Thomas Hummel wrote:
> On Tue, May 25, 2010 at 07:04:13PM +0100, Timo Sirainen wrote:
> > On Thu, 2010-04-22 at 15:31 +0200, Thomas Hummel wrote:
> >
> > > I've noticed that Thunderbird (3.0.3) seems to wrongly "repeat" the
> > > namespace
> > > prefix when selec
On Tue, May 25, 2010 at 07:04:13PM +0100, Timo Sirainen wrote:
> On Thu, 2010-04-22 at 15:31 +0200, Thomas Hummel wrote:
>
> > I've noticed that Thunderbird (3.0.3) seems to wrongly "repeat" the
> > namespace
> > prefix when selecting the top level maildir of a namesapce.
> >
> > hidden = no
>
On Thu, 2010-04-22 at 15:31 +0200, Thomas Hummel wrote:
> I've noticed that Thunderbird (3.0.3) seems to wrongly "repeat" the namespace
> prefix when selecting the top level maildir of a namesapce.
>
> hidden = no
> list = yes
This combination is arguably a wrong way to define namespaces.
>
Hello,
I've noticed that Thunderbird (3.0.3) seems to wrongly "repeat" the namespace
prefix when selecting the top level maildir of a namesapce.
It doesn't occur if "list=yes" and TB has no clue about the namespace prefix.
But it seems to happen only when TB is aware of the namespace prefix, eith
26 matches
Mail list logo
