My company implemented Exchange 2007 in July of last year (2007). We have a dilemma in our implementation of quotas that is fueled by what appears to be a technical issue with the Exchange 2007 mailbox-database architecture. (or perhaps a malformed environment!). The problem we face is this: If we implement a hard quota, we've found that we are unable to reverse the designated restriction (send/receive) once the user has "cleaned up" their mailbox. The problem appears to be related to the dumpster retention time. If data is moved off of the server (i.e. into a PST archive) or even deleted, it goes to the dumpster; which to my knowledge still occupies "recorded" space in the mailbox and counts against the quota. The only solution to "re-enabling" the mailbox once the quota is reached that we can find is to either expand the quota or enforce cleanup and then "move the mailbox" to clear the whitespace. I guess that's a workaround. What we really want is this: A) Migrate data the off of the server into a PST such that the quota is not exceeded. B) Exclude the data from the dumpster so it is not included in the dumpster retention period. Most departments consider mail communications business-critical, so having an inbox offline for an extended and unspecified period (when would the space be re-stated in the database?) because of quota violation is not acceptable. On the other hand, we could fill up and dismount databases at any time because hard quotas are not set. What are we doing wrong?