<div>
<div class="content wysiwyg-content">
Currently running POSTFIX (lots of boxes doing various tasks). &nbsp;Moving to Exchange without an EDGE TRANSPORT server, just MAILBOX, CAS, and HUB. &nbsp;Keeping Postfix on the perimeter and passing to Exchange.<br />
<br />
New Exchange domain (xyz.abc.com) doesn't match existing (non-exchange) mail domain (abc.com). &nbsp;How do I slowly migrate abc.com people to xyz.abc.com and maintain BOTH systems? And still make everything look like abc.com? &nbsp; TO make matters harder, our current POSTFIX system handles 3 different e-mail domains and merging all into Exchange.
</div>
</div>


Currently running POSTFIX (lots of boxes doing various tasks).  Moving to Exchange without an EDGE TRANSPORT server, just MAILBOX, CAS, and HUB.  Keeping Postfix on the perimeter and passing to Exchange.

New Exchange domain (xyz.abc.com) doesn't match existing (non-exchange) mail domain (abc.com).  How do I slowly migrate abc.com people to xyz.abc.com and maintain BOTH systems? And still make everything look like abc.com?   TO make matters harder, our current POSTFIX system handles 3 different e-mail domains and merging all into Exchange.

Configure Exchange with existing SMTP Router

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.

Email Protocols

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.