Re: quota issues solved? (was RE: Large spool mboxes => slow?)

It is not corrupt in the unparseable sense, but the following was happening 
(I quote from a previous post):

When the user starts his mail client and his spool was left at the
temp file due to overquota problem, his client re-gets all the
mail in the temp file along with the new in the spool.
But the mail in the temp file was already downloaded to the client and old 
mail appears now duplicate and new mail once normal. The next time he checks, 
mail is duplicated again , old-old messages exist now 3 times, old 2 times 
and new just appended from spool 1 time. And so on. We assume he has "leave 
messages on server".
This behaviour was observed on at least one brand of MUA (one of them being 
netscape 4.x) on 2003. Your reply was that the msg-ids were the same so the 
clients should download each message once, but since we changed the locking 
mechanism we were no longer able to confirm this problem with modern client 
versions, so it may still exist or not. I am sorry but I can't be of more 
help on this.


Randall Gellens wrote:
> At 12:37 PM +0300 4/8/06, Spiros Ioannou wrote:
> How are the mailboxes getting corrupted?  Qpopper should handle the 
> quota error by leaving the temp drop in place, not by corrupting the 
> mailbox.  If there is a bug that causes mailboxes to get corrupted, I 
> want to know about it.