On 01 Feb 2016, at 23:39, Mark Little <marklittle@koallo.com> wrote:
Hi Timo,
Thank you very much for the information. I had seen the DSync page but I was confused as to how to configure it. I'd definitely love to be able to get the proper dsync migration working as I have some clients who use POP3 and others who use IMAP and I want to make this seamless for all if possible.
Could you please elaborate on how I specify the alternate dovecot.conf? I've gone through the man pages and I don't see anything referencing -c for doveadm? Or do you mean that I should be running the full dovecot server process from the source server with an alternate configuration?
-c is a global option for all dovecot binaries, including doveadm. I guess all the global options should be included in all the man pages..
If I change the name space won't it fail to find the local folders in their mailbox?
I'm not sure what you mean here. It's possible to switch between namespaces on the fly without losing anything (besides clients seeing them differently).
Cheers, Mark
On 2016-01-30 19:05, Timo Sirainen wrote:
On 29 Jan 2016, at 23:16, Mark Little <marklittle@koallo.com> wrote: Hi everyone, I'm hoping I am just missing something obvious - but I cannot seem to get a one-way migration dsync working between two Dovecot servers because the Prefix configuration is different. I think a regular dsync -> dsync migration won't work then directly, because it assumes similar source and destination namespaces. One possibility would be that if you start dsync from the destination server, you simply point it to a configuration with a similar namespace config (via -c dovecot.conf) as the source. It should still write everything correctly so that afterwards you can run with the wanted the namespace prefix (i.e. prefix can be changed in dovecot.conf without having to modify any per-user files). Another possibility would be to do imapc sync and set imapc_prefix=INBOX. - see http://wiki2.dovecot.org/Migration/Dsync