Hi Sam,

I absolutly need a response to these questions, I will reply to your previous answer:

your answer is from the point of view of the client but it's on the server that I see the problem, in 'imapd'. When I test, I see that as soon as I move a file from a folder to the thrash, the quota is updated. (file size removed, the doc maildir/README.maildirquota.txt say it all) But if the files in trash do not count, I will never be over quota and no need for unlocking the account. I could maliciouly put 100GB of thing in trash, at least temporaly.

same goes here. I don't care about the client, I want to build a robust server, With enforced quota, independently of the way client handle their trash (litteraly ;-)

To quote a previous unanswer question I made:

Why .Trash so special ? whouldn't be easier if it was a _standard_ folder ? if you look in the source, everywhere their is check/if for this special case...clutter the code.

Same with file flaged 'T'. They should count in the quota until they get EXPUNGED. Up until then, you consume byte on the disk, part of your quota is used. simple. Why file flaged 'T' so special ? make them standard file for quota consideration, and de-clutter de source code, no ?

now what do you think ?

I'm awaiting answer, 'cause in courier it's easy to fix thing, but the patch 'qmail-ldap' is a mess ('cause of qmail). I like "Maildir" mailbox, and the extention for quota fit our need except this peculiar behavior. I'm sure I'm missing someting, the philosophy behind theses choices.

thanks Pascal