Announcement

Collapse
No announcement yet.

Centralized Exchange Model

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Centralized Exchange Model

    From scratch - I have a requirement to centralize all my user's mail to one (active/passive cluster) Microsoft Exchange 2003 Server in the United States.

    The second requirement is that all mail (headers etc.) must appear to be sent from their originating countries.

    For example, mail sent from a user in South America must appear to come from a server in South America. All mail originating from the United States must appear to have been sent from the United States and so on.

    Is this possible? If so, can anyone point me in the right direction?

    Thank you for your time in advance!!!

  • #2
    Re: Centralized Exchange Model

    What you want to do is not going to be possible easily.
    Exchange doesn't route based on the sender, it routes based on the recipient. You would have to setup an SMTP connector for each location, with a server in each location, and specific domains listed on each connector. So while you could have .co.uk on the UK connector, if the UK company has a .com domain then you are going to be out of luck unless you know in advance.

    Why the requirement for the email to come out of a server located in that country? Most servers and recipients will not care where the email comes from.

    Where the email originates from doesn't really matter unless you are sending messages that could be seen as spam and are trying to get around country blocks.

    The most common method of having country specific domains is to use something like @country.domain.com so user @ us.domain.com, user @ de.domain.com etc
    All of the email comes out of the same server, but it looks like a country specific domain. Although in most cases the user also has user @ domain.com email address.

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: Centralized Exchange Model

      Simon thanks so much for the information!!!

      Here is what we need to accomplish in summary:

      Can Exchange 2003 Route OUTBOUND email based on the FROM address?
      xyz.com to smarthost1
      abc.com to smarthost2

      So one question I have about your response is:

      1. Does the SMTP Connector have to connect to another Exchange Server in each location or.. (This would NOT be financially feasible for us.)

      2. Can we use a non-exchange (Microsoft SMTP Service) to send out the emails at the remote location? (This would be financially feasible for us.)

      fyi... we are a financial services firm and want the email to appear only from where it is actually originating. So it is not for malicious reasons but more for autonomy between the 2 companies that make up our organization. We are the consulting arm of the organization and merely want to centralize the entire companies mail for ease of backup/management. This is just to avoid unnecessary confusion.

      Comment


      • #4
        Re: Centralized Exchange Model

        Here is a response I received from a different forum:

        Anybody agree/disagree?
        I believe so, however I think you need to engineer a transport event sink to meet this scenario (meaning there's no UI to configure this).



        This article delves into how to use C# to make an agent:



        http://support.microsoft.com/kb/894286



        Here's E2K3's transport events:



        http://msdn2.microsoft.com/en-us/library/ms528385.aspx



        I believe the IDNSResolverInterface can be utilized to override where a message is going to go, so you can set a smarthost value on the fly.



        I'd post to the extensibility forum to see if they can elaborate further...

        Comment


        • #5
          Re: Centralized Exchange Model

          A transport sink is about the only way that it could be done. It would mean something specific to you being written.

          However you still have the problem that you want the email to appear to come from a server in that country. That will mean you must have a presence in that country, a server of some kind.

          While I appreciate why you want to do this, the reasons you have given would not be enough for me to want to go through the hassle of trying to get it setup. I have worked with companies where all email goes out the California, doesn't matter if you are in London, Paris, Sydney or Singapore. Up to a few years ago all AOL traffic came out of the USA, so where the traffic originates from doesn't really matter.

          I actually think that the simplification is being over complicated by this desire. It makes no difference technically, commercially or financially where the email appears to come from.

          Simon.
          --
          Simon Butler
          Exchange MVP

          Blog: http://blog.sembee.co.uk/
          More Exchange Content: http://exchange.sembee.info/
          Exchange Resources List: http://exbpa.com/
          In the UK? Hire me: http://www.sembee.co.uk/

          Sembee is a registered trademark, used here with permission.

          Comment


          • #6
            Re: Centralized Exchange Model

            Simon,

            Thank you for your reply again.

            We do have non-exchange SMTP servers ready to go in each location.

            We are not talking about a bunch of locations at all (in fact, just two)

            If it is only available via programming then we are on the same page (It's not worth the hassle)

            However, at this point, I simply want to know if it can be configured via UI (for my sanity's sake)

            I have found others asking this question (on other forums) and I wouldn't mind ending their search as well.

            I have found other mail systems can easily accomplish this conguration, by the way.

            Comment


            • #7
              Re: Centralized Exchange Model

              As I wrote in my first post - Exchange doesn't and cannot route email based on the sender, but the recipient. What other email servers can and cannot do isn't really a concern - if you are committed to Exchange then you have to live within what Exchange can do.

              The most it can do is route email out via a certain path using routing groups - but that is a per SERVER, not per user.

              Simon.
              --
              Simon Butler
              Exchange MVP

              Blog: http://blog.sembee.co.uk/
              More Exchange Content: http://exchange.sembee.info/
              Exchange Resources List: http://exbpa.com/
              In the UK? Hire me: http://www.sembee.co.uk/

              Sembee is a registered trademark, used here with permission.

              Comment


              • #8
                Re: Centralized Exchange Model

                OK here is how to accomplish this:

                ***IMPORTANT*****
                DO THIS AT YOUR OWN RISK - test in a lab first as we have done.
                This will not work for multiple domains for a single user.

                for example:

                This WILL NOT route out a specific connector:
                [email protected]
                [email protected]

                but

                This WILL route out a specific connector:
                [email protected]
                [email protected]

                So in this scenerio I want [email protected] to deliver out to the internet as usual and I want [email protected] to go to a special SMARTHOST

                1. Add (CheckConnectorRestrictions and set it to 1) DWORD registry entry to this key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Resvc\Parameters

                *note: we rebooted after this step

                2. Create Two (or more) SMTP Connectors (ADDRESS SPACE on both set to *, same cost is fine)

                3. On the SMTP connector (that will handle normal internet mail) click the "Delivery Restrictions" tab and set to:

                "By default, messages from everyone are: ACCEPTED"
                also click "ADD" under "Reject messages from:" and add [email protected]

                4. On the SMTP connector (that will handle mail you would like to forward to a special SMARTHOST) click the "Delivery Restrictions" tab and set to:

                "By default, messages from everyone are: REJECTED"
                also click "ADD" under "Accept messages from:" and add [email protected]

                5. Issue IISRESET from a command prompt

                Comment

                Working...
                X