We've set mailbox quotas for our test users in exchange 2007 to 20mb to disable send and 15mb to warn, these limits have been set on the individual rather than on the database, however, when the user logs in using OWA they get the message stating they are over quota and unable to send email, yet they can still send emails quite happily. Also, if we set limits on the database of for example 200mb, these override any setting we have in the mailbox quota, these show up in OWA for the client and restrict sending when breached. Cheers

How log did you wait after setting up quota? It takes sometime due to information store service cache. Setting up quota at user level override at database level so in your case 20mb to disable and 15mb to warn will apply based on these settings are set at user level...Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Hello, This issue occurs because the Microsoft Exchange Information Store service uses the cached mailbox configuration to enforce mailbox size limits. The configuration change does not take effect until the cache is refreshed. The default interval for refreshing the cached mailbox information is two hours. You can change the setting by modifying registry. Check the following article for more information: Mailbox Size Limits Are Not Enforced in a Reasonable Period of Time http://technet.microsoft.com/en-us/library/bb684892.aspx Thanks, Elvis

If you changed the quota for someone and don't want to wait for 2 hours also don't want to modify registry values, then easy solution is just initiate that user's mailbox move to another DB and then cancel immediately it will refresh the new applied quota.