AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<Robert.England@lsi.com>,<Trinh.Tran@lsi.com>,<Larry.Scheer@lsi.com>,<Brian.Stark@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#mh/Mailbox/perfarce	0	7C44B44C1DCF8E4197AF0A1EF03A1DD83598D2DE@PALMAIL01.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 28 Jan 2010 14:34:29 -0800
From: Andrew Sharp <andy.sharp@lsi.com>
To: "England, Robert (Robert)" <Robert.England@lsi.com>
Cc: "Tran, Trinh" <Trinh.Tran@lsi.com>, "Scheer, Larry"
 <Larry.Scheer@lsi.com>, "Stark, Brian" <Brian.Stark@lsi.com>
Subject: Re: Undeliverable: PERFORCE change 34273 for review
Message-ID: <20100128143429.4ab92e80@ripper.onstor.net>
In-Reply-To: <7C44B44C1DCF8E4197AF0A1EF03A1DD83598D2DE@PALMAIL01.lsi.com>
References: <5BD8489488DB2440ABB93FC6779E533F986B3CD3@cosmail01.lsi.com>
	<7C44B44C1DCF8E4197AF0A1EF03A1DD83598D2DE@PALMAIL01.lsi.com>
Organization: LSI
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Oh yes, I'm quite up to date with all the rationalizations.  What I
find amuzing is that nowhere in there is any notion of "...how do we
fulfill the needs of our users" and by that I mean, all the needs, not
just the needs of a particular set of users.  Kind of like a "no child
left behind" policy.  And, yes, I'm referring to myself there.

Since this was set more than 4 years ago, perhaps it's time to revisit
the limits in this day and age.  Put another way, 25MB ain't as big as
it used to be ~:^)

On Thu, 28 Jan 2010 06:55:29 -0700 "England, Robert (Robert)"
<Robert.England@lsi.com> wrote:

