Re: [Dovecot] Migrating from dovecot 2.1 to 2.2
Am 20.09.2013 18:40, schrieb mego...@inboxalias.com: Hey there micah, assuming you have your Dovecot set up using virtual users, I would advise you to use imapsync for that. It does incremental and recursive IMAP transfers from one mailbox to another (on different servers too). As it doesn't make a file copy, but let the two dovecot servers talk directly to each other via IMAP, all your mails with all flags, dates etc. will be preserved on the destination system exactly like on your source system. In your case also the indexes will be written on the fast system automatically by Dovecot 2.2.5 (if configured to do so), so this might do exactly what you are looking for. I have myself successfully transferred over 35000 accounts with imapsync (with very few problems, almost all of them because of corrupt mailboxes or special character encoding problems occured through former use of weird obsolete mail clients) and can highly recommend it. Best regards and good luck, Megodin Yes, I can confirm imapsync works fine: https://github.com/imapsync/imapsync It doesn't replicate the dovecot IMAP UIDs / POP3 UIDLs though, since via IMAP-only it can't force the target IMAP server to use specific UUIDs. Dovecot's own tool dsync can preserve UUIDs and is therefore the better choice when migrating to dovecot: http://wiki2.dovecot.org/Tools/Dsync http://wiki2.dovecot.org/Migration/Dsync Regards Daniel -- Dipl.-Inf. Daniel Parthey System Engineer Metaways Infosystems GmbH Pickhuben 2, D-20457 Hamburg E-Mail: d.part...@metaways.de Web:http://www.metaways.de Tel:+49 (0)40 317031-537 Fax:+49 (0)40 317031-937 Metaways Infosystems GmbH - Sitz: D-22967 Tremsbüttel Handelsregister: Amtsgericht Lübeck HRB 4508 AH Geschäftsführung: Hermann Thaele, Lüder-H.Thaele
Re: [Dovecot] Migrating from dovecot 2.1 to 2.2
Hey there micah, assuming you have your Dovecot set up using virtual users, I would advise you to use imapsync for that. It does incremental and recursive IMAP transfers from one mailbox to another (on different servers too). As it doesn't make a file copy, but let the two dovecot servers talk directly to each other via IMAP, all your mails with all flags, dates etc. will be preserved on the destination system exactly like on your source system. In your case also the indexes will be written on the fast system automatically by Dovecot 2.2.5 (if configured to do so), so this might do exactly what you are looking for. I have myself successfully transferred over 35000 accounts with imapsync (with very few problems, almost all of them because of corrupt mailboxes or special character encoding problems occured through former use of weird obsolete mail clients) and can highly recommend it. Best regards and good luck, Megodin --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen _ Send and receive anonymous emails to your inbox with InboxAlias. http://www.inboxalias.com
[Dovecot] Migrating from dovecot 2.1 to 2.2
Due to the incompatibilities with the dsync protocol version between 2.1 and 2.2, I am unable to use dsync to move users to a new machine where we have 2.2.5 setup. This wouldn't normally be a problem, as I could just rsync the user's mdbox and dovecot would happily do the right thing. However, on the new system I've placed the indexes into a faster storage medium, where on the older system the indexes were included in their mail directory. I can rsync over the entire thing, including their old indexes, and dovecot will try to do the right thing and build new indexes, but what happens is all mail is marked as unread, and I get some old index cruft left around in the directories. How can I preserve the seen/unseen flags in such a migration? Thanks! micah
Re: [Dovecot] Migrating from dovecot 2.1 to 2.2
On 2013-09-13 12:07 PM, Micah Anderson wrote: Due to the incompatibilities with the dsync protocol version between 2.1 and 2.2, I am unable to use dsync to move users to a new machine where we have 2.2.5 setup. This wouldn't normally be a problem, as I could just rsync the user's mdbox and dovecot would happily do the right thing. However, on the new system I've placed the indexes into a faster storage medium, where on the older system the indexes were included in their mail directory. You could either simply upgrade the 2.1 server to 2.2 (that looks to me to be the simplest/best option), or, I believe I recall reading that you can install 2.2 in a separate location, and use the dsync in 2.2 on the 2.1 server...? -- Best regards, */Charles/*
