 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Exchange Publishing steps</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/exchange-publishing-steps/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-publishing-steps/</link>
	<description></description>
	<lastBuildDate>Tue, 21 May 2013 20:11:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: mraslan</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-publishing-steps/#comment-42260</link>
		<dc:creator>mraslan</dc:creator>
		<pubDate>Mon, 10 Jan 2005 04:50:56 +0000</pubDate>
		<guid isPermaLink="false">#comment-42260</guid>
		<description><![CDATA[If you have your exchange server behind an ISA server, then you should follow the steps described in the previous post, however i think that you want to know how to make mails sent to someone@yourcompany.com arrives to your mail server.

The steps are simple, you should first have a real IP connected to your exchange (or Firewall/NAT in general), and it should be fixed, meaning that it doesn&#039;t change when you restart your server, then the next step is that you must have access to the DNS system that is responsible for your domain name &quot;mycompany.com&quot; in my example, you should create in it an A record that maps for example &quot;mail.mycompany.com&quot; to the real IP you have on your server, then you creae an MX record that maps the domain &quot;mycompany.com&quot; to the the A record you created earlier, that is &quot;mail.mycompany.com&quot;.

When any mail server (i.e. Hotmail) on the internet tries to send a mail to say user1@mycompany.com, that mail server will query the DNS hirarcy for the MX record to know who is the server responsible for your domain, which will return mail.mycompany.com, then it will try to get its IP address, this is where the A record comes in, after that it will contact your mail server (or Firewall/NAT pretending to be a mail server) and sends the mail to it. Up from here, its a configuration settings in Exchange or ISA or whatever.]]></description>
		<content:encoded><![CDATA[<p>If you have your exchange server behind an ISA server, then you should follow the steps described in the previous post, however i think that you want to know how to make mails sent to <a href="mailto:someone@yourcompany.com">someone@yourcompany.com</a> arrives to your mail server.</p>
<p>The steps are simple, you should first have a real IP connected to your exchange (or Firewall/NAT in general), and it should be fixed, meaning that it doesn&#8217;t change when you restart your server, then the next step is that you must have access to the DNS system that is responsible for your domain name &#8220;mycompany.com&#8221; in my example, you should create in it an A record that maps for example &#8220;mail.mycompany.com&#8221; to the real IP you have on your server, then you creae an MX record that maps the domain &#8220;mycompany.com&#8221; to the the A record you created earlier, that is &#8220;mail.mycompany.com&#8221;.</p>
<p>When any mail server (i.e. Hotmail) on the internet tries to send a mail to say <a href="mailto:user1@mycompany.com">user1@mycompany.com</a>, that mail server will query the DNS hirarcy for the MX record to know who is the server responsible for your domain, which will return mail.mycompany.com, then it will try to get its IP address, this is where the A record comes in, after that it will contact your mail server (or Firewall/NAT pretending to be a mail server) and sends the mail to it. Up from here, its a configuration settings in Exchange or ISA or whatever.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.013 seconds using memcached
Object Caching 268/271 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-21 21:40:42 -->