dovecot - Feb 2014 - Upgrading from 1.2.x -> 2.2.x in one step possible

Hi,

after some off-ML discussions to and some reconsiderations, we might do
the "big jump" from our current 1.2.17 to the atrpms 2.2.

From googling and reading the dovecot upgrade wiki I don't see any (big)
pitfalls.

Basically we use the default config options, mbox, pop3s/imaps on RH EL 5.

So "just" run the upgrade-config script, fingers crossed and thats it?

Ii it possible to do such a big step form 1.2 to 2.2?

	Thanks for comments and suggestions . G?tz

-- 
G?tz Reinicke
IT-Koordinator

Tel. +49 7141 969 82 420
E-Mail goetz.reinicke at filmakademie.de

Filmakademie Baden-W?rttemberg GmbH
Akademiehof 10
71638 Ludwigsburg
www.filmakademie.de

Eintragung Amtsgericht Stuttgart HRB 205016

Vorsitzender des Aufsichtsrats: J?rgen Walter MdL
Staatssekret?r im Ministerium f?r Wissenschaft,
Forschung und Kunst Baden-W?rttemberg

Gesch?ftsf?hrer: Prof. Thomas Schadt

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5223 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20140226/a1e7cae7/attachment.p7s>

Hello G?tz,

Am 26.02.2014 08:50, schrieb G?tz Reinicke - IT
Koordinator:
> after some off-ML discussions to and some reconsiderations, we might do
> the "big jump" from our current 1.2.17 to the atrpms 2.2.
>
> From googling and reading the dovecot upgrade wiki I don't see any
(big)
> pitfalls.
>
> Basically we use the default config options, mbox, pop3s/imaps on RH EL 5.
>
> So "just" run the upgrade-config script, fingers crossed and
thats it?
>
> Is it possible to do such a big step form 1.2 to 2.2?
You should at least have read these wiki articles:

http://wiki2.dovecot.org/Upgrading/2.0
http://wiki2.dovecot.org/Upgrading/2.1
http://wiki2.dovecot.org/Upgrading/2.2

According to http://wiki2.dovecot.org/Upgrading/2.2
Downgrading can be done fully safely to v2.1.16, not to versions before,
because of attribute and cache file changes.

So it is probably better to do the upgrade step-by-step, from stable
to stable version, or have a good backup.

Regards
Daniel

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 26 Feb 2014, Götz Reinicke - IT Koordinator wrote:
> after some off-ML discussions to and some reconsiderations, we might do
> the "big jump" from our current 1.2.17 to the atrpms 2.2.
>
> From googling and reading the dovecot upgrade wiki I don't see any
(big)
> pitfalls.
>
> Basically we use the default config options, mbox, pop3s/imaps on RH EL 5.
>
> So "just" run the upgrade-config script, fingers crossed and
thats it?
>
> Ii it possible to do such a big step form 1.2 to 2.2?
Yes, but you should verify the generated config and make some tests. IMHO, 
you should create the config from scratch with help from the upgraded one. 
Esp. because "Basically we use the default config options" should not
pose
too much effort. Do you know, still, what you've changed in the v1.2 
config? Then re-do those changes in v2.2 and verify each step, that the 
particular setting is unchanged.

Expect some mailbox errors the first time, telling you that some files are 
broken and needed to re-create.

- -- 
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEVAwUBUw20yHD1/YhP6VMHAQIU9QgAgtUAgyOrQvohYj2bmUJNtuVX45kA5GR5
a8+8+WS1cV+UT4ihhlDFAWsAYzYvPL7X6qrcbhVt76myzfesOHxYPC2LfxmBkMVg
BJBxb3mRe+XNHZQPzrdxwAY2gvjvCr3q/X9ez35wKMFgAUnuVja8m2NOZgs8sWce
ZuaETllU9QcGt5rfP+m/5YEZPSFA4jrLt8BCqa7Q0pJTZBlwUMXRm782Psfh0+84
34dxz2FhiA3cJlbRFQYKEI1kkMGcRtm9Lu3UBUrGu9mMyTVxLx9hJkr9M40aHFdh
V+3WRGYZm5evLEtMnBxeH9XxOFEu7Bo5xiJaC9C5TX5LWITuAlJfXg==R3m6
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 26 Feb 2014, G?tz Reinicke - IT Koordinator wrote:
> after some off-ML discussions to and some reconsiderations, we might do
> the "big jump" from our current 1.2.17 to the atrpms 2.2.
>
> From googling and reading the dovecot upgrade wiki I don't see any
(big)
> pitfalls.
>
> Basically we use the default config options, mbox, pop3s/imaps on RH EL 5.
>
> So "just" run the upgrade-config script, fingers crossed and
thats it?
>
> Ii it possible to do such a big step form 1.2 to 2.2?
Yes, but you should verify the generated config and make some tests. IMHO, 
you should create the config from scratch with help from the upgraded one. 
Esp. because "Basically we use the default config options" should not
pose
too much effort. Do you know, still, what you've changed in the v1.2 
config? Then re-do those changes in v2.2 and verify each step, that the 
particular setting is unchanged.

Expect some mailbox errors the first time, telling you that some files are 
broken and needed to re-create.

- -- 
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEVAwUBUw20yHD1/YhP6VMHAQIU9QgAgtUAgyOrQvohYj2bmUJNtuVX45kA5GR5
a8+8+WS1cV+UT4ihhlDFAWsAYzYvPL7X6qrcbhVt76myzfesOHxYPC2LfxmBkMVg
BJBxb3mRe+XNHZQPzrdxwAY2gvjvCr3q/X9ez35wKMFgAUnuVja8m2NOZgs8sWce
ZuaETllU9QcGt5rfP+m/5YEZPSFA4jrLt8BCqa7Q0pJTZBlwUMXRm782Psfh0+84
34dxz2FhiA3cJlbRFQYKEI1kkMGcRtm9Lu3UBUrGu9mMyTVxLx9hJkr9M40aHFdh
V+3WRGYZm5evLEtMnBxeH9XxOFEu7Bo5xiJaC9C5TX5LWITuAlJfXg==R3m6
-----END PGP SIGNATURE-----