Inbox management issue

Caporegime
Joined
21 Apr 2004
Posts
33,225
Location
Bristol
I'm looking for thoughts from like minded (or superior) individuals. We're on 2k3 sp2 here and we keep bouncing off the 75gb limit. I've been tasked with finding a solution that doesn’t involve buying a newer version of Exchange.

The issue is some people don't keep they're Inbox tidy, they have 4,5-7gb inboxes which they use effectively as a document management system with 50-100meg CAD files in.

We don't want to use PST's as local copies won't be backed up and networked PST's will put load on the server (which is like the exchange box, old). There are systems like Colligo that will allow Outlook to tie to SharePoint, so I could effectively allow them to move large amounts of emails to SharePoint. I feel this just moves the problem of poor document management from one place to another.

Ideally I'd implement 200mb inboxes, encouraging people to stop email CAD files about. But how would you go about dealing with the massive email inboxes?

I was thinking about exporting them as is to a PST, backing up the PST then placing it on the local machine with no ability to add more items to it. Then with the 200mb limit they can save the emails to relevant places on their network drives and viola the problem is solved (I think).

My question is, have you ever had this issue come up or have a better idea on how to manage this?
 
I had similar issue when we were running Exchange 2000. Only thing we did was impose size limits on all Exchange mailboxes. If user's mailbox went over 150mb in size Exchange wouldn't let user send any emails out, if mailbox went over 200mb Exchange would stop emails coming in/out for that particular user. This caused us some problems when staff went on holiday but otherwise staff were forced to keep inbox tidy. We also didn't allow any attachments over 10mb in size as that's Microsoft recommendation.
 
I could do that easy enough, it's just how to handle the initial issue of the inboxes. It's making sure I don't come across as a **** when I implement these changes. They're not going to be happy which ever way, but I want to make it as seamless as possible.
 
Personally I don't like limiting it, as in the absence of serious document management systems, outlook is pretty good to use casually in that role. It's available from anywhere and easy to access.

I particularly hate forced archiving as it's a very blunt tool which annoys the hell out of me (I need an email out of my archive urgently, oh but I'm on OWA or a different machine, tough luck...).

End of the day I see the solutions as

- A decent document management system so people don't use outlook for the job, this will cost a lot.

- An exchange implementation which will handle that usage, this will cost a fair bit too

- Various bad compromises involving archiving and mailbox limits.

End of the day email is one of the big areas where IT needs to follow the business's requirements rather than just do what the sysadmins fancy. Give them the options and let them decide what they want to do.
 
I BRIEFLY looked at some Sunbelt exchange archiving software which looked to have a decent enough price point and extensive feature list.

I never got round to putting it in a test environment but it may be worth your time.
 
I'm afraid if you want people to make proper use of e-mail, you must not put restrictions on it.

If you don't want them to use it as a DMS, put a DMS in place.

I suggest you ask your superiors if they would rather that communication in the workplace suffered due to OTT restrictions on their mailboxes. I know money is tight but they need to invest.

I'm not sure there is another way around it - but good luck.
 
I've taken you advice on board and I'm going to chat to my boss in a short while, run up some quotes and give him the option of how he wants to proceed. It's a management issue at the end of the day I don't want to say how were doing it but if I'm being held responsible with no option of budget then limiting is unfortantly the only way.
 
i presume you are using the standard version of Exchange here and you have done the reg fix to set the 75gig limit.. Enterprise version has no database limit.

i would get the users to clean up there mailboxes, archive, get rid of unwanted mail etc. Need to be tough on this one.

have a look through the event logs to see how much white space you can claim back. After they have archived, deleted old email etc, defrag the database if its worthwhile.

use eseutil to do an offline defrag of the database as this will shrink the database files.

create a mailbox quota policy and apply it to your stores.
 
Last edited:
i would get the users to clean up there mailboxes, archive, get rid of unwanted mail etc. Need to be tough on this one.

