<div>
Check your Recipient Policies for the domain that is now external and remove the domain name from the Policy - this will tell Exchange to deliver mail externally, not internally.
</div>


<div>
The problem lies with your code on the server where the &quot;website&quot; is.<br />
<br />
Let's say that your domain is example.com. &nbsp;Your site is on the server example.com (@1.1.1.1), and the MX records for mail.com are pointed to 2.2.2.2.<br />
<br />
When mail is being sent from the site (@1.1.1.1), the code is checking the DNS server for the 'A' record of example.com which is returned as 1.1.1.1 and mail is sent locally. &nbsp;The code should be checking the DNS server for the 'MX' record of example.com which would be returned as 2.2.2.2 and the mail would go properly.<br />
<br />
A couple of ways to fix this:<br />
<br />
1. &nbsp;Set the 'A' record for mail.example.com to 2.2.2.2 and send the mails to user@mail.example.com (instead of user@example.com).<br />
2. &nbsp;If there are only a few users, then do the mail forwarding from user@example.com to user@mail.example.com - this will vary depending on the mail server you are using.<br />
<br />
SS
</div>


<div>
Hi,<br />
<br />
on the first comment I'm afraid I'm<br />
not using exchange. I'm using what's called Matrix Mail on a Fasthosts server.<br />
<br />
On the second I'm afraid, yes that may work using the name@mail.domain.com but it isn't just sending from the site. If I send from domain2.com on the same server it routes locally too.<br />
<br />
Any other ideas, sorry.
</div>


<div>
In a sense it is as the is hosted, but email isn't. Iv got round it now by deleting the domain and aliasing it onto another which as cleared the DNS <br />
<br />
Many thanks for your help guys
</div>


<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
Over the last few days I have spent trying to find an asnwer to my problem. I recently redirected the MX record of a customers email to a new email server, seperate from the server where the domain is, that worked, email sent from say gmail, or hotmail is delivered.<br />
<br />
The problem occurs when I try to send email from <br />
<br />
a. a domain on the same server where the site is<br />
b. from the website in code<br />
<br />
obviosuly those are being delivered locally onto the server, so I went into the DNS settings and changed the mail point to the ip of the external mail server and the MX re3cord to mail.domain.com and then done an nslookup to confirm it was correct - but the mail still goers locally and im running out of time to get it resolved, any help would be much appreciatted.<br />
<br />
Kind Regards<br />
Karl
</div>
</div>


Hi,

Over the last few days I have spent trying to find an asnwer to my problem. I recently redirected the MX record of a customers email to a new email server, seperate from the server where the domain is, that worked, email sent from say gmail, or hotmail is delivered.

The problem occurs when I try to send email from 

a. a domain on the same server where the site is
b. from the website in code

obviosuly those are being delivered locally onto the server, so I went into the DNS settings and changed the mail point to the ip of the external mail server and the MX re3cord to mail.domain.com and then done an nslookup to confirm it was correct - but the mail still goers locally and im running out of time to get it resolved, any help would be much appreciatted.

Kind Regards
Karl

Sending Emails to External Mail Server, Getting Caught Locally

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).