Hi, Firstly, are there any reasons, other than email, for which you need "domainb.com" configured within your network/AD? If not then my suggesion is to: - remove the recipient policy for "domainb.com" from your Exchange server. - all mail (from the internet and from the local staff) to domainb.com will go to the unix box - when you decide that your staff really need to start using the exchange server for domainb.com then set the recipient policy accordingly and change the MX records in your zonefiles and the ISP's zonefiles to point to the exchange server. For a short while email from the internet will be sent to both the unix server and the exchange server, at least until everyone's DNS records are updated. At the same time, your staff now send internally only. Just ensure that your staff collect email from the unix box (POP3). Hoep that helps, Adrian > -----Original Message----- > From: Mustafa Cicek [mailto:mbcicek@xxxxxxxxx] > Sent: Thursday, 17 February 2005 10:34 PM > To: [ExchangeList] > Subject: [exchangelist] RE: Two mail server with the same mail domain? > > http://www.MSExchange.org/ > > HI! > You are right. I try to explain why we want so. Actually we > don't, but a customer of us wants that we realize that. > > 1. We have a customer and we manage the domain domainA.com on > our Exchange Server. This customer has also the second mail > domain domainB.com which we manage also on our Exchange > Server but not have for it any MX record. > 2. Another mail server (Unix) which belongs to an Internet > Provider has MX record for the domain domainB.com. > 3. The accounts of customer for domainB.com has mailboxes on > our Exchange Server, but also on Unix mail server. > 4. The customer will migrate later his MX for domainB.com to > our server. > 5. The customer wants that his employees should send their > mails internal and external by using their Exchange > mailboxes, with the primary alias user@xxxxxxxxxxxx > 6. But the customer wants also that all mails which are sent > (external or > internal) to alias@xxxxxxxxxx should be go to the mailboxes > on Unix mail server. > > Situation: > - The employees of customer can send mail to external domains > without any problem by using their alias@xxxxxxxxxxx aliases > on our Exchange. > - The employees can also receive the mails from external > domains to their mailboxes on Unix mail server. > > PROBLEM: > - If the employees send mails internal by using our Exchange, > for example from user1@xxxxxxxxxxx to user2@xxxxxxxxxxx, the > mails will be sent to mailboxes on the Exchage Server. As I > described above the customer wants that these internal mails > should be sent also to the mailboxes on Unix mail server. > > Exchange Server acts hier absolutly correct! My questin is, > is there any "trick" that I tell Exchange Server that it > should send all internal mails to other server (Unix mail > server) without any checking?? > > That is all story! Puhh.... > It is a little bit strange story but the customer asks me > about it. Now I ask you if it is possible. > > Thanks in advance. > Mustafa > > ------------------------------------------------------ > List Archives: > http://www.webelists.com/cgi/lyris.pl?enter=exchangelist > Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp > Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ > ------------------------------------------------------ > Other Internet Software Marketing Sites: > World of Windows Networking: http://www.windowsnetworking.com > Leading Network Software Directory: http://www.serverfiles.com > No.1 ISA Server Resource Site: http://www.isaserver.org > Windows Security Resource Site: > http://www.windowsecurity.com/ Network Security Library: > http://www.secinf.net/ Windows 2000/NT Fax Solutions: > http://www.ntfaxfaq.com > ------------------------------------------------------ > You are currently subscribed to this MSEXchange.org > Discussion List as: abolzan@xxxxxxxxxxxxxxxxxxxxxxxxx To > unsubscribe visit > http://www.webelists.com/cgi/lyris.pl?enter=exchangelist > Report abuse to listadmin@xxxxxxxxxxxxxx > ============================================================ IMPORTANT - This email and any attachments is confidential. If received in error, please contact the sender and delete all copies of this email. Please note that any use, dissemination, further distribution or reproduction of this message in any form is strictly prohibited. Before opening or using attachments, check them for viruses and defects. Regardless of any loss, damage or consequence, whether caused by the negligence of the sender or not, resulting directly or indirectly from the use of any attached files, our liability is limited to resupplying any affected attachments. Any representations or opinions expressed in this email are those of the individual sender, and not necessarily those of the Capital Transport Services. ============================================================