That's not the same thing (even though they're both uid). The uid message you are getting is the id of the message that dovecot uses in its indexes to find a message and it's attributes. The uid in the conf is the user id for whose allowed to login. Eg. Root is userid 0 and most daemons have user ids less than 500, so if the uid in the conf were the case, that user would have never been able to log in and you would get a message in the log about authentication or something similar. Did you try deleting the indexes? If the problem came back after that, I would guess that there's a particular message in the mailbox causing the problem.
I google'd and found this message from the 0.99.x series but it says it may be related to locking:
http://www.dovecot.org/list/dovecot/2003-May/001613.html
Which version of 0.99 are you using?
-- 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: Thursday, June 22, 2006 11:47 AM To: 'Chris H.'; dovecot@dovecot.org Subject: RE: [Dovecot] imap - mailbox in an inconsistant state
Yes. I looked into that. But our conf. file has this:
# Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 first_valid_uid = 100 #last_valid_uid = 0
# Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0
Patrick
-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Chris H. Sent: Wednesday, June 21, 2006 5:50 PM To: dovecot@dovecot.org Subject: Re: [Dovecot] imap - mailbox in an inconsistant state
Greetings, Please forgive me if this has already been answered. But it would appear that the UID that is attempting to access the mailbox in question is LOWER than the MINIMUM UID allowed in your dovecot.conf file.
Hope this helps you fix it.
Quoting Patrick Carney patrick@castandcrew.com:
Can anyone help me with this issue?
The CEO of our company keeps getting IMAP time out errors and "mailbox is in an inconsistent state" messages. He uses Outlook 2003.
There are errors on the server side. This is what it says:
"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 hi
gher 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.
Thank You!
Patrick
-- Shameless self-promotion follows... ... or does it?
FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 /////////////////////////////////////////////////////////////////