<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Comments on article "Qmail tips"</title>
<link>http://home.zyrianes.net/blog/Articles/145/</link>
<description>&lt;div class="contents topic" id="contents"&gt;
&lt;p class="topic-title"&gt;&lt;a name="contents"&gt;Contents&lt;/a&gt;&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;&lt;a class="reference" href="#repair-the-queue" id="id1" name="id1"&gt;Repair the queue&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="reference" href="#setup-as-mx-secondary-for-a-domain" id="id2" name="id2"&gt;Setup as MX secondary for a domain&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="reference" href="#watch-qmail-logs-with-date-time" id="id3" name="id3"&gt;Watch qmail logs with date/time&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;p&gt;This short article enumerates tips for qmail (a reminder for me):&lt;/p&gt;
&lt;div class="section" id="repair-the-queue"&gt;
&lt;h1&gt;&lt;a class="toc-backref" href="#id1" name="repair-the-queue"&gt;Repair the queue&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;The queue is located here : /var/qmail/queue/ , you can repair it with queue_repair ( &lt;a class="reference" href="http://www.qcc.ca/~charlesc/software/queue_repair/"&gt;http://www.qcc.ca/~charlesc/software/queue_repair/&lt;/a&gt; ).&lt;/p&gt;
&lt;p&gt;command:&lt;/p&gt;
&lt;pre class="literal-block"&gt;
./queue_repair.py -c -s 23 --no-bigtodo /var/qmail
&lt;/pre&gt;
&lt;p&gt;see:  &lt;a class="reference" href="http://www.qcc.ca/~charlesc/software/queue_repair/docs.html#docs"&gt;http://www.qcc.ca/~charlesc/software/queue_repair/docs.html#docs&lt;/a&gt;
-c create and repair
-s 23 number of split directories
--no-bigtodo if your qmail don't use the qmail big-todo patch&lt;/p&gt;
&lt;/div&gt;
&lt;div class="section" id="setup-as-mx-secondary-for-a-domain"&gt;
&lt;h1&gt;&lt;a class="toc-backref" href="#id2" name="setup-as-mx-secondary-for-a-domain"&gt;Setup as MX secondary for a domain&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;It's quite simple, add the domain in the /var/qmail/control/rcpthosts of each recorded MX secondary. And, restarts qmail (just kill -HUP).&lt;/p&gt;
&lt;p&gt;exemple:&lt;/p&gt;
&lt;pre class="literal-block"&gt;
server1.domain1.tld has:
MX   10 server1.domain1.tld
MX   20 server2.domain2.tld

on server2.domain2.tld,
in /var/qmail/control/rcpthosts file add line:
server1.domain1.tld 
&lt;/pre&gt;
&lt;/div&gt;
&lt;div class="section" id="watch-qmail-logs-with-date-time"&gt;
&lt;h1&gt;&lt;a class="toc-backref" href="#id3" name="watch-qmail-logs-with-date-time"&gt;Watch qmail logs with date/time&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Qmail use a special log format for the date and the time (maybe seconds number since 1/1/1970 ). tai64nlocal shows user fiendly date/time.&lt;/p&gt;
&lt;p&gt;exemple:&lt;/p&gt;
&lt;pre class="literal-block"&gt;
# tail -f /var/log/qmail/current  | tai64nlocal
2005-02-10 14:07:55.565508500 delivery 3973: success: did_1+0+0/
2005-02-10 14:07:55.565510500 status: local 0/10 remote 0/20
2005-02-10 14:07:55.565511500 end msg 52055
2005-02-10 14:27:01.610629500 new msg 52055
&lt;/pre&gt;
&lt;/div&gt;
</description>
<language>en</language>
<copyright>The contents of this blog are available for non-commercial use only.</copyright>
<generator>Alinea http://pythonfr.org/alinea/</generator>


<item>
<title>Ludo on Qmail tips</title>
<link>http://home.zyrianes.net/blog/Comments/16/</link>
<guid isPermaLink="true">http://home.zyrianes.net/blog/Comments/16/</guid>
<description><![CDATA[
Subliminal response, qmail version don't change since few years, because no holes was found...
]]></description>
<dc:creator>Ludo</dc:creator>
<dc:date>2004-10-29T15:27:27Z</dc:date>
</item>

<item>
<title>Jkx on Qmail tips</title>
<link>http://home.zyrianes.net/blog/Comments/15/</link>
<guid isPermaLink="true">http://home.zyrianes.net/blog/Comments/15/</guid>
<description><![CDATA[
Subliminal message, postfix handle MX dns lookup without any tricks :)
]]></description>
<dc:creator>Jkx</dc:creator>
<dc:date>2004-10-20T21:06:05Z</dc:date>
</item>


</channel>
</rss>