How to make Exchange 2003 non-authoritive

Posted by Romski on Server Fault See other posts from Server Fault or by Romski
Published on 2012-12-17T01:44:43Z Indexed on 2012/12/17 5:04 UTC
Read the original article Hit count: 407

Filed under:

Background

We are a small company with an internally hosted Exchange 2003. It receives email for 2 domains (the company was renamed a few years back). For the sake of argument, the domains are:

  • oldname.com
  • newname.com

We have moved newname.com to a hosted exchange service, and our DNS record is correctly routing emails. Our internal server still receives email for oldname.com, although we have asked our hosting company to accept emails for that domain.

Problem

My problem is that emails generated internally from monitoring software, printer, etc. are being caught by our (defunct) internal server and being delivered to the old mailboxes.

I believe that what is happening is that our internal exchange server considers itself to be the authoritive server for newname.com. I think it must be looking in active directory for a mailbox and delivering it internally without ever going outside.

Attempt to fix

I started to follow the article here: http://support.microsoft.com/kb/321721. I removed the SMTP recipient policy for newname.com, and added a dummy address and made it primary. I also answered yes for updating the associated emails. I then restarted the Microsoft Exchange Routing System and SMTP, but emails are still being routed internally.

Is there a way to force the exchange server to route all emails for the domain newname.com to the new hosted service?

© Server Fault or respective owner

Related posts about exchange-2003