[Dovecot] Eliminate legacy INBOX namespace - how?
genie at geniechka.ru
Sat Dec 21 20:10:26 EET 2013
It has been a while since I migrated from Courier to Dovecot, but I don't
remember any special problems. They both were using $HOME/Maildir for
storage so I did not even had to move anything, just remove that INBOX root
prefix from the client config and refresh the folder list.
From: Charles Marcus
Sent: Saturday, December 21, 2013 9:12 PM
To: dovecot at dovecot.org
Subject: Re: [Dovecot] Eliminate legacy INBOX namespace - how?
On 2013-12-21 10:58 AM, Timo Sirainen <tss at iki.fi> wrote:
> On 21.12.2013, at 17.49, Charles Marcus <CMarcus at Media-Brokers.com> wrote:
>> Our mailstore was converted from a Courier-IMAP system last year, but I
>> am planning a migration to a shiny new VM, and would really like to clean
>> things up and do away with the legacy INBOX namespace.
>> My goal is to simplify IMAP client setup - no special 'INBOX' namespace
>> needed, they just enter the server info and credentials.
>> Also important because I will be rolling out SOGo, which has a nice web
>> interface, and I want the mailstore to be as close to default dovecot
>> settings as possible - although I do plan on converting from maildir to
>> mdbox when I do the conversion
>> I also don't want other folders to show up as subfolders of the Inbox in
>> IMAP clients, they should all show up on the same level as the Inbox.
>> I've read http://wiki2.dovecot.org/Migration/Courier, but I don't see
>> anything about how to eliminate this stupid legacy INBOX. namespace, so
>> that new IMAP clients won't show all folders as subfolders of the INBOX
>> unless/until they add the INBOX namespace prefix in the advanced
>> I've also been reading http://wiki2.dovecot.org/Namespaces, but I'm still
>> confused as to how to go about this.
> I don't think it can be done easily with just a single config. Whatever
> you do to new users might break existing setups. So the only good way I
> think would be to use two different IPs. One for the new setups, one for
> the old. For example imap.domain.com -> mail.domain.com or vice versa.
Actually, that's a good idea... thanks! :)
Then I guess I proxy the old users to the old server until I get them
all converted? Now I'm off to read about how to implement that...
More information about the dovecot