<?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: (Fix) Postfix: Recipient address rejected: Domain not found</title>
	<atom:link href="http://www.fencepost.net/2010/03/fix-postfix-recipient-address-rejected-domain-not-found/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fencepost.net/2010/03/fix-postfix-recipient-address-rejected-domain-not-found/</link>
	<description>Thoughts &#38; Resources on IT Consulting for Small Medical Practices</description>
	<lastBuildDate>Fri, 06 Jan 2012 06:39:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Alan</title>
		<link>http://www.fencepost.net/2010/03/fix-postfix-recipient-address-rejected-domain-not-found/comment-page-1/#comment-54815</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Sat, 10 Sep 2011 01:20:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.fencepost.net/?p=455#comment-54815</guid>
		<description>It&#039;s not clear to me exactly what you&#039;re doing, but I wonder about two things: first, is there anything that tells Postfix that the MX record for &quot;domain2.com&quot; is &quot;domain2.com&quot;? And second, is Postfix actually resolving those names using the local lookup and host file, or is it doing something different?</description>
		<content:encoded><![CDATA[<p>It&#8217;s not clear to me exactly what you&#8217;re doing, but I wonder about two things: first, is there anything that tells Postfix that the MX record for &#8220;domain2.com&#8221; is &#8220;domain2.com&#8221;? And second, is Postfix actually resolving those names using the local lookup and host file, or is it doing something different?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alex</title>
		<link>http://www.fencepost.net/2010/03/fix-postfix-recipient-address-rejected-domain-not-found/comment-page-1/#comment-54248</link>
		<dc:creator>alex</dc:creator>
		<pubDate>Wed, 07 Sep 2011 00:26:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.fencepost.net/?p=455#comment-54248</guid>
		<description>Hello,

I am hosting 3 domains in one server. For headers Return-Path,X-RocketMAILFROM and Received, sendmail puts canonical name of the server with correct usernames. For example if I send and email as users user1, these headers looks like user1@canonicalname.com. For user2 as user2@canonicalname.com
DNS looks fine and I have in my hosts file the following,
127.0.0.1  localhost localhost.localdomain canonicalname.com
***.**.***.**(server&#039;s ip) domain1.com
***.**.***.** domain2.com
***.**.***.** domain3.com

Any help appreciated.

Thanks.
Alex.</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I am hosting 3 domains in one server. For headers Return-Path,X-RocketMAILFROM and Received, sendmail puts canonical name of the server with correct usernames. For example if I send and email as users user1, these headers looks like <a href="mailto:user1@canonicalname.com">user1@canonicalname.com</a>. For user2 as <a href="mailto:user2@canonicalname.com">user2@canonicalname.com</a><br />
DNS looks fine and I have in my hosts file the following,<br />
127.0.0.1  localhost localhost.localdomain canonicalname.com<br />
***.**.***.**(server&#8217;s ip) domain1.com<br />
***.**.***.** domain2.com<br />
***.**.***.** domain3.com</p>
<p>Any help appreciated.</p>
<p>Thanks.<br />
Alex.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mohamed</title>
		<link>http://www.fencepost.net/2010/03/fix-postfix-recipient-address-rejected-domain-not-found/comment-page-1/#comment-22139</link>
		<dc:creator>Mohamed</dc:creator>
		<pubDate>Mon, 27 Dec 2010 11:11:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.fencepost.net/?p=455#comment-22139</guid>
		<description>Apologize that my answer is very late but it could help somebody else :)
Your postfix is chrooted. That&#039;s why your problem is solved when your copied ‘/etc/resolv.conf’ to ‘/var/spool/postfix/etc/resolv.conf’
Your can un-chroot it by changing the following line is /etc/postfix/master.cf
   smtp      inet  n       -       -       -       -       smtpd
  BY
   smtp      inet  n       -       n       -       -       smtpd

and you have to restart your postfix after this step</description>
		<content:encoded><![CDATA[<p>Apologize that my answer is very late but it could help somebody else :)<br />
Your postfix is chrooted. That&#8217;s why your problem is solved when your copied ‘/etc/resolv.conf’ to ‘/var/spool/postfix/etc/resolv.conf’<br />
Your can un-chroot it by changing the following line is /etc/postfix/master.cf<br />
   smtp      inet  n       &#8211;       &#8211;       &#8211;       &#8211;       smtpd<br />
  BY<br />
   smtp      inet  n       &#8211;       n       &#8211;       &#8211;       smtpd</p>
<p>and you have to restart your postfix after this step</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://www.fencepost.net/2010/03/fix-postfix-recipient-address-rejected-domain-not-found/comment-page-1/#comment-7966</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Sat, 07 Aug 2010 17:30:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.fencepost.net/?p=455#comment-7966</guid>
		<description>Thanks for sharing the fix for that - I don&#039;t remember seeing that mentioned as a problem before.</description>
		<content:encoded><![CDATA[<p>Thanks for sharing the fix for that &#8211; I don&#8217;t remember seeing that mentioned as a problem before.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oscar</title>
		<link>http://www.fencepost.net/2010/03/fix-postfix-recipient-address-rejected-domain-not-found/comment-page-1/#comment-7607</link>
		<dc:creator>Oscar</dc:creator>
		<pubDate>Mon, 02 Aug 2010 16:17:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.fencepost.net/?p=455#comment-7607</guid>
		<description>The problem was solved when I copied &#039;/etc/resolv.conf&#039; to &#039;/var/spool/postfix/etc/resolv.conf&#039;. It seems Postfix was running chrooted.</description>
		<content:encoded><![CDATA[<p>The problem was solved when I copied &#8216;/etc/resolv.conf&#8217; to &#8216;/var/spool/postfix/etc/resolv.conf&#8217;. It seems Postfix was running chrooted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oscar</title>
		<link>http://www.fencepost.net/2010/03/fix-postfix-recipient-address-rejected-domain-not-found/comment-page-1/#comment-7570</link>
		<dc:creator>Oscar</dc:creator>
		<pubDate>Mon, 02 Aug 2010 00:10:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.fencepost.net/?p=455#comment-7570</guid>
		<description>Hello,

I&#039;m having a similar problem with postfix (installed by iedMail). I can send and receive between users of the local domain, but I can&#039;t send to or receive from a external domain.

I can even resolve with host and host -x my domain and the external domais.

I googled it for a while but I haven&#039;t found anything that works for me.</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I&#8217;m having a similar problem with postfix (installed by iedMail). I can send and receive between users of the local domain, but I can&#8217;t send to or receive from a external domain.</p>
<p>I can even resolve with host and host -x my domain and the external domais.</p>
<p>I googled it for a while but I haven&#8217;t found anything that works for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://www.fencepost.net/2010/03/fix-postfix-recipient-address-rejected-domain-not-found/comment-page-1/#comment-1914</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Tue, 09 Mar 2010 16:32:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.fencepost.net/?p=455#comment-1914</guid>
		<description>A quick note based on someone searching for &quot;ESVA 2.0.5.9 download&quot; - to get ESVA 2.0.5.9, download and install the most recent available version from http://www.global-domination.org/ESVA.php (I believe it&#039;s 2.0.5.7), configure it per the instructions, then log back on as root (either at the console or by logging in via SSH and doing &quot;su -&quot; and run the command &quot;esva-update&quot; to convert from 2.0.5.7 to 2.0.5.9.</description>
		<content:encoded><![CDATA[<p>A quick note based on someone searching for &#8220;ESVA 2.0.5.9 download&#8221; &#8211; to get ESVA 2.0.5.9, download and install the most recent available version from <a href="http://www.global-domination.org/ESVA.php" rel="nofollow">http://www.global-domination.org/ESVA.php</a> (I believe it&#8217;s 2.0.5.7), configure it per the instructions, then log back on as root (either at the console or by logging in via SSH and doing &#8220;su -&#8221; and run the command &#8220;esva-update&#8221; to convert from 2.0.5.7 to 2.0.5.9.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://www.fencepost.net/2010/03/fix-postfix-recipient-address-rejected-domain-not-found/comment-page-1/#comment-1898</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Mon, 08 Mar 2010 17:30:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.fencepost.net/?p=455#comment-1898</guid>
		<description>Worth checking if you&#039;re getting a &quot;Domain not found&quot; error: at the command line of the Postfix server itself, try `host domainnotresolving.com` - if it doesn&#039;t return anything, then Postfix is going to have the same problem of not being able to confirm that the domain in question exists, so it&#039;s not going to accept the message.

If you&#039;re having this problem and you know that the domain should resolve, try to find out why it&#039;s not doing so. Just putting it in the hosts file may not do the trick - if `host`, `nslookup` or `dig` won&#039;t resolve it, Postfix won&#039;t either.</description>
		<content:encoded><![CDATA[<p>Worth checking if you&#8217;re getting a &#8220;Domain not found&#8221; error: at the command line of the Postfix server itself, try `host domainnotresolving.com` &#8211; if it doesn&#8217;t return anything, then Postfix is going to have the same problem of not being able to confirm that the domain in question exists, so it&#8217;s not going to accept the message.</p>
<p>If you&#8217;re having this problem and you know that the domain should resolve, try to find out why it&#8217;s not doing so. Just putting it in the hosts file may not do the trick &#8211; if `host`, `nslookup` or `dig` won&#8217;t resolve it, Postfix won&#8217;t either.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

