Size limits on Corporate mail systems?

  • Thread starter Thread starter ajf
  • Start date Start date

ajf

ajf

Soldato
Joined
30 Oct 2006
Posts
3,053
Location
Worcestershire, UK
Had a bit of a discussion at work today about this, so what is the size limit of incoming and outgoing mail on your corporate mail system?

Would be interesting to see if ours is excessive or as I think, too small.

Andrew
 
Ours is the Exchange default of 10mb.

In this day and age, I think this is too small, but... it's unlikely many other organisations have lowered their limits below this, so it does prevent some mails from being bounced back to us because they're over the limit, it's easier to trap this on the sending end and instantly tell our users.
 
20MB in and out (or whatever the email formatted version of that is, I think it works out at 19.5MB).
Over that amount, you ought to use another kind of system. Email is not a file system.
 
+1

We also leave ours at the exchange default internal limit. If it's over a few MB then there's dropbox etc out there for free that you can upload big files to and email a 1KB link instead :) Then they can download it through their bandwidth not mine :P
 
If it's over a few MB then there's dropbox etc out there for free that you can upload big files to and email a 1KB link instead :) Then they can download it through their bandwidth not mine :P
I would say any half-decent CMS or even an SFTP server would be better.
Dropbox is still a pain in the rear from a security perspective, but it's up to you to look after it in your environment.
 
Hmm, seems ours is higher them at 30Mb and I am wrong:p

The issue I see with using ftp for example is we block ftp generally, as do many companies so it starts being a pain for noth sides to use day to day.

Again, Dropbox is useful but there is the security of stuff leaving without anyone knowing, and do you really want 100+ users all with their own Dropbox accounts?
 
Depends on the client and how they use email. Achitects/design related company can be up to 50MB, majority of the rest I deal with have the default and some others have 20MB.
 
I would say any half-decent CMS or even an SFTP server would be better.
Dropbox is still a pain in the rear from a security perspective, but it's up to you to look after it in your environment.

If it's a single account shared among everyone it's not so bad, security is ok if people use the "friends" options in it rather than public links. Also with the luxury of an expensive firewall I can control which bits they can use. I.e web based http upload only not the local app and sync feature.
If you were really that bothered you could set up a sync folder that had auditing on it to recored exactly what was uploaded and shared to private and public folders. You can also (with my firewall anyway) limit it to uploading .zip files with passwords on as well.

For a techie Secure FTP is better, but for end users it's not practical because they don't understand it fully. The remote site needs to have it permitted through their firewall which most dont, you still have to create and send FTP usernames and passwords to the remote users which is something IT would end up doing. If you let users do it, you're in the same boat not known who they've shared the username and password with or they won't get their heads around doing it at all...

You could use a private CMS portal which remote parties had to register an account on before being able to download stuff, but that's significant time effort and money invested, so unless it's a mission critical daily task it's not usually worth it.
 
20MB in and out (or whatever the email formatted version of that is, I think it works out at 19.5MB).
Over that amount, you ought to use another kind of system. Email is not a file system.

Amen, +1

Don't forget though, if you are using Exchange and you increase the default message sizes (above 10mb), to increase your Hub Transport Dumpster Queues to 1.5 times the size of your new message size limit.
 
Back
Top Bottom