[Dovecot] upgrading from old version 1.1.2 to version 2.0.11
Im getting ready to upgrade our production server from version 1.1.2
to version 2.0.11. Ive read through the upgrade info. Is there any
other gotcha's I should be aware of?
thanks,
ddh
-- Dwayne Hottinger Network Administrator Harrisonburg City Public Schools
"Everything should be made as simple as possible, but not simpler." -- Albert Einstein
"The hottest places in Hell are reserved for those who, in times of moral crisis, preserved their neutrality." -- Dante
On 03/07/2011 06:57 AM, dhottinger@harrisonburg.k12.va.us wrote:
Im getting ready to upgrade our production server from version 1.1.2 to version 2.0.11. Ive read through the upgrade info. Is there any other gotcha's I should be aware of?
thanks,
ddh
I just upgraded from 1.0.10 to 2.0.10 yesterday, and nary a problem (except those I created for myself). Just be sure to run your old configuration through doveconf, then make appropriate changes to the stock configuration. I really like the example structure, and would use that as a starting point. Then create a local.conf file for your particular preferences, and comment out the include_try line for local.conf in the dovecot.conf file.
Speaking of which, given that the local.conf file in the example configuration is the target of !include_try, why is it commented out??? (DOH!)
-Eric 'shubes'
On 7.3.2011, at 17.56, Eric Shubert wrote:
Speaking of which, given that the local.conf file in the example configuration is the target of !include_try, why is it commented out???
Its idea was simply to be an example of what you can do.. Maybe it's a bad example and could be something else, like maybe dovecot-secret.conf. There is anyway already !include conf.d/*.conf so you could just put your local.conf to conf.d/ directory and it would get used automatically.
On 03/07/2011 02:47 PM, Timo Sirainen wrote:
On 7.3.2011, at 17.56, Eric Shubert wrote:
Speaking of which, given that the local.conf file in the example configuration is the target of !include_try, why is it commented out???
Its idea was simply to be an example of what you can do.. Maybe it's a bad example and could be something else, like maybe dovecot-secret.conf. There is anyway already !include conf.d/*.conf so you could just put your local.conf to conf.d/ directory and it would get used automatically.
True enough.
My point was simply that !include_try local.conf does not need to be commented out at all, since it's just a try. What's the purpose of commenting it out?
I really do like the idea of a local.conf file, literally. I created one myself for my own (local) configuration settings after reading through the dovecot.conf file. It wasn't until I tested my local.conf settings that I realized that the statement in the dovecot.conf file was commented out! My bad that I didn't notice the comment to begin with, but then it occurred to me - why is it commented? Works the same either way. :)
-- -Eric 'shubes'
it's simply
in my blog are two exemple from old config to new config
http://fakessh.eu/2010/08/29/dovecot-n-dans-les-moindres-details/ http://fakessh.eu/2010/06/10/la-config-de-mon-postfix-et-de-mon-devocot/
Le lundi 07 mars 2011 à 08:57 -0500, dhottinger@harrisonburg.k12.va.us a écrit :
Im getting ready to upgrade our production server from version 1.1.2
to version 2.0.11. Ive read through the upgrade info. Is there any
other gotcha's I should be aware of?thanks,
ddh
-- gpg --keyserver pgp.mit.edu --recv-key 092164A7 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x092164A7
participants (4)
-
dhottinger＠harrisonburg.k12.va.us
-
Eric Shubert
-
fakessh ＠
-
Timo Sirainen