+ Reply to Thread
Results 1 to 6 of 6
  1. Senior Member jamesp1983's Avatar
    Join Date
    Sep 2007
    Location
    PA
    Posts
    2,465

    Certifications
    A+,Net+,S+,MCSA:S & MCSE:S 2k3,MCITP:SA/EA, CCNA:Security/RS/DC,CCNP DC, CCIE RS 51060
    #1

    Default Division email migrated to new domain?

    How is everyone doing? I am helping a local company's engineering division break off into their own company. They have an Exchange 2003 email server currently in place. The company's current domain is @companyA.com. The new company is going to be @Bengineering.com. The guys at Bengineering.com want to be able to have their emails that are sent to their old emails at companyA to be sent to their new email addresses. The catch is they don't want to involve any of CompanyA's servers. Is there any way to accomplish this? Is this impossible? I know how to configure forwarding, but this is something I've never had to do before.
    Reply With Quote Quote  

  2. SS -->
  3. Virtually in the shadows pennystrader's Avatar
    Join Date
    Oct 2008
    Location
    Central Illinois
    Posts
    154

    Certifications
    CEH,Security+, MCITP: Enterprise Messaging Administrator 2K7, MCSE:Security 2K3, VCP 3.5/4.0, ITIL 3.0
    #2

    Default Forwarding

    Well I think you answered the question yourself. I think you just have to forward it. I am more familiar with Exchange 2007 but 2003 is similar in the fact that a Windows trust should be in place so the domains are trusted and then configure forwarding on the @companyA.com to @Bengineering.com.
    Reply With Quote Quote  

  4. Senior Member jamesp1983's Avatar
    Join Date
    Sep 2007
    Location
    PA
    Posts
    2,465

    Certifications
    A+,Net+,S+,MCSA:S & MCSE:S 2k3,MCITP:SA/EA, CCNA:Security/RS/DC,CCNP DC, CCIE RS 51060
    #3
    Quote Originally Posted by pennystrader View Post
    Well I think you answered the question yourself. I think you just have to forward it. I am more familiar with Exchange 2007 but 2003 is similar in the fact that a Windows trust should be in place so the domains are trusted and then configure forwarding on the @companyA.com to @Bengineering.com.



    They just don't want to have companyA have any idea or have to be involved at all. I think its impossible.
    Reply With Quote Quote  

  5. Senior Member meadIT's Avatar
    Join Date
    Aug 2006
    Location
    Central VA
    Posts
    579

    Certifications
    Ran out of room :(
    #4
    I'm thinking it's impossible too. The public DNS will have companyA's MX record pointing to companyA's server. CompanyA's server will have to process all mail addressed to their domain.
    Reply With Quote Quote  

  6. Self-Described Huguenot blargoe's Avatar
    Join Date
    Nov 2005
    Location
    NC
    Posts
    4,098

    Certifications
    VCAP5-DCA; VCP 3/4/5/6 (DCV); EMCSA:CLARiiON; Linux+; MCSE:M 2000/2003; MCSE:S 2000/2003; MCTS:Exch2007; Security+; A+; CCNA (expired)
    #5
    Internet MX has to point to a mail exchanger (currently this is the Exchange 2003 server) which will accept all mail from the internet for companyA.com. There is no way around having a single server handling both the old company and the engineering group if they're still going to be using the companyA domain.

    However, if the engineering people are going to be in a completely separate AD forest and their accounts in the companyA domain are going to be removed, I think you could have a dedicated Exchange SMTP Server that would forward all requests for companyA.com that aren't in their directory to a specific server (the Bengineering.com server). I believe a standalone Exchange 2007 Edge Transport Server could do this for you. Then you'd have to configure Exchange in the BEngineering forest to accept mail for the CompanyA.com domain, and somehow set it up such that the BEngineering servers do not think they are authoritative for CompanyA.com (so when they try to send mail to the old company, it will be delivered to the companyA.com Exchange 2003 servers).

    IMO, not worth the trouble. Just tell them it can't be done, other than you can give them their own mailbox servers and keep that part separate. There is no way to COMPLETELY isolate it, they can't have zero traffic coming in to devices that CompanyA manages if they are still going to be using their domain name.
    Last edited by blargoe; 02-02-2010 at 11:10 AM.
    IT guy since 12/00

    Recent: 10/27/2017 - Passed Microsoft 70-410 (one exam left for MCSA 2012)
    Working on: MCSA 2012 upgrade from 2003 (to heck with 2008!!), MCSA 2016 upgrade, more Linux
    Thinking about: VCP6-CMA, AWS Solution Architect (Associate), Python, VCAP6-DCD (for completing VCIX)
    Reply With Quote Quote  

  7. Senior Member jamesp1983's Avatar
    Join Date
    Sep 2007
    Location
    PA
    Posts
    2,465

    Certifications
    A+,Net+,S+,MCSA:S & MCSE:S 2k3,MCITP:SA/EA, CCNA:Security/RS/DC,CCNP DC, CCIE RS 51060
    #6
    thanks guys!
    Reply With Quote Quote  

+ Reply to Thread

Social Networking & Bookmarks