We have had occasions where items in a user's dumpster are counting against their quota. Now it has happened to me! It may or may not be related to moving my mailbox back and forth between Exchange 2007 and Exchange 2010 in preparation for a migration. This morning I received the alert that my mailbox was almost full, containing 103MB. If, in Outlook, I view the mailbox size, it tells me that the total size is 28710KB with 2190KB in Deleted Items (183 items). Get-MailboxStatistics yields the following: AssociatedItemCount : 300 DeletedItemCount : 6935 ItemCount : 2935 TotalDeletedItemSize : 79430242B TotalItemSize : 30744398B Maibox is currently on Exch 2010 SP1. Database defaults are 48/58MB for Warn/Prohibit Send. Any ideas on why the Dumpster is apparently counting against the quota?

It should not, I would suggest you to move it into other store in same server and then recheck size of your mailbox. http://technet.microsoft.com/en-us/library/ee832796.aspxAnil

Hi, The size of Mailbox Dumpster is the Average size of each soft-deleted item X Amount of mail send/receive per mailbox per day X Deleted Item Retention Setting (14 days by default) and it will be considered against the total mailbox size. It’s usually 5 percent of the Mailbox Quota. You may configure deleted item Retention period using Set-MailboxDatabase <database_name> -DeletedItemRetention 7.00:00:00 Replace 7.00:00:00 with the number of days, hours, minutes, and seconds that you want for deleted item retention. Regards from www.windowsadmin.info

Thanks for the reply. From this article, http://technet.microsoft.com/en-us/library/ee364755.aspx, it appears that having recoverable items full will prevent deletion of additional items, but not sending, which is what I was experiencing--a symptom of a full parent mailbox. As Anil said, the dumpster should not affect the normal quota or the ability to send. In any case, it was Exchange 2007 that was indicating my mailbox was almost full (after being moved to Exchange 2010 and back to 2007). I was subsequently moved back to Exchange 2010, and did not receive the warning again. It may be because I'm back on 2010, or it may have been that everything was reset by the move, as Anil suggested.Mike

As I replied to ManU, this may have been what did the trick. It was simply a matter of waiting to see if the the warning was sent out the next night.Mike