Moe Wibble wrote:

On Wed, Apr 16, 2003 at 10:58:15AM +0200, Farkas Levente wrote:

...

hi, in the yesterday cvs, an internal error in the imap message appear in the client side and in the maillog:

Apr 16 10:01:42 red imap(zgabor): Corrupted index file /home/zgabor/Maildir/.Lists.Bugtraq/.imap.index: Invalid seen messages count (284 < 285) Apr 16 10:01:43 red imap(zgabor): Corrupted index file /home/zgabor/Maildir/.Lists.Linux/.imap.index: Invalid seen messages count (191 < 192) Apr 16 10:01:44 red imap(zgabor): Corrupted index file (in-memory index for /home/zgabor/Maildir/.Lists.Linux): Filename mismatch for UID 1: 1050448183.2238_1.red.int.bppiac.hu vs 1050321835.21498_1.red.int.bppiac.hu

ACK. I'm getting similar errors: Apr 16 15:22:13 rafter imap(moe): Corrupted index file /<snipped>/.INBOX/.imap.index: index.next_uid (441) > uidlist.nex t_uid (440)

Yesterday's CVS version running here. Removing the '.imap.index'-file has stopped the errors so far.

Haven't noticed any other side effects, yet.

we still got these errors (after the delete)...

-- Levente "Si vis pacem para bellum!"

On Wed, Apr 16, 2003 at 03:46:28PM +0200, Moe Wibble wrote:

On Wed, Apr 16, 2003 at 10:58:15AM +0200, Farkas Levente wrote:

...

hi, in the yesterday cvs, an internal error in the imap message appear in the client side and in the maillog:

Apr 16 10:01:42 red imap(zgabor): Corrupted index file /home/zgabor/Maildir/.Lists.Bugtraq/.imap.index: Invalid seen messages count (284 < 285) Apr 16 10:01:43 red imap(zgabor): Corrupted index file /home/zgabor/Maildir/.Lists.Linux/.imap.index: Invalid seen messages count (191 < 192) Apr 16 10:01:44 red imap(zgabor): Corrupted index file (in-memory index for /home/zgabor/Maildir/.Lists.Linux): Filename mismatch for UID 1: 1050448183.2238_1.red.int.bppiac.hu vs 1050321835.21498_1.red.int.bppiac.hu

ACK. I'm getting similar errors: Apr 16 15:22:13 rafter imap(moe): Corrupted index file /<snipped>/.INBOX/.imap.index: index.next_uid (441) > uidlist.nex t_uid (440)

Yesterday's CVS version running here. Removing the '.imap.index'-file has stopped the errors so far.

Haven't noticed any other side effects, yet.

The bug has just hit me again:

Apr 20 02:08:00 rafter imap(moe): Corrupted index file /<snipped>/.INBOX/.imap.index: index.next_uid (495) > uidlist.nex t_uid (494)

Removing .imap.index has muted it once again.

Is this problem being worked on?

regards

MW

On Mon, Apr 21, 2003 at 04:49:34PM +0300, Timo Sirainen wrote:

On Sun, 2003-04-20 at 03:11, Moe Wibble wrote:

...

The bug has just hit me again:

Apr 20 02:08:00 rafter imap(moe): Corrupted index file /<snipped>/.INBOX/.imap.index: index.next_uid (495) > uidlist.nex t_uid (494)

Removing .imap.index has muted it once again.

Is this problem being worked on?

I think it should be fixing itself now. The index is rebuilt automatically next time the mailbox is opened.

I have just updated and the problem has not appeared again since then. Hope it stays that way.

I also found a few more potential problems with it, -test6 should come out soon.

What kind of problems?

regards!

MW