Hi I'm about to upgrade to 2.1.7 in my test environment, but "doveconf -n -c dovecot.1.conf > dovecot.2.conf" is producing a blank file, so I am unsure how to proceed. I know a lot has changed between them, so I don't really want to have to start from scratch unless I have to. I have tried both as my user and with sudo. Simon
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 5 Mar 2013, Simon Brereton wrote:> I'm about to upgrade to 2.1.7 in my test environment, but "doveconf > -n -c dovecot.1.conf > dovecot.2.conf" is producing a blank file, so I > am unsure how to proceed. I know a lot has changed between them, so Ihonestly, especially because "a lot has changed between them" I would start from scratch.> don't really want to have to start from scratch unless I have to.check what you have changed in v1.2 config, then check if that particular setting has changed or the functionality has changed, and finally change the default in v2.1 - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUTX/PV3r2wJMiz2NAQI2AAf+Iq80FmUHsZp1qvD7R8q14V2NCwK4Tktp 3LN+yjMaeaZ+FJEDGsZD99eEDhfqNSU1BCbQl/RfXjMngr8ptBLowqCb7ooSK3X4 jjK9bf8eHaKbjpEMMlHACFWkxl8nCgT0IHqQk//L+sic8UhgbuyXyv5oo4nyTc7A 4WQBWnB7nfx9zmfARDCJpEhM2sEPzU74BU9OQ94hyKCczIEMHj5Ri/rnqfuustvZ pBHOyOb6a4XJ51LffviVucgpoLvO1fYJK2L3ztbybS9RnySZTtIwFr56dtfTWNed VByo0ICJW0djinnkBKjOb0s29OydjHbrsTfFcZOEeCOgKj9mShyzqA==F9YZ -----END PGP SIGNATURE-----
On Tue, 2013-03-05 at 11:33 +0100, Simon Brereton wrote:> Hi > > I'm about to upgrade to 2.1.7 in my test environment, but "doveconf > -n -c dovecot.1.conf > dovecot.2.conf" is producing a blank file, so I > am unsure how to proceed. I know a lot has changed between them, so I > don't really want to have to start from scratch unless I have to. > > I have tried both as my user and with sudo. > > SimonSounds like symptom of an error or something in 1.conf, I found converting that if it strikes something it does not like it bails there and then, but it gave me about 80% conversion, only requiring tweaking to finalise it, however it did not convert quota stuff to new format so start that from scratch. When you run convert it usually spits out what it is, or is not doing, that must give you some clue. and should matter what UID you are on, so long as you have read access to 1.conf and write access to 2.conf -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20130306/337ec2eb/attachment.bin>
Simon, * Simon Brereton <simon.buongiorno at gmail.com>:> I'm about to upgrade to 2.1.7 in my test environment, but "doveconf > -n -c dovecot.1.conf > dovecot.2.conf" is producing a blank file, so I > am unsure how to proceed. I know a lot has changed between them, so I > don't really want to have to start from scratch unless I have to.unless you have spent hours tweaking your config, setting up Dovecot 2.x should be fairly easy. If your old config isn't too complex I wouldn't waste time discussing this problem, but move on to create it from scratch in 2.x. p at rick -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich