locked
Adding temp server, mail routing question RRS feed

  • Question

  • Current: 1 E2K10 server (server1), all roles, barracuda as smart host btw server and internet. All production mailboxes.

    Adding: 1 additional E2K10 server (server2) which will eventually be single production server (current server is a temp server during hdw rebuild). a few test mailboxes only.

    Situation: mail from server1 is routing through server2 and this causes problems when I perform maintenance.

    Desired: Route all in/outbound mail from each server independently. Allow reboots/changes on server2 without affecting mail flow.

    How do I isolate this routing? We have one send connector with both severs as source servers. Should I put up a second send server and only source one server per connector? Or is there a better method?

    Thanks!

    Thursday, August 2, 2012 2:06 PM

Answers

  • Hi, Charlie!  It's been a long time.

    The only way I can think of to avoid any kind of disruption is to remove server1 from all send connectors some time before performing maintenance on server1, and the same for server2.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."


    • Edited by Ed CrowleyMVP Friday, August 3, 2012 4:08 PM
    • Marked as answer by Castinlu Saturday, August 11, 2012 1:47 AM
    Friday, August 3, 2012 4:07 PM

All replies

  • Recheck your send connector(s) and make sure both servers are in the SourceTransportServer property.  This setting should configure both servers to send directly to the Barracuda.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."


    • Edited by Ed CrowleyMVP Thursday, August 2, 2012 3:41 PM Clarification
    • Proposed as answer by Jamestechman Thursday, August 2, 2012 3:44 PM
    Thursday, August 2, 2012 3:40 PM
  • Hi Ed. Long time no talk. Good to see you're still plugging away with Exchange...

    My original config after installing server2 last night was the original send connector with both servers added as source servers. With that config, and all mailboxes on server 1, mail from server1 went out through server2. If I stopped transport on server 2, mail queued on server 1.

    My reading showed AD sites and connectivity parameters are used in the algorithm for determining which server in a site (both are in the same site) is used by the send connector.

    This AM after posting, I created a second send connector, put one server as source on one and the other on the second, restarted the transport service on server2, and after that mail from server1 went out through server1. But that might have been because I had affected connectivity on server2; I don't know. While I can understand the source routing into the connector, I don't understand how it determines where to go out of the connector to the smart host. I'm thinking it's the AD/Connectivity algorithm and I can't force it to use a specific server?

    We are very sensitive to mail flow disruptions for this client (this one's a long story I'll tell you sometime) so I do not want to affect production mail flow while I test/configure server2. I can't think of a great way to positively isolate mail flow, though...

    Thanks.

    Charlie Kaiser 

    Thursday, August 2, 2012 10:34 PM
  • hi,

    >>>My original config after installing server2 last night was the original send connector with both servers added as source servers.

    >>> If I stopped transport on server 2, mail queued on server 1.

    If you add the both servers in to the send connector source server, i think message will random be pass through either HUB server.  So i think may be something is wrong. HUB server will auto load balance your mail flow. Do you get some error in the queue? if you have, can you post here? Do you have any other send connector on these two servers? Please run the cmd: get-sendconnector | FL  and post the result here.

    thanks,


    CastinLu

    TechNet Community Support

    Friday, August 3, 2012 7:59 AM
  • Hi, Charlie!  It's been a long time.

    The only way I can think of to avoid any kind of disruption is to remove server1 from all send connectors some time before performing maintenance on server1, and the same for server2.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."


    • Edited by Ed CrowleyMVP Friday, August 3, 2012 4:08 PM
    • Marked as answer by Castinlu Saturday, August 11, 2012 1:47 AM
    Friday, August 3, 2012 4:07 PM