Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've had an issue lately where one of our branch offices with around 60 employees will end up sending a 10MB email to 20 users at that facility.

The problem is that the email server itself is located at HQ across a 1.5Mbps MPLS circuit.

So what happens is the Exchange server at HQ has to send a 10MB email to 20 different users across that pipe to their cached OST file (unless I'm missing something, but that's what it appears to do on the network).

This causes serious congestion on that link until all of that traffic is transmitted.

Besides putting a mailbox server at the branch office or limiting email size, are there other ways to mitigate this?

share|improve this question
Use sharepoint for file storage? – Vick Vega Jul 28 '12 at 19:47
up vote 3 down vote accepted

Your four options are:

  1. Increase bandwidth
  2. Limit attachment size
  3. Put an Exchange server at the remote site, configure a mailstore on it, and then house those users locally to that mailstore. If you try to do direct replication with your primary mailbox server, you'll crush the pipe in a similar fashion.
  4. Put a fileserver at that location and explain to users that email is not a fileshare. Seriously - if they're all local to that office, why are they emailing documents? It's an inefficient use of Exchange storage space.
share|improve this answer

Another idea, create a Transport Rule that only allows the sending of large messages until approved by a moderator, which can be done outside of office hours.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.