I strongly disagree with that last part, it's nothing to do with IT and being 'tough' about it is the wrong approach and it's what gets IT departments a bad reputation. Email is a service which exists for the users benefit and an IT teams job is to make it work for them, they don't exist for their own sake. You need to make management aware of the costs of large inbox sizes and let them make a call about additional investment or size limiting - it's their issue to solve and their issue to communicate it to staff (through you if they fancy). There are far too many nazi sysadmins who're on the power trip 'you must have a 100Mb mailbox, no exceptions' thing...
 
I strongly disagree with that last part, it's nothing to do with IT and being 'tough' about it is the wrong approach and it's what gets IT departments a bad reputation. Email is a service which exists for the users benefit and an IT teams job is to make it work for them, they don't exist for their own sake. You need to make management aware of the costs of large inbox sizes and let them make a call about additional investment or size limiting - it's their issue to solve and their issue to communicate it to staff (through you if they fancy). There are far too many nazi sysadmins who're on the power trip 'you must have a 100Mb mailbox, no exceptions' thing...

Amen to that - perfect!
 
Just wanted to say were now running Exchange 2007 we've given our users pretty big mailboxes and setup Quest Archive Manager for email archiving. Users seem happy with this setup and we're happy with no longer dealing with PST files and can recover emails if their deleted or for legal reasons.
 
As above we've implimented Symantec's version of e-mail archiving. The system is pretty seamless and its moved us away from PSTs sat on PCs around the office.
 
For a smaller org, look at Backup Exec's archiving option. I believe it's just Symantec Vault 'lite' bolted on to Backup Exec but not really looked at it in any great depth. As it's BE, I'd imagine the costs to be relatively small.

For larger orgs, Symantec Vault or EMC SourceOne should see you right.
 
Personally I don't like limiting it, as in the absence of serious document management systems, outlook is pretty good to use casually in that role. It's available from anywhere and easy to access.

I particularly hate forced archiving as it's a very blunt tool which annoys the hell out of me (I need an email out of my archive urgently, oh but I'm on OWA or a different machine, tough luck...).

<snip>

Symantec Enterprise Vault works through OWA and doesn't limit a user to a PC, you can even access your vault via an IE shortcut.

And now with V 8.0 SP3 your archive appears in Outlook as if it is an attached PST with federated search etc, users don't know the difference between it and a PST.
 
Definately worth looking at Barracuda Email archiving. Pretty cheap as an archiving solution as you dont have to pay a 'per mailbox fee', its just flat rate and it does the job it says on the tin. Retention policies included and nice outlook integration. Will allow your company to stay away from 'unsupported network PSTs' at a pretty decent price point
 
Proper email archiving is your friend, I did a Zantas EAS install a couple of years ao that drastically reduced our mail server storage without effecting users.

The other problem area is user education and offering an alternative to emailing large cad files around, email really isn't the best option for this but if you want users to stop you have to offer them a convenient alternative.
 
Proper email archiving is your friend, I did a Zantas EAS install a couple of years ao that drastically reduced our mail server storage without effecting users.

The other problem area is user education and offering an alternative to emailing large cad files around, email really isn't the best option for this but if you want users to stop you have to offer them a convenient alternative.

Agreed. Look into EAS Archiving Solution. Good system, works well.
 
We dont allow any attachments over 10mb external and 20mb internal.

Inbox sizes are as follows...

Over 500Mb – Warning about exceeding the size limit
Over 600Mb – Can no longer send emails
Over 700Mb – Can no longer send or receive emails

However we do backup some large PSTs (around 2gb i think is the biggest someone has) We assist anyone who needs help with getting their inbox to the correct size. Some people just forget to delete their 'deleted items' sometimes

We do use another document management (Watermark Volume)

Maybe having a (backed up) document management system for cad files etc instead of using Outlook to store it all is a better way to go
 
Last edited:
Guest... you should setup a mailbox management policy to empty the deleted items folder :)

^these are my new best friends.
 
Back
Top Bottom