I have an Accellion as well. Although we didn't implement it, I believe the Accellion plugin will do the same.
On Thu, Sep 8, 2011 at 1:06 PM, Garcia-Moran, Carlos < cgarciamo...@spragueenergy.com> wrote: > Requires the BDS Outlook plugin and their API kit, then you push a setting > for Outlook and BDS that forces attachments to use the plugin when they are > larger than 30MB > > -----Original Message----- > From: Young, Darren [mailto:darren.yo...@chicagobooth.edu] > Sent: Thursday, September 08, 2011 12:58 PM > To: MS-Exchange Admin Issues > Subject: RE: Best Practices for Attachment Size Limits > > How are you implementing the AD policy that automatically sends through it? > > > -----Original Message----- > > From: Garcia-Moran, Carlos [mailto:cgarciamo...@spragueenergy.com] > > Sent: Thursday, September 08, 2011 11:56 AM > > To: MS-Exchange Admin Issues > > Subject: RE: Best Practices for Attachment Size Limits > > > > 30MB Limit with a Biscom transfer appliance and AD policies that send > > anything larger through it automatically, no mailbox limits. > > > > -----Original Message----- > > From: Young, Darren [mailto:darren.yo...@chicagobooth.edu] > > Sent: Thursday, September 08, 2011 12:40 PM > > To: MS-Exchange Admin Issues > > Subject: RE: Best Practices for Attachment Size Limits > > > > We have a 20MB attachment limit and an Accellion FTA to securely > > transfer files larger than that. Biggest problem: MIME overhead. > > People say "you said it's 20MB but it won't go through". So, we have > > to explain that depending on the type of file even an 18MB Excel might > > surpass 20MB with MIME overhead. > > > > We have 2GB mailbox quota limits. > > > > > -----Original Message----- > > > From: John Hornbuckle [mailto:john.hornbuc...@taylor.k12.fl.us] > > > Sent: Thursday, September 08, 2011 11:35 AM > > > To: MS-Exchange Admin Issues > > > Subject: Best Practices for Attachment Size Limits > > > > > > We have the standard 10-meg attachment size limit in place, and I > > > was wondering if we should reconsider. It actually doesn't seem to > > > cause much of a problem, but periodically we have a situation where > > > someone is trying to send/receive a file that's too big. > > > > > > There were two main reasons for the limit. > > > > > > One is that e-mail isn't a particularly efficient method for > > > transferring files, so big files should be transferred some other way. > > > But in this day and age, is 10 MB considered "big" anymore? > > > > > > The second reason is that big files will fill up users' mailboxes > > > quickly, and our users have 250 MB quotas. Although the fact that I > > > don't too often hear complaints about the 10 MB limit makes me think > > > users aren't sending/receiving files of that size very often > > > anyway--so the mailbox size may not be a problem if I bump up the > > attachment size limit. > > > > > > I know situations vary from enterprise to enterprise, but I'm > > > looking for general best practices and pros/cons to increasing the > limit. > > > > > > > > > > > > John Hornbuckle, MSMIS, PMP > > > MIS Department > > > Taylor County School District > > > www.taylor.k12.fl.us > > > > > > > > > --- > > > To manage subscriptions click here: http://lyris.sunbelt- > > > software.com/read/my_forums/ or send an email to > > > listmana...@lyris.sunbeltsoftware.com > > > with the body: unsubscribe exchangelist > > > > > > --- > > To manage subscriptions click here: http://lyris.sunbelt- > > software.com/read/my_forums/ or send an email to > > listmana...@lyris.sunbeltsoftware.com > > with the body: unsubscribe exchangelist > > > > > > _________________________________________________________ > > This e-mail, including attachments, contains information that is > > confidential and may be protected by attorney/client or other privileges. > > This e-mail, including attachments, constitutes non-public information > > intended to be conveyed only to the designated recipient(s). If you > > are not an intended recipient, you are hereby notified that any > > unauthorized use, dissemination, distribution or reproduction of this > > e-mail, including attachments, is strictly prohibited and may be > > unlawful. If you have received this e-mail in error, please notify me > > by e-mail reply and delete the original message and any attachments from > your system. > > _________________________________________________________ > > > > --- > > To manage subscriptions click here: http://lyris.sunbelt- > > software.com/read/my_forums/ or send an email to > > listmana...@lyris.sunbeltsoftware.com > > with the body: unsubscribe exchangelist > > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe exchangelist > > > _________________________________________________________ > This e-mail, including attachments, contains information that is > confidential and may be protected by attorney/client or other privileges. > This e-mail, including attachments, constitutes non-public information > intended to be conveyed only to the designated recipient(s). If you are not > an intended recipient, you are hereby notified that any unauthorized use, > dissemination, distribution or reproduction of this e-mail, including > attachments, is strictly prohibited and may be unlawful. If you have > received this e-mail in error, please notify me by e-mail reply and delete > the original message and any attachments from your system. > _________________________________________________________ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe exchangelist > > --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
