[Dovecot] Upgrade from 1.00 to 1.0.1
Hi,
I'm getting a bunch of errors since I upgraded to 1.0.0. I understand now that some of them are bug related to release 1.0.0. I'm about to upgrade to 1.0.1.
Does anyone know if there are changes in the config file btwn these to versions?
Also, what is the best way to do the upgrade? Can I just run ./configure : make : make install : killlall -HUP dovetcot?
Best Regards - Jon
On Wed, 2007-07-04 at 13:16 +0200, Jon wrote:
"*" marked items in NEWS file tells all the important changes.
Also, what is the best way to do the upgrade? Can I just run ./configure : make : make install : killlall -HUP dovetcot?
HUPing dovecot doesn't restart the master dovecot process. Rather:
./configure make killall dovecot make install dovecot
Hi Timo,
Wednesday, July 4, 2007, 4:44:38 PM, you wrote:
Does anyone know if there are changes in the config file btwn these to versions?
"*" marked items in NEWS file tells all the important changes.
FYI:
I use Linux 2.6.20-gentoo-r8 i686. Yesterday I switched from dovecot-1.0_rc29 to dovecot-1.0.1 and got error that was fixed:
Jun 9 14:34:11 mail dovecot: POP3(xxx@xxx.com): UID larger than next_uid in file /home/mail-root/xxx.com/xxx/dovecot-uidlist (1 >= 1)
Then I switched back to rc29 immediately.
Maybe this is a Gentoo related problem because port is masked.
-- Sergey
Hi Jon,
dovecot-1.0_rc29 works fine for me except namespaces (same problem with 1.0.1).
Thursday, July 5, 2007, 12:34:58 PM, you wrote:
Hi,
I tried uprading and I get less errors but I still get them. Don't you get any error messagess with dovecot-1.0_rc29?
/jon
-- Sergey
On Thursday 05 July 2007 10:49:02 Timo Sirainen wrote:
FWIW, after my upgrade from 1.0.0 -> 1.0.1, I started getting similar error messages in my mail.err log but no one is complaining so I figure they are harmless.
Jul 5 14:14:08 giganta dovecot: IMAP(hzzzz@arinbe.com): /home/hzzzz/Maildir/.Development.HUD/dovecot-uidlist: Broken header (uidvalidity = 0, next_uid=2) Jul 5 14:14:08 giganta dovecot: IMAP(hzzzz@arinbe.com): Maildir /home/hzzzz/Maildir/.Development.HUD sync: UIDVALIDITY changed (1168017041 -> 1183659248)
Jim
On 7/6/07, Jim Horner <jhorner@arinbe.com> wrote:
I also upgraded from 1.0.0 to 1.0.1. After the upgrade, I started getting these "UIDVALIDITY changed" errors, too. I'm currently considering downgrading to 1.0.0 again.
Maildir XXX sync: UIDVALIDITY changed (1183728784 -> 1183728864) POP3(YYY): Couldn't init INBOX: Internal error occurred. Refer to server log for more information. POP3(YYY): Corrupted index cache file XXX/dovecot.index.cache: indexid changed POP3(YYY): Maildir XXX sync: UIDVALIDITY changed (1183728956 -> 1183730221) POP3(YYY): Couldn't init INBOX: Internal error occurred. Refer to server log for more information.
Chris
Jim Horner wrote:
I've been getting these too since upgrading to 1.0.1 but because I have faith in Timo I assume that 1.0.1 is fixing some problem caused by the previous 1.0.0 and I have not been worrying about it. No user complaints, and it only seems to happen once per mailbox.
Mark
participants (7)
-
Chris Laif
-
Jim Horner
-
Jon
-
Jon Essen-Moller
-
Mark Nienberg
-
Sergey A. Kobzar
-
Timo Sirainen