The only quick and easy band-aid I can think of is to delete the indexes and let dovecot recreate them.
-- Jeff Graves, MCSA Image Source, Inc. 508.966.5200 x31 www.image-src.com
-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Patrick Carney Sent: Tuesday, June 20, 2006 12:44 PM To: 'Timo Sirainen' Cc: dovecot@dovecot.org Subject: RE: [Dovecot] imap - mailbox in an inconsistant state
Yes. I was afraid of that. But the weird thing is it only happens with One particular user. And at that, it wasn't doing it for the longest time. It just started recently. Is there a band-aid for this. I ask because we are not in a place to upgrade at the moment.
Thanks Patrick
-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Timo Sirainen Sent: Tuesday, June 20, 2006 9:37 AM To: Patrick Carney Cc: dovecot@dovecot.org Subject: Re: [Dovecot] imap - mailbox in an inconsistant state
On Tue, 2006-06-20 at 09:07 -0700, Patrick Carney wrote:
"Jun 19 08:08:34 burmail imap(ed): Corrupted binary tree file /home/ed/mail/.imap/INBOX/.imap.index.tree: UID to be inserted isn't higher than existing (2 <= 504)"
Can someone tell me what that means?? I have been assigned to take over for a departed sys admin and have never used or administered Dovecot before.
You're using 0.99.x Dovecot and there's not much point anymore in trying to figure out why it's broken. I'd suggest upgrading to 1.0beta versions as the first step. If it still breaks after that I can help debug it further.