I have an Exchange 2007 server. Everything runs on a single server. I have two email domains running successfully for over a year on it already and have added a third. The problem is that when we test the third domain by sending an email froman external location (like gmail.com or verizon), it always gets kicked back saying that my Exchange server said: =================== Hi. This is the qmail-send program at yahoo.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <fakename@ourthirddomain.com>: public.ip.of.our.exchangeserver does not like recipient. Remote host said: 550 5.7.1 Unable to relay for <fakename@ourthirddomain.com> Giving up on public.ip.of.our.exchangeserver. ========================= This third domain is configured in DNS and Exchange just like the second domain I added. I can send email from our first or second domain to the third, or send from the third to either of the first two (that have been working for over a year), but those are all on the same server and all inside our network. When I try to send email from the third domain to any external domain, the message appears to send, but never arrives and there is no bounce-back message.I have added the third domain as an accepted domain and created a new email address policy (which I didn't seem to need for the second domain I created). I have assigned two users email addresses (primary) with this third domain and to the new email address policy.I have been fighting this for a several days now and haven't made any progress yet. I really need some help. Any help will be appreciated.

Hi,You don't have an antispam / antivirus server in front of the exchange server where the domain needs to be added as well??Leif

I have seen similar issues but on pre-SP1 servers.. What RollUp package are you running at the moment?... In my case it was resolved by deleting the Accepted Domain, removing the email policy, restarting the System Attendant, Transport and Information Store service, and then re-creating them both again... Use the following as a reference:http://technet.microsoft.com/en-us/library/aa996314.aspxIf you try the above and it still doesn't work, post the results from the following command and I will have a look: Get-AcceptedDomainLet me know how you get on... Regards, Carl FerrerCi6 Ltd - Cheshire based Exchange, AD and Virtualisation Consultants.Check out my blog: http://www.ci6.co.uk/blog/Carl Ferrer Ci6 Ltd - Cheshire Based Exchange, AD and Virtualization Consultants. Check out my blog: http://www.ci6.co.uk/blog/

yes as Leif said you need to make sure that you donot have any antispam in between such as trend micro etc. where you need to relay the messages to exchange server. mean while just run the below test for third domain and see what is the output. www.checkdns.net Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

Leif, you were on the right path. I do have an antispam / antivirus device in front of the exchange server, that I had checked (config) at least twice already, when I first added this domain, then again when it didn't work. Looks like the device was having a bad hair day and had a process hung on it. Once I finally found this problem, I restarted it and it all works. Thanks.