<?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: Of Qmail, Zombies and qmail-remote timeout issues.</title>
	<atom:link href="http://www.computersolutions.cn/blog/2010/02/of-qmail-zombies-and-qmail-remote-timeout-issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.computersolutions.cn/blog/2010/02/of-qmail-zombies-and-qmail-remote-timeout-issues/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=of-qmail-zombies-and-qmail-remote-timeout-issues</link>
	<description>Whats happening at Computer Solutions</description>
	<lastBuildDate>Thu, 02 Feb 2012 15:38:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Lawrence Sheed</title>
		<link>http://www.computersolutions.cn/blog/2010/02/of-qmail-zombies-and-qmail-remote-timeout-issues/comment-page-1/#comment-2121</link>
		<dc:creator>Lawrence Sheed</dc:creator>
		<pubDate>Tue, 05 Apr 2011 02:22:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.computersolutions.cn/blog/?p=355#comment-2121</guid>
		<description>Yahoo does tarpitting - so that may be the issue.

I&#039;d suggest also install some kind of local dns caching lookup in your computer, especially if its a mail server.
I used to use djb&#039;s dnscache, but now I prefer unbound.  Easy to install, and just works.

It also has DNSSec, so it checks that the records do come from the appropriate server.  

I can&#039;t use the DNSSec stuff in China, as China&#039;s DNS internally does not compute!  
They do a few naughty things to the DNS records, plus they own the root servers, and sign things they shouldn&#039;t.

In China I get to find out about lots of &quot;interesting&quot; issues that you don&#039;t see oversea&#039;s hehe.</description>
		<content:encoded><![CDATA[<p>Yahoo does tarpitting &#8211; so that may be the issue.</p>
<p>I&#8217;d suggest also install some kind of local dns caching lookup in your computer, especially if its a mail server.<br />
I used to use djb&#8217;s dnscache, but now I prefer unbound.  Easy to install, and just works.</p>
<p>It also has DNSSec, so it checks that the records do come from the appropriate server.  </p>
<p>I can&#8217;t use the DNSSec stuff in China, as China&#8217;s DNS internally does not compute!<br />
They do a few naughty things to the DNS records, plus they own the root servers, and sign things they shouldn&#8217;t.</p>
<p>In China I get to find out about lots of &#8220;interesting&#8221; issues that you don&#8217;t see oversea&#8217;s hehe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://www.computersolutions.cn/blog/2010/02/of-qmail-zombies-and-qmail-remote-timeout-issues/comment-page-1/#comment-2117</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Mon, 04 Apr 2011 14:43:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.computersolutions.cn/blog/?p=355#comment-2117</guid>
		<description>This script worked great for me on a Centos 5.5 box.  I actually have a weird issue where my yahoo.com emails sometime get stuck during the DNS lookup.  This will go on for days.  With your script, not only did the qmail-remote processes not only clear out, but I noticed that qmail was smart enough to try the messages one more time and actually deliver and/or bounce them!

Very happy with this.  I might suggest a --quiet option for those who are not comfortable redirecting to null in their crontab scripts.

Keep up the good work.  It&#039;s always nice to know somebody has dealt with the same problems you have, and you&#039;re not crazy.</description>
		<content:encoded><![CDATA[<p>This script worked great for me on a Centos 5.5 box.  I actually have a weird issue where my yahoo.com emails sometime get stuck during the DNS lookup.  This will go on for days.  With your script, not only did the qmail-remote processes not only clear out, but I noticed that qmail was smart enough to try the messages one more time and actually deliver and/or bounce them!</p>
<p>Very happy with this.  I might suggest a &#8211;quiet option for those who are not comfortable redirecting to null in their crontab scripts.</p>
<p>Keep up the good work.  It&#8217;s always nice to know somebody has dealt with the same problems you have, and you&#8217;re not crazy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lawrence Sheed</title>
		<link>http://www.computersolutions.cn/blog/2010/02/of-qmail-zombies-and-qmail-remote-timeout-issues/comment-page-1/#comment-703</link>
		<dc:creator>Lawrence Sheed</dc:creator>
		<pubDate>Thu, 18 Mar 2010 12:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.computersolutions.cn/blog/?p=355#comment-703</guid>
		<description>Suggest do:

man kill

And see what CentOS 5.2 wants for parameters. Amend script accordly (and let me know, so I can update it to cater for that).</description>
		<content:encoded><![CDATA[<p>Suggest do:</p>
<p>man kill</p>
<p>And see what CentOS 5.2 wants for parameters. Amend script accordly (and let me know, so I can update it to cater for that).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ricardo</title>
		<link>http://www.computersolutions.cn/blog/2010/02/of-qmail-zombies-and-qmail-remote-timeout-issues/comment-page-1/#comment-702</link>
		<dc:creator>Ricardo</dc:creator>
		<pubDate>Thu, 18 Mar 2010 11:29:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.computersolutions.cn/blog/?p=355#comment-702</guid>
		<description>Hi!

Great script, I think I will use it... but kill -9 PID does not seem to kill the defunct process... Any help? It&#039;s a CentOS 5.2...</description>
		<content:encoded><![CDATA[<p>Hi!</p>
<p>Great script, I think I will use it&#8230; but kill -9 PID does not seem to kill the defunct process&#8230; Any help? It&#8217;s a CentOS 5.2&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

