Subject: How Mail Capping works
You should be setting this up using the database properties and can easily turn it on in your environment through the admin client.
To enable this… I’ll give you an idea of how to get to these instructions from either the names.nsf or the admin client:
First go into your server’s configuration settings:
Admin client - Configuration Tab … Server … Configurations … Edit the configuration for your mail server(s) / Names.nsf Configuration … Servers … Configurations … Edit the configuration for the current server.
In the configuration document you want to go into the Router/SMTP tab … Restrictions and Controls … Delivery Controls.
That section (Delivery Controls) has a spot for Quota Controls. This is where you set how often people will get their over threshold warnings (be careful how often you do this, we do it daily and even that irritates some… but that may be your goal…) as well as how often you send over quota intervals and how the server enforces the quota. You can hold mail and retry, deliver regardless of the quota or simply reject the message immediately. Hold and Retry is nice because it gives the recipient a chance to clean their file up of they go over quota… if they do that, the system will automatically retry and deliver the message.
Once you’ve set this to your liking, you’ll want to set the quota. Going into Filesl on the server you can select some or all of the mail files, right click and choose the “Quotas” option. Pick the warning threshold and the quota itself.
You can go through the process of creating settings/ policies and enforce one for new users that includes the quota or (as we do) simply set that on setup.
One thing to be aware of is that a quota on server A doesn’t translate into the same quota on Server B if you make a replica there. Also, people are great a lifting quotas temporarily to allow a person to continue receiving mail because they are always too busy to clean things up… of course there is no reminder to put it back in place.
And another tidbit of helpful information, when calculating quotas, the server takes into account white space and what it finds in the trash (if you use soft deletes and the trash) when attempting to deliver. So an over quota user could throw 50 MB of mail in the trash, not compact, but still have room to receive mail. We run Transaction logging and can’t compact on the fly so we’ve tried to educate our support folks on this fact … that doesn’t prevent a threshold WARNING from going out, but keeps them getting mail until the weekly space reducing compacts run.