Poll: Email retention and mailbox quotas

HCL Domino Domino Forum
1

I am working a business case to the upper management of my company for revising our email retention policy to combat the rapidly increasing size of our mail store. I’m trying to get as much info as I can on what other companies are doing to justify what I am proposing. All responses to the following questions will be much appreciated:

  1. What is your company doing with email retention?

  2. What is your company doing with mailbox quotas?

  3. How many users in your environment?

Thanks in advance!

2

Subject: Poll: Email retention and mailbox quotas

hard disks are a lot cheaper than lawsuits, a good archiving policy can also help in keeping the active mailfiles to a manageable size and store old mail in a central archive for retrieval if required.

3

Subject: RE: Poll: Email retention and mailbox quotas

That may be true for your Executive team, but really, why would I want to save every email to an archive, including those sent/received by the users at the bottom of the corporate ladder?

4

Subject: Re: Poll: Email retention and mailbox quotas

I’ll start it off with what we’re currently doing…

  1. 1 year retention - Messages are purged after 1 year

  2. No quotas - You see why I want to revise this :slight_smile:

  3. 21,000+ users

Paul

5

Subject: RE: Re: Poll: Email retention and mailbox quotas

  1. 45 day purge, except Calendar entries: kept forever2) No quotas

  2. 15,000+ users

6

Subject: RE: Re: Poll: Email retention and mailbox quotas

Hi,There are other possible solutions to combat storage other than quotas and retention. You can compress attachments, restrict uses from sending big emails, remove duplicate attachments, reduce image resolutions to reduce size, …

There are tools at www.zipmail.com that will help you to not only reduce storage but improve the bandwidth.

Using quotas is not really user-friendly: The user sends a big email and two hours later that user sees this email rejected! It may be an important email! So implementing restrictions in the workstation rather that in the server will prevent such cases since the user will get prompted as soon as the email is tried to be sent.

HTH