2.0.17 mailbox corruption

[Paul Christie]

URGENT: advise needed

Having just upgraded from 1.6.24 to 2.0.17 we are having problems with mail 
clients hanging at the point where they scan the entire hierarchy for 
shared folders which the user might have access to.

It takes a few hours, after the server is started, for this to occur. This 
corresponds with an increasingly large number of lockers in the error 
messages as below. I have no idea whether this is related.

Jan  7 18:37:05 serena.bath.ac.uk imapd[29994]: [ID 866726 local6.error] 
DBERROR db3: 422 lockers

On a possibly related matter I know that there are a large number of 
folders in the mailboxes.db which do not really exist. However since there 
is no reconstruct -m I can't see how to deal with this. I have seen a 
comment to the effect that reconstruct -r -f does much the same thing but 
this can't be run on the whole system and does not remove entries from the 
mailboxes.db, not in 2.0.17 anyway, as far as I can see.

All comment very welcome.


Paul Christie
Bath University Computing Services