Hello, we have a centos 6 server running dovecot 2.0 provided with the OS, currently 2.0.9. We would like to upgrade to the 2.2.19 package provided by the mailserver.guru repo. I read the upgrading docs for 2.1 and 2.2 and found the following issues: 2.0 - 2.1: - define namespace inbox or delete 15-mailboxes.conf (we do not "care about special use mailboxes") - plugins and UTF-8: we do not use one of the listed plugins - to allow mixed usernames set auth_username_format to "nothing" - solr backend: not used in our setup - expire plugin: not used - dsync: not used 2.1 - 2.2 - fts-solr: not used (?) - autocreate: not used - other changes: trivial or not used Are there other things that we need to observe? Is a direct update from 2.0.9 to 2.2.19 feasible with the above precautions or do we need to put in a 2.1 version in between? Thank you for hints, Jakob
On 2017-03-03 13:22, Jakob Curdes wrote:> Hello, we have a centos 6 server running dovecot 2.0 provided with the > OS, currently 2.0.9. We would like to upgrade to the 2.2.19 package > provided by the mailserver.guru repo. I read the upgrading docs for > 2.1 and 2.2 and found the following issues: > > 2.0 - 2.1: > - define namespace inbox or delete 15-mailboxes.conf (we do not "care > about special use mailboxes") > - plugins and UTF-8: we do not use one of the listed plugins > - to allow mixed usernames set auth_username_format to "nothing" > - solr backend: not used in our setup > - expire plugin: not used > - dsync: not used > 2.1 - 2.2 > - fts-solr: not used (?) > - autocreate: not used > - other changes: trivial or not used > > > Are there other things that we need to observe? Is a direct update > from 2.0.9 to 2.2.19 feasible with the above precautions or do we need > to put in a 2.1 version in between? > > Thank you for hints, > JakobI would also consider possibility of upgrading the server too, so you would instead setup a new environment and migrate your users there instead of upgrading the old server. This way you could make sure everything works. Aki
On 04/03/17 00:22, Jakob Curdes wrote:> Hello, we have a centos 6 server running dovecot 2.0 provided with the > OS, currently 2.0.9. We would like to upgrade to the 2.2.19 package > provided by the mailserver.guru repo.Why upgrade to such an old version? You can get 2.2.27 (2.2.28 in testing) packages from GhettoForge plus: http://ghettoforge.org/ Peter
Am 05.03.2017 um 22:49 schrieb Peter:> On 04/03/17 00:22, Jakob Curdes wrote: >> Hello, we have a centos 6 server running dovecot 2.0 provided with the >> OS, currently 2.0.9. We would like to upgrade to the 2.2.19 package >> provided by the mailserver.guru repo. > > Why upgrade to such an old version? You can get 2.2.27 (2.2.28 in > testing) packages from GhettoForge plus: > > http://ghettoforge.org/+1> PeterAlexander
Am 03.03.2017 um 12:45 schrieb Aki Tuomi:> > > On 2017-03-03 13:22, Jakob Curdes wrote: >> Hello, we have a centos 6 server running dovecot 2.0 provided with >> the OS, currently 2.0.9. We would like to upgrade to the 2.2.19 >> package provided by the mailserver.guru repo. I read the upgrading >> docs for 2.1 and 2.2 and found the following issues:(...)>> Are there other things that we need to observe? Is a direct update >> from 2.0.9 to 2.2.19 feasible with the above precautions or do we >> need to put in a 2.1 version in between? >> >> Thank you for hints, >> Jakob > > I would also consider possibility of upgrading the server too, so you > would instead setup a new environment and migrate your users there > instead of upgrading the old server. This way you could make sure > everything works. >Well, then I have a different problem because in this way I upgrade the complete environment to eg. CentOS 7 and will need to test a plethora of other things. I'd rather stick to the current system (which ist not "old", just the dovecot package in CentOS 6 is "old"). Ok so no other problems known? Regards, Jakob