Email hoarder intervention and education - (Exchange environment)
Solution 1:
Our solution was a pit painful. One of our partner organizations (k12 education) was hit by discovery request in a lawsuit (FOIA). The costs to sort through the tons of email and redact the secret bits was huge (~$100k) because of how much email was saved that may have match the request. Our lawyers suggested, and our Superintendent put into place a strict retention policy so we could limit the costs of a request for us in the future.
By default all mail is purged after 45 days. Anything that must be saved for legal reasons, must be moved to a managed folder. There are a couple different managed folders with various retention policies applied.
Anyway, my point is, this should be a business decision, not IT complaining about storage. Do your best to make it clear the real costs, and point out the potential costs of having a huge mailbox. Then the executive officer to make a decision based on costs.
An arbitrary assigned quota will not make sense to a user.
Solution 2:
I believe that it's not your problem. To my mind it's some manager's problem. I don't think you need to be a hardass, but it sounds like somebody needs to be.
The user's unfettered email storage is costing the company money. The user wouldn't be allowed to hoard trash in their office-- why should hoarding trash on the email server be any different?
IT has to set limits on data storage because of performance and backup concerns. These are real, physical, tangible concerns. Hopefully your corporate policies on IT security, disaster recovery, email retention, acceptable use, etc, give these kinds of concerns some "teeth".
If it absolutely falls to you to "help" the user I'd consider, at a minimum, setting up Outlook rules to file incoming messages into "2010", "2011", "2012", etc folders based on date received. Then the user (or you) can prune old emails a year at a time. That'll also keep the Inbox folder smaller.
I've been a contractor for nearly all of my "IT life", so I've never had to fight the political battles around something like this. If I had a "C-level" user (or in a small business the owner or family of the owner) who was problematic like this I'd probably end up capitulating rather than fighting. I'd try to make a business case, at least, but I'd probably also end up giving up, and I'd definitely want that business case in writing for "CYA" purposes if their hoarding ends up creating operational difficulties.
Solution 3:
This may be a pure management issue, but in my experience this kind of decision devolves to the sysadmin staff to justify and enforce all too often. Because of this, it is my job as the sysadmin to convince management that there is a problem here and it should be taken seriously, and to posit management mechanisms that may be useful.
One of my old employers had a GroupWise system, which at the time didn't have any quota mechanisms in it (this was a while ago, GW has had it for some time now). So ultimately we resorted to a peer-pressure method. Each month we'd print off a report of the $X largest mail-boxes in each department and send the reports off to the office-managers. Within two months the top-5 list of largest mailboxes had a much smaller average size.
Some methods I've found useful for convincing management to pay attention to this issue:
Define the cost of mail storage
If you're getting the "but Google does it" pushback, start building spread-sheets that show how much mail costs. Managers understand cost. You, or the people you buy things through, have the costs for your server hardware, software, AV software, and other related costs. From this you can assign a dollars-per-MB number for mail storage. This allows you to give a decently good dollar value for a 3GB mailbox versus a 200MB mailbox.
This, by the way, is why you learned algebra back in school.
This can go one of three ways:
- They increase their mail-storage spend. They see the numbers, realized they're under-investing, and throw money at it to get to where you "should" be.
- They agree to provide downward pressure on mail growth in order to better control this cost.
- They say %*&!@ it! To the cloud!
Produce mail system upgrade costs
If the above is beyond your mad spreadsheeting skills, producing upgrade plans for keeping ahead of your storage consumption curve is a good way to at least get the conversation started. When they see bigbigmoney for upgrades, they'll ask why. And then you'll tell them. When they ask how they can avoid this cost, mention providing downward pressure on the big mail users.
I've done both of the above to justify simple storage purchases. The same techniques work for email, where you've got an entire application stack sitting on top of your storage/backup infrastructures. Dollars (or currency-of-choice) per unit is a great method of highlighting costs and the perils of overindulgence. Sometimes it can cause very significant strategic changes (see also, to the cloud!). Sometimes it can jar loose resources.
Politically speaking, it's a good idea to provide some suggestions for how to provide downward pressure for email consumption. But that's all they are, suggestions to the management who has to actually implement them or convince other managers to do so.
Solution 4:
We've had the same problem, it's currently under control, but I'm sure it will come back.
First of all, it's rarely the number of messages that's an issue - and it's not in your case, 22,000 is nothing, my mailbox runs to over 200,000 message - it's the &^%$# attachments.
I think attachments are a terrible way to store files, but lots of people like it because it preservers some meta-data: date sent or received and who a file was sent to or came from). Also, people are just lazy - it takes time to save and delete attachments.
In our case, education was the key: we made sure that people who "needed" a larger quota understood the hidden costs (backup time and storage needs, recovery time, the nightmare if there were a legal issue, etc.)
Then we made sure they understood that the biggest issue was attachments (this is why I kept so many emails online - I rigorously got rid of my attachments, so I could point to my own mailbox and say "I have 20 times as much mail as you, but my mailbox is less than 1/4 the size") and gave them some tools to help them deal with attachments.
The tools we used were mostly more training - e.g. how to sort messages by size, how to save attachments, how to save multiple attachments at once, how to also save an email to a file if they wanted the "meta-data," how to delete attachments (and the need to SAVE changes after deleting them), help with setting up directory structures, and so on.
In exactly two cases (and one of them was me), we were able to use 3rd party tools to help. There are a bunch of tools that will save messages and/or files, we use EZDetach and MessageSave, they're ok, but not really user-friendly enough for a lot of people (to be fair, none of the products I looked at for this function were easy enough for general users). For the one user, they learned to use the software and liked the idea of once a month running it to extract and delete all their attachments at once. For everyone else we tried to get to use it, they found it too complicated, so we stuck with basic Outlook training.
In our case, it worked because the President was one of the big users, and a senior manager was the the one who liked EZDetach. They gave us enough momentum to be able to tell people "nope, no one gets more email quota, if these techniques work for the bigwigs, they'll work for you!"
Solution 5:
It sounds you have a formal policy that the employees are aware of: There is a 3GB storage limit without valid reasons for a special-case exemption. "I don't read my mail" is not (IMHO) a valid reason.
The user's manager needs to be informed that the user is refusing to comply with company-wide IT policy, and you need to be prepared to make a business case to the C-Level offices as to why the policy makes sense. (In these days where everyone has a gmail account the real justifier is going to be cost).
If this person really needs their extra space they should be able to give you written justification for a quota bump.
Beyond that, you should send a CYA Memo (on paper, keep a copy) to the user(s) who are near the 3GB threshold and their manager(s) detailing the fact that the user will stop getting mail if they do not reduce their utilization or submit a valid reason they need more space. You already went out of your way once to help this person, so at this point after a written notice it becomes their responsibility to take action (clean up or beg a quota increase), otherwise the mail bounces become their fault.
You want to do everything you can to avoid a face full when the feces hits the fan because this person's mail is bouncing.