The Quota warning message can redirect message to administrator

I don't believe so. If the administrator wanted to know when users had exceeeded quoat, they could use Powershell to check rather than receiving (potentially) hundreds of emails. Get-MailBoxStatistics | where {"IssueWarning","ProhibitSend","MailboxDisabled" -contains $_.StorageLimitStatus} | format-Table DisplayName, @{expression={$_.totalitemsize.value.ToMB()};label="Mailbox Size(MB)"}, itemcount

Although I think that the best practice would be to follow the advice in Chris' response. If you really wanted to go down the road of a mail being sent to an administrator - would a Transport Rule on your HT Server suffice? Something along the lines of Apply this rule to messages; when the subject field contains "specify the warning message that your users recieve"; bcc/copy/redirect (as necessary) the message to "admins email address". Not sure if this is of any help to you?

Dear Chirs For system admin can run powershell My case is the user (Manager) she want to know those information, BTW we can create a report like your powershell, but i think this is not got, when you send a schedule report to user Most user will ignore this message and some mailbox are already exist the limit when we sent out the report. so many issue foresee Dear David I think using HT Rule also, but i try it before using HT rule to redirect the NDR message. It is not work , BTW i will try to use HT rule for testing first Thanks you help (Chirs and David) Happy Easter

Hello, You can create the transport rule by filtering the title of the quota warning emails. Generally, the quota message have standard titles. Please refer to the following article to see the titles: http://technet.microsoft.com/en-us/library/bb232173.aspx Thanks, Simon

Hi, Mailbox quota messages are system generated messages and by design exchange transport rules doesn't apply on such messages like; NDR, message receipts and Quota messages. If you want to stop this to be delivered to user's mailbox, disable this from mailbox database's property. Tarun Verma**Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.** Tarun Verma

I'm not sure who you mean when you say users will ignore the message. If you mean the quota message to the end user, if you set Prohibit Receive to a number significantly larger than Prohibit Send and have a reasonable Issue Warning limit then users will be warned multiple times that they won't be able to send mail. Then they won't be able to send, but could still receive for months. If an employee can do their job without sending emails for months, ignore all the warnings that come with it and not be fired then I don't really see the problem. If you meant the supervisor would ignore daily reports emailed to them of the output of the powershell script I mentioned, that seems like a non-issue as well. It just means they asked for yet another report they don't need and won't read.... I think they teach that in business school.

On Fri, 15 Apr 2011 15:44:56 +0000, Chris Scharff wrote: > > >I'm not sure who you mean when you say users will ignore the message. If you mean the quota message to the end user, if you set Prohibit Receive to a number significantly larger than Prohibit Send and have a reasonable Issue Warning limit then users will be warned multiple times that they won't be able to send mail. Then they won't be able to send, but could still receive for months. > >If an employee can do their job without sending emails for months, ignore all the warnings that come with it and not be fired then I don't really see the problem. > >If you meant the supervisor would ignore daily reports emailed to them of the output of the powershell script I mentioned, that seems like a non-issue as well. It just means they asked for yet another report they don't need and won't read.... I think they teach that in business school. It's a learned behavior, Chris, much like one of my favorite stories: Start with a cage containing five monkeys. Inside the cage, hang a banana on a string and place a set of stairs under it. Before long, a monkey will go to the stairs and start to climb towards the banana. As soon as he touches the stairs, spray all of the monkeys with cold water. After a while, another monkey makes an attempt with the same result - all the monkeys are sprayed with cold water. Pretty soon, when another monkey tries to climb the stairs, the other monkeys will try to prevent it. Now, turn off the cold water. Remove one monkey from the cage and replace it with a new one. The new monkey sees the banana and wants to climb the stairs. To his surprise and horror, all of the other monkeys attack him. After another attempt and attack, he knows that if he tries to climb the stairs, he will be assaulted. Next, remove another of the original five monkeys and replace it with a new one. The newcomer goes to the stairs and is attacked. The previous newcomer takes part in the punishment with enthusiasm. Again, replace a third original monkey with a new one. The new one makes it to the stairs and is attacked as well. Two of the four monkeys that beat him have no idea why they were not permitted to climb the stairs, or why they are participating in the beating of the newest monkey. After replacing the fourth and fifth original monkeys, all the monkeys that have been sprayed with cold water have been replaced. Nevertheless, no monkey ever again approaches the stairs. Why not? Because as far as they know that's the way it's always been around here. And that's how company policy begins ... --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP