We help IT Professionals succeed at work.

Mysterious "Over you quota limits" in Exchange 2010. Any ideas on why users are getting these message if Quota has not been met?

admitech
admitech asked
on
Mysterious "Over you quota limits" in Exchange 2010. Any ideas on why users are getting these message if Quota has not been met? End users are getting over the limit errors in outlook even though the minimum level (quota) has not even been met yet. (IE Warnings for reaching 310 mb for example when the warning quota is set to 400mb).
Comment
Watch Question

That is a classic phishing scheme.  Are they phishing emails or real ones?
William FulksIT Services Analyst

Commented:
How close are they to the warning level? Could be something hung up in Exchange that may be pushing it over the limit, like a large outgoing or incoming message. A screenshot of the error would help, too.
MacleanSystem Engineer

Commented:
Did you make 100% sure that none of the users have a quota applied at either mailbox or mailstore level?
One usually will find that if the message is legitimate, it would be coming from the back-end exchange.
Exchange Experts
Commented:
1) First Check the Quota Limit on Exchange Database using following powershell command

Get-MailboxDatabase | fl IssueWarnningQuota,ProhibitSendQuota,ProhibitSendReceiveQuota

2) Check Mailbox Quotas Per User using following powershell command

Get-Mailbox -Identity "server_support" |fl IssueWarnningQuota,ProhibitSendQuota,ProhibitSendReceiveQuota

3) Use PowerShell to see which user has exceeds the quota limit

Get-MailboxStatistics -Database MDB01 | ? {$_.StorageLimitStatus -eq “IssueWarning” -OR $_.StorageLimitStatus -eq “ProhibitSend” -OR $_.StorageLimitStatus -eq “ProhibitSendReceive”} | Select DisplayName, Alias, StorageLimitStatus

4) Use PowerShell to see which users received a quota message:

Get-TransportServer | Get-MessageTrackingLog -ResultSize Unlimited -MessageSubject “your mailbox is” –EventID DELIVER | Select TimeStamp, Recipients, MessageSubject

Using above powershell command you will be able to find the root cause.

Author

Commented:
apparently this was client side (outlook) issue

Author

Commented:
Didn't really identify the issue but is a PowerShell List of command to keep in the toolbox! Thanks