Email Bounceback for formerly hosted domain.

IDPInc used Ask the Experts™
Okay I hope I can describe this properly.  We used to allow emails addressed to a secondary domain ( to be delivered here (  We have since transferred ownership, and also removed the MX record from that used to point to our email server.  So, anyone from the outside world can email to however, no one from can send an email to that address.  The error message is pasted below.  I have removed the from the recipient policy from Exchange System Manager and restarted IIS, but no dice.  Any ideas??  

<>: does not like recipient.
Remote host said: 550 5.7.1 Unable to relay for

Return-Path: <>
X-VirusChecked: Checked
X-StarScan-Version: 6.1.3;,-,
X-Originating-IP: []
X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE
Received: (qmail 7694 invoked from network); 21 Oct 2009 20:32:21 -0000
Received: from (HELO (
  by with RC4-SHA encrypted SMTP; 21 Oct 2009 20:32:21 -0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
Subject: test
Date: Wed, 21 Oct 2009 16:32:20 -0400
Thread-Topic: test
Thread-Index: AcpSjZbLaLEpjrjGSTOY/76i1UvrPQ==
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Who is Is it your Exchange? Is so, then try to look in the ESM\AdminGroups\FirstAdminGroup\Servers\<Server>\Protocols\SMTP\VirtualServer\Properties\Access\Relay. If not, please provide some info about message flow.


It is the external address of our email server.  I checked the Relay properties as you suggested, and there's a list of internal addresses.  The addresses are for our copiers which have a scan and mail function.  

According to log you are trying to connect from external network to external ip of your Exchange and trying to send mail to It'll not work if you deleted all info about FORMERHOSTEDDOMAIN from your Exchange server. If you moved FORMERHOSTEDDOMAIN to the different server you need to modify MX records on FORMERHOSTEDDOMAIN to point to correct mail server for FORMERHOSTEDDOMAIN.
Try to check MX records for FORMERHOSTEDDOMAIN like:

nslookup -type=MX

If you still see in command output, something wrong with your cache or you registrar for didn't update MX records. Try to check MX records from different network, different ISP or different DNS server. If you see everywhere - something worng with registrar, if only on your network and your DNS - something wrong with caching or your DNS server.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!


The nslookup returned appropriate external MX records for the new host of that email domain.
Did you try to run nslookup to request MX records for old domain from your Exchange server?
Just in case try to run from your Exchange server:
ipconfig /flushdns
and run nslookup again.


The issue ended up being with the spam scrubbing service which was routing our internal mail.  I've removed the connector and everything is working great.  

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial