Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 372
  • Last Modified:

Increasing sending/receiving sizes for e-mails to 20 MB

Some of the Company Managers are requesting to change the limit of the e-mails sent and received by our Exchange server from 10 MB to 20 MB.  I warned about performance issues, hard drive space, time to restore, mailbox sizes, etc but they want it done.  We have an Exchange 2003 Enterprise server and only have a T1.  We have FTP so any files that are above 10 MB we usually just use this method but the Managers do not want to.  I wanted to see how many people are sending/receiving 20 MB or above e-mail attachments and any issues they might have and how they overcome them?  
0
regsamp
Asked:
regsamp
  • 5
  • 4
2 Solutions
 
sullivanr6Commented:
the easiest way is to open ESM (exchang system manager), expand global settings, right click "message delivery", click the "defaults" tab, and you can change sending/receiving sizes there...

with respect to knowing who is sending these large attachments you can use the "message tracking center" to determine who's sent what to where...
0
 
sullivanr6Commented:
...one more place you can set message size;

"first admin group (you may have to enable this in the "view", "servers", "name of your server", "protocols", "smtp", right click your virtual server, then click the "messages" tab.

J
0
 
regsampAuthor Commented:
Are there Organizations with a T1 line on an Exchange 2003 server that are sending 20 MB files on average?  I would think that there would be corruption and performance issues so this is more or less a question of actual application of doing this?  
0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 
sullivanr6Commented:
...all day long. Most everyone I know is using at least a 20mb attachment rule, some in a university environment use 50mb.

are your using a standard version of exchange,  if your are then keep in mind your edb file can't grow beyond 14GB... So that would really be your only defense to not implement a larger attachment policy. If you're using an enterprise version there's no reason why you shouldnt do this.

J
0
 
i2q2Commented:
If the business requires then it must me provided. It all boils down to how much the business depends on the emails. To prevent misuse of this you could restrict certain type of music and video files and allow other types like pdf, doc etc.
0
 
regsampAuthor Commented:
We are using Exchange Enterprise 2003.  Which colleges are using 50 MB files?  The IT department of M.I.T limits their e-mail system to 10 MB.  Wouldn't 50 MB files crash an Exchange server on a T1 line?  
0
 
sullivanr6Commented:
optical sciences at UofA, College of engineering at UofA... but there not using a T1, its more like an OC12 connection :)

I find it hard to believe that MIT (on campus) uses anyting less than what my friends use at the UofA...

Crashing a T1??? you have no worries, it may hangup internet traffic while the file transfer is in progress, but the connection to your ISP will remain intact.
0
 
regsampAuthor Commented:
Well, with OC12 being the line then I can see getting that kind of size.  I was told MIT does not go over 10 MB on average according to a friend.  When I say crashing a T1, I mean hanging up the line and other issues listed below.  Are these not concerns of expanding the 10 MB limit?

"10MB is the standard limit for email attachments for good reason.
 Large attachments bloat Inboxes
Make mailbox corruption more likely,
takes longer to backup and restore,
performs poorer on slower WAN links and via VPN,
takes longer to process through delivery queues,
and is *very likely to be denied by an outside mail server who has a lower attachment size limit*.

This means it costs the company more money in disk capacity on the Exchange server, backup time, backup disk/tape capacity, downtime to restore the large InfoStore in a server loss, and bandwidth costs to transfer that email.  
Users should be using file servers (or at least workstation file shares) to transfer 10MB+ files to other employees and use an FTP site or similar service for external users."
0
 
sullivanr6Commented:
..why don't you sell your managment on this then? keep in mind, you're supporting them, but you make a good argument. However, if they NEED to send large attachement, then that's what you have to do.
0
 
regsampAuthor Commented:
True, if they need to send large attachments then might have to do it but I try to suggest that is what FTP is for.  Well, some valid points, thank you.  
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now