I am running Dovecot 1.2.16 and considering moving up to 2.0.8. I have found <http://wiki2.dovecot.org/Upgrading/2.0> but there's not a lot about deploying a 2.0 server alongside an existing 1.2. Any hints on a seamless approach to this, especially one that might allow me to upgrade individual users in place, without moving their maildirs into a new tree and still avoid issues with 1.2/2.0 sharing access?
* Tom Talpey <tmtalpey at gmail.com>:> I am running Dovecot 1.2.16 and considering moving up to 2.0.8. > I have found <http://wiki2.dovecot.org/Upgrading/2.0> but there's > not a lot about deploying a 2.0 server alongside an existing 1.2. > Any hints on a seamless approach to this, especially one that might > allow me to upgrade individual users in place, without moving their > maildirs into a new tree and still avoid issues with 1.2/2.0 sharing > access?I'm switching back and forth between 1.2 and 2.0. No need to worry. -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt at charite.de | http://www.charite.de
On 5.12.2010, at 16.40, Tom Talpey wrote:> I am running Dovecot 1.2.16 and considering moving up to 2.0.8. > I have found <http://wiki2.dovecot.org/Upgrading/2.0> but there's > not a lot about deploying a 2.0 server alongside an existing 1.2. > Any hints on a seamless approach to this, especially one that might > allow me to upgrade individual users in place, without moving their > maildirs into a new tree and still avoid issues with 1.2/2.0 sharing > access?Added to wiki: Once running v2.0, it's safe to downgrade to v1.2.5 or newer. Older versions don't understand some of the changes to index files and will log errors. It's also safe to run v1.2 and v2.0 in parallel, even accessing the same index files.