Hi, I'm running Exchange 2003 on a W2K3 SBS server, up until recently we serviced 2 mail domains, with dns mx entries on the internet, both pointing to our server. We have now taken up a mail hosting service for one of these mail domains at a local ISP, and changed the DNS accordingly. Everything seems to work normally, except when we try to send a message from an existing exchange account to the new mail system. I have removed all aliases from AD to the accounts that have moved, and continually get Undeliverable messages when I try to send to these users, coming back immediately. If I restore the email alias in AD, the message comes into the users Exchange inbox. Is there an entry somewhere that tells Exchange that it is still responsible for the domain that I think I have moved, and is therefore still attempting to route the mails locally? I've removed all references to the moved mail domain from the local DNS server (I think!) as oinging the moved mail domain resolves to the correct address. We can send from the new domain to the domain remaining on our Exchange server, and connect Outlook Express to the new kmail domain from within our existing Active Directory setup, so I'm fairly certain DNS is now correct. Thanks in advance Hugh Esler

Hi, Did you also remove the domain name from the recipient policies? Leif

Hi Leif, Thanks for the reply - yes, someone else suggested this after I had posted the question, also had me check the 'masquerade as' entry in the properties for the connector, which was already empty. Still seems to be attempting to route messages internally. If I create an email alias for the old domain on my own user in AD, the mail comes straight into my local exchange box, so I'm fairly certain Exchange still thinks it is handling mail for this defunct domain. Thanks anyway, any other thoughts gratefully received Hugh