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

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?
akalichAsked:
Who is Participating?
 
mdcseaConnect With a Mentor Commented:
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.
0
 
mdcseaCommented:
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!
0
 
akalichAuthor Commented:
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.
0
 
mdcseaCommented:
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.

0
 
akalichAuthor Commented:
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)?
0
All Courses

From novice to tech pro — start learning today.