Go Premium for a chance to win a PS4. Enter to Win


Shared Namespace situation - one side allows massive attachments, the "hosting" side does not...what to do?

Posted on 2007-11-29
Medium Priority
Last Modified: 2010-03-06
This is a follow on to an earlier question I posed. The situation is that we have a company where one part is in Asia and other other in the US. They are not connected in any way, network, vpn, nothing. But they want to share an email name space. Our side (US) uses Exchange 2003 in a front-end, back-end, DMZ setup. The have a web based email. Everything works fine except that since they do not use a network with files servers, they share files via email!  ARRGGHHH.  And they expect to continue to accept 50MB files inbound. I thought (a kind hall of famer here agreed) that since we are only routing their mail, the size limit wouldn't be a problem. But it is. Our 10MB limit stops anything larger even when when it's being routed to Asia and doesn't go to our mailboxes here. They want to go live on Monday so this is really urgent. (Isn't everything??) :-)  I'm thinking of trying this:  Up the limit on the front-end server to accompdate them -- there are no mailboxes on that server -- and see if that fixes it.  Anyone had any experience with this?
Question by:akalich
  • 3
  • 2

Expert Comment

ID: 20375223
How is the 10Mb limit being imposed?  If it's set on the SMTP Virtual Server handling mail for this domain, the limit will be enforced on all traffic, regardless of its ultimate destination.

Your idea of raising the limit on the front end (if that's where the limit is imposed) should work although it depends on where the Asia group's mailboxes actually reside and whether the mail ever passes to your internal server with more restrictive limits.

Not being privy to the original question - there may be something I'm missing about your arrangement.

Good Luck!

Author Comment

ID: 20377703
The 10MB limit is on the Exchange Application. Asia's mailboxes reside there, not here so they should never hit our backend server.  But your point about the SMTP Virtual server is a good one and I will check to be sure there isn't something there as well.

Expert Comment

ID: 20377808
By default, I don't believe any restrictions are set in the SMTP connector so that's probably not the issue unless you set them.  You haven't said where your 10Mb limit is being enforced.

If you are enforcing limits at the Routing Group level (which you may be) and it's a routing group for the shared namespace through which the Asia mail must pass, you'll have a problem.


Author Comment

ID: 20379376
Actually there WAS a restriction set in the SMTP connector so I upped that to 50MB and increased the sending restriction to 20MB.  No limits were on the routing groups. I'm awaiting confirmation of a success in a large attachment message to Asia. But so far, no bounceback or error. Do you suggest that I get rid of the restiction completely (on the front end server only)?

Accepted Solution

mdcsea earned 2000 total points
ID: 20379453
Eliminating all restrictions is like letting go of control of your server but in this case, on the front end it may be necessary.

Still, you may want to maintain some kind of restrictions unless you have pretty much unlimited bandwidth to that SMTP server through which all mail, including the smaller mail objects for the US Team, will route.

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
Steps to fix “Unable to mount database. (hr=0x80004005, ec=1108)”.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video discusses moving either the default database or any database to a new volume.
Suggested Courses

782 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question