• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 323
  • Last Modified:

Best Exchange configuration for colocation

I manage a network running SBS2003. I have 25 clients using outlook 2003 with Exchange. So far, the network has been relatively simple, with one Exchange server on a single domain managing all mail. We are in the process of collocating some of our internet facing services (web server, SQL) to a data center that will provide better reliability and sustainability. Most of our internal resources will remain at our main office where they are now. We have a few addresses used exclusively by our web services that deliver e-mail based products and notifications. I'm thinking of adding another Exchange server to our network in order to host these addresses at the data center so that they can be afforded the same benefits as our other services there. Since I've never dealt with a multi-Exchange environment, I'm not really sure about the best configuration for my purposes. I've looked into setting up routing groups, but will I be able to designate what server routes specific e-mail addresses in such a configuration? I've also thought about simply moving our single Exchange server to the data center, but I would prefer not to have all of our clients connecting through that link. It will be secure but it's going to increase the overhead bandwidth significantly. Any configuration suggestions?
0
petereader
Asked:
petereader
1 Solution
 
ATIGCommented:
I guess my question would be what does the applications do, send notification to your internal users or ?

You could simpley install an SMTP box (IIS -> SMtp) to relay everything from the datacenter to you local server.  Which seems the lighted way to configure items but need more info about your setup.
0
 
petereaderAuthor Commented:
Thank you for the response ATIG,

the app sends notifications to customers when they purchase products from our websites, as well as reports to customers who purchased certain products (the report is in essence the product itself). So these would be emails going to the outside world.

Let me see if I understand you correctly: you suggest placing an incoming mail server (our mx records would point to it) at the datacenter (doesn't have to be an Exchange server), while our local exchange server POPs mail from it, our internal outlook clients connect to it, and perhaps even do the outgoing mail?

Is that correct? Perhaps the datacenter mail server could also do outgoing mail and that would provide the reduncy we are looking for?
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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