> Andrew et al,
> 
> We have file size limitation set to ensure a specific level of
> performance and service level. Prior to setting this 4+ years ago,
> extensive research and testing went into determining this size, we
> had conversations with Microsoft, and we researched best practices
> and based on all that our limit was determined.
> 
> You should consider using SharePoint for this as you can email data
> into SharePoint and then email a link versus sending a 25mb+ file
> that would inevitably keep the recipients mailboxes smaller.
> 
> 
> Issues that can arise from a lack of internal message size quota
> policy:
> 
> -         Denial of Service Attacks - Without or with improper
> message size limits, a hacker (whether internal or external) can
> easily implement a denial of service attack by sending messages with
> large attachments, ultimately using all available resources on the
> Exchange servers, thereby causing system failure. Even a user who
> does not have an ill intent could send a large message to a large
> number of people and have an impact on performance.
> 
> -         Capacity Planning - Improper quota management effectively
> limits any type of future capacity planning (e.g. cannot predict
> future database growth).
> 
> -         Backup/Restore Windows - Improper quota management will
> ultimately impact backup restore windows.  As the database sizes
> grow, the backup window will increase.  At some point this backup
> window will interfere with business hours.  The same is true for the
> restore window.
> 
> -         Virus Scanning - Improper quota management will incur
> performance penalties on virus scanning of the messages.
> 
> -         Anti-Spam Measures - Many anti-spam products won't scan the
> message if they are over a certain size.
> 
> -         Network Utilization - Network utilization will increase as
> messages are sent between Exchange servers and between the Exchange
> organization and the Surf Control relay devices.
> 
> 
> 
> Thanks and Regards,
> 
> Robert England | LSI Corporation, Allentown PA | Office:
> 610-712-5549, Mobile: 610-216-1886
> 
> 
> 
> -----Original Message-----
> From: Tran, Trinh
> Sent: Wednesday, January 27, 2010 9:09 PM
> To: Sharp, Andy; Scheer, Larry; England, Robert (Robert)
> Cc: Stark, Brian
> Subject: Re: Undeliverable: PERFORCE change 34273 for review
> 
> Bob,
>   Can you follow up?
> 
> Trinh
> 
> ----- Original Message -----
> From: Andrew Sharp <andy.sharp@lsi.com>
> To: Scheer, Larry
> Cc: Stark, Brian; Tran, Trinh
> Sent: Wed Jan 27 18:15:06 2010
> Subject: Re: Undeliverable: PERFORCE change 34273 for review
> 
> 
> Dang.  This never used to happen.
> 
> OK, this has to be fixed.  A change email was bounced by our fraking
> exchange server for being too large.  Not cool.  I don't know if we
> have to teach exchange to ignore that restriction for this sender (I'm
> not sure how that would work since it seems to come from me but really
> comes from the perforce server) or just raise our overly-stingy
> limits for this modern era.
> 
> 
> On Wed, 27 Jan 2010 17:10:20 -0700 "postmaster@onstor.com"
> <postmaster@onstor.com> wrote:
> 
> > Delivery has failed to these recipients or distribution lists:
> >
> > agarwal anurag<mailto:anurag.agarwal@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > mitra anand<mailto:Anand.Mitra@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > Sharp Andrew<mailto:andy.sharp@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > Fisher William<mailto:bill.fisher@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > Stark Brian<mailto:brian.stark@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > chris.greiveldinger@lsi.com<mailto:chris.greiveldinger@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > Vandever Christina<mailto:chris.vandever@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > david.olien@lsi.com<mailto:david.olien@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > david.phelps@lsi.com<mailto:david.phelps@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > Lau Henry<mailto:henry.lau@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > Seidel Jan<mailto:jan.seidel@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > Ariyamannil, Jobi<mailto:jobi.ariyamannil@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > Goldick Jonathan<mailto:jonathan.goldick@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > Scheer Larry<mailto:larry.scheer@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > Kozlovsky Maxim<mailto:maxim.kozlovsky@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > Fong Rendell<mailto:rendell.fong@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > Upendran Praburam<mailto:ram.upendran@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > Chandra Svati<mailto:Svati.Chandra@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > siva.kodiganti@lsi.com<mailto:siva.kodiganti@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > sam.revitch@lsi.com<mailto:sam.revitch@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> > usha.ketineni@lsi.com<mailto:usha.ketineni@lsi.com>
> > This message exceeds the maximum message size allowed. Microsoft
> > Exchange will not try to redeliver this message for you. Please make
> > the message smaller -- by removing attachments, for example -- and
> > try sending it again, or provide the following diagnostic text to
> > your system administrator.
> >
> >
> >
> >
> >
> >
> >
> > Diagnostic information for administrators:
> >
> > Generating server: mail.onstor.com
> >
> > anurag.agarwal@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > Anand.Mitra@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > andy.sharp@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > bill.fisher@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > brian.stark@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > chris.greiveldinger@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > chris.vandever@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > david.olien@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > david.phelps@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > henry.lau@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > jan.seidel@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > jobi.ariyamannil@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > jonathan.goldick@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > larry.scheer@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > maxim.kozlovsky@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > rendell.fong@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > ram.upendran@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > Svati.Chandra@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > siva.kodiganti@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > sam.revitch@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > usha.ketineni@lsi.com
> > #< #5.2.3> #SMTP#
> >
> > Original message headers:
> >
> > From: Andrew Sharp <andy.sharp@lsi.com>
> > To: "aagarwal" <anurag.agarwal@lsi.com>, "amitra"
> > <Anand.Mitra@lsi.com>, "Andrew Sharp" <andy.sharp@lsi.com>,
> > "bfisher" <bill.fisher@lsi.com>, "brians" <brian.stark@lsi.com>,
> > "Chris Greiveldinger" <chris.greiveldinger@lsi.com>, "chrisv"
> > <chris.vandever@lsi.com>, "dolien" <david.olien@lsi.com>, "dphelps"
> > <david.phelps@lsi.com>, "henryl" <henry.lau@lsi.com>, "Jan Seidel"
> > <jan.seidel@lsi.com>, "Jobi Ariyamannil" <jobi.ariyamannil@lsi.com>,
> > "jong" <jonathan.goldick@lsi.com>, "Larry Scheer"
> > <larry.scheer@lsi.com>, "Maxim Kozlovsky" <maxim.kozlovsky@lsi.com>,
> > "Rendell Fong" <rendell.fong@lsi.com>, "rupendran"
> > <ram.upendran@lsi.com>, "Svati Chandra" <Svati.Chandra@lsi.com>,
> > "Siva Kodiganti" <siva.kodiganti@lsi.com>, "srevitch"
> > <sam.revitch@lsi.com>, "uketinen" <usha.ketineni@lsi.com>
> > Message-ID: <WEBMAILkMwBKMsa7A9g0010c1e0@mail.onstor.com> Subject:
> > PERFORCE change 34273 for review MIME-Version: 1.0 Content-Type:
> > text/plain
> >
