On Sat, 2008-05-24 at 13:33 -0700, Troy Engel wrote: > Timo Sirainen wrote: > > > > But I don't think there are any problems if you make INBOX. namespace > > the hidden one. Most clients don't care about namespaces. > > Hi Timo, thanks for the reply - I understand what you're saying. Can you > theorize what will happen to the already configured/subscribed users > (Thunderbird) whose tree looks like: > > INBOX > |_ Sent > |_ Drafts > > ...when I would change the default namespace around and make the empty > prefix inbox=yes?
The INBOX should point to the same location with both namespaces, so it doesn't matter which one has inbox=yes. > Would everything suddenly become "flat" on them and > cause confusion? Ala: > > INBOX > Sent > Drafts Isn't this how it already is if the INBOX. prefix is set? I thought mailboxes are shown under INBOX only if there was no prefix. > Would it be correct to assume that all these existing users would be > fine (because of the hidden INBOX prefix namespace, compatibility mode), > and only new users would see a flat hierarchy when setting up Thunderbird? I'm not really an TB expert..
signature.asc
Description: This is a digitally signed message part
