Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
Exchange 2007 Server - Separate Outbound Traffic

Unanswered Exchange 2007 Server - Separate Outbound Traffic

  • Friday, November 30, 2012 10:37 PM
     
     
    Sign In to Vote
    0

    Hey Folks,

    We are in a bit of a pickle as a bulk email sender. We are a small but growing financial institution that needs to communicate to our customers regarding account transactions, notices, statements, etc.

    We have had pretty smooth sailing with the exception of yahoo.com addresses. We've followed their guidelines, implemented DomainKeys/DKIM, etc., but they seem to be blocking a lot of our email the last month or so. Have opened a ticket with them to have us whitelisted, but to no avail thus far.

    The final step we'd like to take is to use an independent mailserver for sending bulk messages like this rather than normal email. To accomplish this, we've spun-up a Server 2008 R2 VM and have a 2nd Exchange 2007 (sp3 rollup5) server on it.

    This second server has already introduced itself to our production server. However, we have some things we'd like to get some answers about before proceeding:

    1. Is it possible to set the new server up to send via its own hub transport rather than go thru the cluster (and attached smart host)?

    2. How does one accomplish a send connector to a specific domain - ie. we want all mail bound to yahoo.com addresses to route thru the secondary host (different public IP, etc.).

    Any insights would be most appreciated... thanks!

    Tom W.

    JTW

     

All Replies

  • Sunday, December 02, 2012 8:36 PM
     
     
    Sign In to Vote
    0
    On Fri, 30 Nov 2012 22:37:54 +0000, MWave6 wrote:
     
    >We are in a bit of a pickle as a bulk email sender. We are a small but growing financial institution that needs to communicate to our customers regarding account transactions, notices, statements, etc.
    >
    >We have had pretty smooth sailing with the exception of yahoo.com addresses. We've followed their guidelines, implemented DomainKeys/DKIM, etc., but they seem to be blocking a lot of our email the last month or so. Have opened a ticket with them to have us whitelisted, but to no avail thus far.
    >
    >The final step we'd like to take is to use an independent mailserver for sending bulk messages like this rather than normal email. To accomplish this, we've spun-up a Server 2008 R2 VM and have a 2nd Exchange 2007 (sp3 rollup5) server on it.
    >
    >This second server has already introduced itself to our production server. However, we have some things we'd like to get some answers about before proceeding:
    >
    >
    >
    >1. Is it possible to set the new server up to send via its own hub transport rather than go thru the cluster (and attached smart host)?
     
    Sure. Assuming the server has the HT role installed, create a new Send
    Connector and nominate just the new server as the "Source Server".
     
    >2. How does one accomplish a send connector to a specific domain - ie. we want all mail bound to yahoo.com addresses to route thru the secondary host (different public IP, etc.).
     
    Put "yahoo.com" into the "Address Space" tab on that new Send
    Connector (don't include the normal "*" address space).
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     
    --- Rich Matheisen MCSE+I, Exchange MVP
     
  • Monday, December 03, 2012 10:55 PM
     
     
    Sign In to Vote
    0

    Thanks Rich,

    We went down this road with the send connector and all went well. Also gave a higher cost to the "*" connector.

    Can you also weigh in as to how one would send from certain mailboxes and route outbound thru a particular mailserver? We are now wanting to refine our message routing in this manner as well.

    TIA, Tom W.

    JTW

     
  • Tuesday, December 04, 2012 2:37 AM
     
     
    Sign In to Vote
    0
    On Mon, 3 Dec 2012 22:55:16 +0000, MWave6 wrote:
     
    >We went down this road with the send connector and all went well. Also gave a higher cost to the "*" connector.
     
    Don't worry about the "cost" associated with the address space. The
    use of a specific domain is always going to override that.
     
    >Can you also weigh in as to how one would send from certain mailboxes and route outbound thru a particular mailserver? We are now wanting to refine our message routing in this manner as well.
     
    For that you'll need something call "sender based routing". Exchange
    only comes with "recipient based routing".
     
    You can "roll you own" routing agent:
    http://blogs.technet.com/b/appssrv/archive/2009/08/26/how-to-control-routing-from-your-own-routing-agent.aspx
     
    Or you can buy one:
    http://www.messageconcept.net/en/products/exsbr/
    http://ivasoft.com/routebysender.shtml
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     
    --- Rich Matheisen MCSE+I, Exchange MVP
     
  • Tuesday, December 04, 2012 6:01 PM
     
     
    Sign In to Vote
    0

    Rich,

    Thanks for your help. I think we found a solution to the question above but inline with that it has created at least one more.

    We essentailly seperated the two mail servers so that any mailbox that sits on server B will use the new public IP and go out its own connector while server A will continue to work as normal etc.

    The new question is if we move our "marketing" mail box over will the aliases associated with that box continue to work or do they have to be re-created?

    Thanks!

     
  • Wednesday, December 05, 2012 3:12 AM
     
     
    Sign In to Vote
    0
    On Tue, 4 Dec 2012 18:01:46 +0000, uk2us88 wrote:
     
    >Thanks for your help. I think we found a solution to the question above but inline with that it has created at least one more.
    >
    >We essentailly seperated the two mail servers so that any mailbox that sits on server B will use the new public IP and go out its own connector while server A will continue to work as normal etc.
     
    Are both servers in the same AD foret? If so, are they in the same AD
    site? If so, I don't know what you did to "separate" them. It may be
    that you think you've made things work but if you're depending on a
    multi-role server to always use the HT role that's on the same machine
    as the MBX role you're building a house on sand.
     
    >The new question is if we move our "marketing" mail box over will the aliases associated with that box continue to work or do they have to be re-created?
     
    If they just moving to a different server in the same Exchange
    organization you don't have to do anything except move the mailbox.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     
    --- Rich Matheisen MCSE+I, Exchange MVP