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? If I change the name space won't it fail to find the local folders in their mailbox? Cheers, Mark On 2016-01-30 19:05, Timo Sirainen wrote:>> On 29 Jan 2016, at 23:16, Mark Little <marklittle at 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
> On 01 Feb 2016, at 23:39, Mark Little <marklittle at 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 at 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
On 2016-02-02 07:22, Timo Sirainen wrote:>> On 01 Feb 2016, at 23:39, Mark Little <marklittle at 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.. >Ok great. I will try that out. So you are saying I could run the daemon on a source server specifying to use a different config with the namespace matching the other, and then when dsync connects it will see the namespaces as the same?>> 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). >Ok. I am just realizing that I am probably unable to have a transparent migration for IMAP, right? Seeing as my destination is using a different Prefix, that means some IMAP clients will not see their migrated folders by default unless they update their configuration. I am mainly concerned about POP3 I guess, because if IMAP has to re-download it's not as big of a deal because everything is already marked as read.. but re-downloading POP3 doesn't work the same. I tried following the dsync page but I cannot get it working. Do I just have to include the POP3 configuration examples, or the IMAP too? Do I need to use 'pop3c:' at the end of the line instead of imapc: (eg: 'doveadm -R -u user at domain pop3c:') to signify it needs to preserve the UIDL's? Do I need to add the same settings to the source as well as destination? or just one side? I tried yesterday but then ended up breaking Dovecot on my destination server. After I added the pop3-migration namespace part to the namespace section, all users were failing with: 'Error: User initialization failed: namespace configuration error: list=yes namespace missing' Sorry for all the questions but the I am unable to work it out from the documentation documentation. If you know of some examples or some additional documentation it would be very appreciated. Thanks, Mark>> On 2016-01-30 19:05, Timo Sirainen wrote: >>>> On 29 Jan 2016, at 23:16, Mark Little <marklittle at 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