[Dovecot] Suggestions for upgrading dovecot 1.0.7 Redhat EL 5.x

[Steffen Kaiser]

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

On Tue, 26 Feb 2013, Götz Reinicke - IT Koordinator wrote:

> we still have our solid rock dovecot 1.0.7 Redhat el 5.x up and running.
>
> We don't need much magic or special setups.

The configuration has been split up since v1.0, but you can grep through 
the files and find the spots easily. Also, if you didn't changed much in 
v1.0 (that is how I understand your "don't need much magic or special 
setups"), the chances are good, that you'll not change much in v2.1 or 
v2.2.

> However we'd like to think what might be the next step in upgrading our
> setup. Each user one mbox mailbox. About 500 imap/pop3 accounts, 400GB data.
>
> First of all: to what version is a good step from 1.0?

I would setup a Dovecot v2.2 server, it's RC2, but Dovecot is usually more 
stable than other software ... .

However, I would install the whole server anew, no automatic upgrade or 
whatsoever.

> Dose anyone has any experiences in doing such a "big" step forward?

I have upgraded a v1.0 to v2.1 now. No big deal from Dovecot.

> Can we get a rpm from e.g. atrpms repository?

Ah, OK, then use the most current version available :-) I build Dovecot 
from source.

> Or should we think of migrating to a total updated Redhat EL 6.x /
> Dovecot 2.0.x system?

I don't know Redhat, but it seems to be wise to upgrade. What's the "Known 
Bug List" or "Known Security Holes" in Redhat EL 5.x?

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

iQEVAwUBUSy9Gl3r2wJMiz2NAQLjEQf+Ju37uRQ7FCM+F9yjS3vOqJIZeFF7HEvZ
UvDQjWkb1B7hJcfBOSP/TtsdI2BBiEeUzs1m+1QC4oxiz5Dy3ids1AAl7adhqm1e
o83YfpQVIBdITF51myq6PLLD8+AwmaNIcTadURPBOrM+ZpOmCn9k433QVmhR6HL5
3xgIHoqGzEz9TbFnGji5iZ8XrwvypJgP50tASPn6INXywKJ0qOUCd/ZeuupJs4dt
tYLdZEOHwUs5L77gvANDn/uXB7Yyho4ovtapEsrCeRhDKriABzkuwySGWuB5OHZ9
bhwqU6/lF8gAr/l1kCjiavht+tMQT/lnNMWdUfMTsUBT3rwm/usVnw==
=hL5a
-----END PGP SIGNATURE-----