Hey Luke, Basically, you need to make sure that relaying for that particular domain is allowed and configured correctly. If this server is a SMTP service on a server then click on Internet Services Manager, Default SMTP Virtual Server, Domains, and look for the domains you want to receive on. Here you might find abc.com and serverA.abc.com. You could just continue to add the specific sub-domains here or you could use a wildcard character as follows: *.abc.com If you are on the Exchange server, open Exchange System Manager, Recipient Policies, Default Policy (Or whichever policy you want to configure) Under the Email Addresses Policy, you will have to add, without wildcards, the domains you are setting up to receive on. Click on New, SMTP address, type in serverB.abc.com and make sure the option "This Exchange Organization is responsible for all mail delivery to this address" is checked. Now to test, open a command prompt, & type telnet localhost 25 helo mail from: bogus@xxxxxxx rcpt to: bogus@xxxxxxxxxxxxxxx You should not get the denied relay message. Good luck. Fares -----Original Message----- From: Luke Marioni [mailto:lmarioni@xxxxxxxxxxxxx] Sent: Thursday, July 15, 2004 8:19 AM To: [ExchangeList] Subject: [exchangelist] New E2k Servers http://www.MSExchange.org/ Hey all, I originally had my users residing on serverA, so their smtp address looked thus: someone@xxxxxxx (primary) someone@xxxxxxxxxxxxxxx Now, I have moved my users onto a new server (serverB), and have setup a test user with the following addresses: someone@xxxxxxx someone@xxxxxxxxxxxxxxx However, when I try to send an external mail to this test user, I receive the following message: *Server Internal IP* does not like recipient. Remote host said: 550 5.7.1 Unable to relay for someone@xxxxxxxxxxxxxxx My e2k servers receives the mail from our q-mail gateways. Why is this?? I would really like to get the new server name in, instead of the one that is soon to be decommissioned. Cheers L