Hi Kevin,
I think the point Bonno was making was that it was
the combination of file size AND number of recipients that was the
problem. He probably has a file size limit in place, but when a
10MB attachment goes to 100 people, you're suddenly at 1.2-1.4 GB of disk
space used. Yes, he could limit number of recipients as well, but that
would unnecessarily limit other broadcast messages on his network.
I think we all understand the education issue, but
also know we have to take steps to protect ourselves against users who forget,
don't realize, or just plain ignore the policies we put in place.
Darin. ----- Original Message -----
From: Kevin Bilbee
Sent: Tuesday, February 14, 2006 1:06 PM
Subject: RE: [Declude.JunkMail] large mail to large number op
recips I
realize this was an accident mailing but you should have in place attachment
size limits to avoid sucking the disk space of the mail server and to avoit
filling up mailboxes to unrealistic sizes. On average an attachment will become
20% larger once encoded in an email. Users should know a 10mb file
attachment will take up about 12mb of mailbox space and will be viewed as a 12mb
attachement.
I
would limit the size of attachments to no more that 10mb in the mail server to
start. Then I would setup an upload/download for files larger than 10mb. Educate
your users on how sending large files can cause all kinds of problems.
Like send/receive timing out and resetting, resulting in dulpicate mssages
being downloaded.
I get
calls all the time to delete large messages from mail boxes on domains that pay
to not have a file size attachemnt limit.
Kevin
Bilbee
|
- Re: [Declude.JunkMail] large mail to large number op recips Darin Cox