dovecot - Aug 2007 - Enabling IMAP namespaces for existing folders

Hi.

We're using dovecot 1.0.3 with a very very simple setup; specifically, 
there are no namespaces defined.  Users have been puttering away happily 
for many months, creating subfolders and whatnot with (almost) zero 
problems.

We'd like to start taking advantage of shared IMAP folders.  I've been 
reading over the dovecot wiki and have only one question that I don't 
see documented.  The docs point out that if we define any namespaces, we 
must also explicitly define the private previously-default one.  My 
question is:  are there any migration or transition steps that must be 
taken there?  Will clients' configuration need to be modified in any way 
when, e.g., their existing IMAP folders suddenly become part of a 
private namespace?

Thanks for the newbie help.


-- 
Phil Edwards

On Tue, 2007-08-21 at 16:24 -0400, Phil Edwards wrote:
> We'd like to start taking advantage of shared IMAP folders.  I've
> been 
> reading over the dovecot wiki and have only one question that I don't 
> see documented.  The docs point out that if we define any namespaces, we 
> must also explicitly define the private previously-default one.  My 
> question is:  are there any migration or transition steps that must be 
> taken there?  Will clients' configuration need to be modified in any
way
> when, e.g., their existing IMAP folders suddenly become part of a 
> private namespace?
Even though you didn't explicitly create a namespace, Dovecot internally
created it for you. So as long as you create an identical namespace your
clients don't see any difference. The identical namespace can be created
easily:

namespace private {
}

(or at least I'm pretty sure it fills out the defaults by itself)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20070824/3c258436/attachment-0002.bin>