Re: Upgrade from 2.0. to 2.2

2017-03-06 Thread Jakob Curdes
Ah, still better. I just want to upgrade to a package that is available from maintained repos, so that is good news for me. Thx, Jakob (The last message was crippled somewhere - in my sent folder it looks ok but on the list only our logo appeared...) Am 05.03.2017 um 22:52 schrieb Alexande

Re: Upgrade from 2.0. to 2.2

2017-03-06 Thread Jakob Curdes
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

Re: Upgrade from 2.0. to 2.2

2017-03-06 Thread Jakob Curdes
Ah, still better. I just want to upgrade to a package that is available from maintained repos, so that is good news for me. Thx, Jakob Am 05.03.2017 um 22:52 schrieb Alexander Dalloz: Am 05.03.2017 um 22:49 schrieb Peter: On 04/03/17 00:22, Jakob Curdes wrote: Hello, we have a centos 6 serv

Re: Upgrade from 2.0. to 2.2

2017-03-05 Thread Alexander Dalloz
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

Re: Upgrade from 2.0. to 2.2

2017-03-05 Thread 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)

Re: Upgrade from 2.0. to 2.2

2017-03-03 Thread 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: