[gentoo-doc-cvs] cvs commit: home-router-howto.xml qmail-howto.xml

[Josh Saddler]

nightmorph    07/03/07 21:30:18

  Modified:             home-router-howto.xml qmail-howto.xml
  Log:
  qmail --> netqmail migration, bug 165874

Revision  Changes    Path
1.56                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.56&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.56&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.55&r2=1.56

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -r1.55 -r1.56
--- home-router-howto.xml	28 Jan 2007 22:36:37 -0000	1.55
+++ home-router-howto.xml	7 Mar 2007 21:30:18 -0000	1.56
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.55 2007/01/28 22:36:37 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.56 2007/03/07 21:30:18 nightmorph Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.34</version>
-<date>2007-01-28</date>
+<version>1.35</version>
+<date>2007-03-07</date>
 
 <chapter>
 <title>Introduction</title>
@@ -793,9 +793,9 @@
 </p>
 
 <pre caption="Setting up SMTP">
-# <i>emerge qmail</i>
+# <i>emerge netqmail</i>
 <comment>make sure the output of `hostname` is correct</comment>
-# <i>ebuild /var/db/pkg/*-*/qmail-1.03-r*/*.ebuild config</i>
+# <i>emerge --config netqmail</i>
 # <i>iptables -I INPUT -p tcp --dport smtp -i ! ${LAN} -j REJECT</i>
 # <i>ln -s /var/qmail/supervise/qmail-send /service/qmail-send</i>
 # <i>ln -s /var/qmail/supervise/qmail-smtpd /service/qmail-smtpd</i>
@@ -816,10 +816,10 @@
 </pre>
 
 <p>
-I'm a huge fan of qmail, but you're free to use a different mta :).  When you
+I'm a huge fan of netqmail, but you're free to use a different mta :).  When you
 setup e-mail on the hosts in your network, tell them that their SMTP server is
 192.168.0.1 and everything should be peachy.  You might want to visit the <uri
-link="http://qmail.org/">qmail homepage</uri> for more documentation.
+link="http://netqmail.org/">netqmail homepage</uri> for more documentation.
 </p>
 
 </body>



1.38                 xml/htdocs/doc/en/qmail-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/qmail-howto.xml?rev=1.38&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/qmail-howto.xml?rev=1.38&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/qmail-howto.xml?r1=1.37&r2=1.38

Index: qmail-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/qmail-howto.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- qmail-howto.xml	18 Jun 2006 22:40:51 -0000	1.37
+++ qmail-howto.xml	7 Mar 2007 21:30:18 -0000	1.38
@@ -1,24 +1,24 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/qmail-howto.xml,v 1.37 2006/06/18 22:40:51 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/qmail-howto.xml,v 1.38 2007/03/07 21:30:18 nightmorph Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/qmail-howto.xml">
 
-<title>qmail/vpopmail Virtual Mail Hosting System Guide</title>
+<title>netqmail/vpopmail Virtual Mail Hosting System Guide</title>
 
 <author title="Author">
   <mail link="vapier@g.o">Mike Frysinger</mail>
 </author>
 
 <abstract>
-This document details how to create a mail hosting system based upon qmail, 
+This document details how to create a mail hosting system based upon netqmail,
 vpopmail, courier-imap, mysql, and horde's imp.
 </abstract>
 
 <license/>
 
-<version>1.13</version>
-<date>2006-06-18</date>
+<version>1.14</version>
+<date>2007-03-07</date>
 
 <chapter>
 <title>Introduction</title>
@@ -26,16 +26,16 @@
 <body>
 
 <p>
-Whether you're providing e-mail for just system daemons, a single server, a 
-domain, or for many virtual domains, qmail can easily be setup to handle your 
-needs. This guide will help you setup qmail for all of these scenarios with a 
+Whether you're providing e-mail for just system daemons, a single server, a
+domain, or for many virtual domains, netqmail can easily be setup to handle your
+needs. This guide will help you setup netqmail for all of these scenarios with a
 focus on remote access and encrypted communications the whole way through.
 </p>
 
 <p>
-Specifically, the packages this guide will help you with are qmail, 
-courier-imap, vpopmail, and horde/imp.  These core packages will also bring in 
-daemontools, ucspi-tcp, mysql, apache, and mod_php.  qmail provides the core 
+Specifically, the packages this guide will help you with are netqmail, 
+courier-imap, vpopmail, and horde/imp. These core packages will also bring in 
+daemontools, ucspi-tcp, mysql, apache, and mod_php.  netqmail provides the core 
 mta functions, courier-imap provides remote retrieval services, vpopmail 
 provides virtual domain management, and horde/imp provides webmail access.
 </p>
@@ -54,13 +54,13 @@
 </note>
 
 <p>
-The last step of course is to commit yourself to the qmail system.  There are 
-many other packages with which you could build your e-mail system.  Now is 
-the time to research and decide that qmail is for you.  We have another <uri 
-link="virt-mail-howto.xml">lovely guide</uri> centered around <uri 
-link="http://www.postfix.org/">Postfix</uri>, or you could look into <uri 
-link="http://www.exim.org/">exim</uri>.  It's up to you to choose the best 
-solution for yourself; it is up to us to show you how to use qmail.
+The last step of course is to commit yourself to the netqmail system.  There are
+many other packages with which you could build your e-mail system.  Now is the
+time to research and decide that netqmail is for you.  We have another <uri
+link="virt-mail-howto.xml">lovely guide</uri> centered around <uri
+link="http://www.postfix.org/">Postfix</uri>, or you could look into <uri
+link="http://www.exim.org/">exim</uri>.  It's up to you to choose the best
+solution for yourself; it is up to us to show you how to use netqmail.
 </p>
 
 </body>
@@ -68,16 +68,16 @@
 </chapter>
 
 <chapter>
-<title>qmail (talking to myself)</title>
+<title>netqmail (talking to myself)</title>
 <section>
 <body>
 
-<pre caption="Emerge qmail">
-# <i>emerge mail-mta/qmail</i>
+<pre caption="Emerge netqmail">
+# <i>emerge mail-mta/netqmail</i>
 </pre>
 
 <impo>
-This guide is designed around qmail-1.03-r13 or later.  Will it work with 
+This guide is designed around netqmail-1.05-r4 or later.  Will it work with 
 earlier versions?  Maybe.  Should you upgrade? Yes, if you want to be sure this 
 guide will work.
 </impo>
@@ -85,33 +85,33 @@
 <warn>
 If you get a message like <c>the virtual/mta package conflicts with another 
 package</c> then you need to make sure to unmerge the other MTA on your system. 
-To figure out what package that is, just run <c>emerge qmail -p</c>.
+To figure out what package that is, just run <c>emerge netqmail -p</c>.
 </warn>
 
 <p>
-Emerging qmail will also emerge ucspi-tcp and daemontools.  You can read up on 
-<uri link="http://cr.yp.to/ucspi-tcp.html">ucspi-tcp</uri> and on <uri 
-link="http://cr.yp.to/daemontools.html">daemontools</uri> if you like.  
-Basically, daemontools is responsible for managing qmail as a service while 
-ucspi-tcp is responsible for managing the incoming TCP connections to the 
-qmail service.
+Emerging netqmail will also emerge ucspi-tcp and daemontools.  You can read up
+on <uri link="http://cr.yp.to/ucspi-tcp.html">ucspi-tcp</uri> and on <uri
+link="http://cr.yp.to/daemontools.html">daemontools</uri> if you like.
+Basically, daemontools is responsible for managing netqmail as a service while
+ucspi-tcp is responsible for managing the incoming TCP connections to the
+netqmail service.
 </p>
 
 <p>
 First we have a few post-install configuration steps.
 </p>
 
-<pre caption="Out-of-the-box setup for qmail">
+<pre caption="Out-of-the-box setup for netqmail">
 <comment>(Customize to fit your personal information)</comment>
 # <i>nano /var/qmail/control/servercert.cnf</i>
-# <i>ebuild /var/db/pkg/mail-mta/qmail-1.03-r*/qmail-1.03-r*.ebuild config</i>
+# <i>emerge --config netqmail</i>
 </pre>
 
 <p>
-The design of qmail has been completely around the focus of security.  To this 
-end, e-mail is never sent to the user 'root'.  So now you have to select a user 
-on your machine to receive mail that would normally be destined for 'root'.  
-From now on in this guide, I will refer to that user as I have it in my setup, 
+The design of netqmail has been completely around the focus of security.  To
+this end, e-mail is never sent to the user 'root'.  So now you have to select a
+user on your machine to receive mail that would normally be destined for 'root'.
+From now on in this guide, I will refer to that user as I have it in my setup,
 'vapier'.
 </p>
 
@@ -123,10 +123,10 @@
 </pre>
 
 <p>
-Now we want to get the qmail delivery service up and running.
+Now we want to get the netqmail delivery service up and running.
 </p>
 
-<pre caption="Start qmail delivery service">
+<pre caption="Start netqmail delivery service">
 # <i>rc-update add svscan default</i>
 # <i>/etc/init.d/svscan start</i>
 # <i>cd /service</i>
@@ -134,7 +134,7 @@
 </pre>
 
 <p>
-We want to make sure qmail is working correctly, so here's a quick test.
+We want to make sure netqmail is working correctly, so here's a quick test.
 </p>
 
 <pre caption="Test delivery service">
@@ -161,12 +161,12 @@
 <warn>
 If you don't receive any mail or you see weird errors in the log files (check
 <path>/var/log/qmail/</path>) involving 'localhost.localhost', then that means
-your domain/dns information is not setup properly.  By default, qmail utilizes
-the output of <c>hostname --fqdn</c>.  If, on your machine, this returns
-'localhost', then check your <path>/etc/conf.d/hostname</path>,
+your domain/dns information is not setup properly.  By default, netqmail
+utilizes the output of <c>hostname --fqdn</c>.  If, on your machine, this
+returns 'localhost', then check your <path>/etc/conf.d/hostname</path>,
 <path>/etc/hosts</path>, and your dns to make sure everything is correct.  Once
-you have, edit the configuration files in <path>/var/qmail/control/</path>.
-Use the example setups that follow if you need some more help.
+you have, edit the configuration files in <path>/var/qmail/control/</path>.  Use
+the example setups that follow if you need some more help.
 </warn>
 
 <pre caption="Example /var/qmail/control/ files for a 2nd level domain">
@@ -280,7 +280,7 @@
 Every domain that vpopmail creates comes with a 'postmaster' account.  Here we 
 told vpopmail that the password for the postmaster account is 'postpass'.  
 Before vpopmail can be truly useful, we'll need to be able to receive mail 
-via courier and send mail via qmail and SMTP.
+via courier and send mail via netqmail and SMTP.
 </p>
 
 </body>
@@ -345,7 +345,7 @@
 </chapter>
 
 <chapter>
-<title>qmail (talking to the world)</title>
+<title>netqmail (talking to the world)</title>
 <section>
 <body>
 
@@ -354,7 +354,7 @@
 hole for people to abuse.
 </p>
 
-<pre caption="Start qmail SMTP service">
+<pre caption="Start netqmail SMTP service">
 # <i>cd /var/qmail/control/</i>
 # <i>nano conf-smtpd</i>
 <comment>(Uncomment the SMTP-AUTH variables and set QMAIL_SMTP_CHECKPASSWORD to /var/vpopmail/bin/vchkpw)</comment>
@@ -367,14 +367,14 @@
 </pre>
 
 <p>
-Assuming you haven't tweaked the qmail control files at all, qmail will now 
-accept mail for the wh0rd.org virtual domain and for users of the local machine.
-Furthermore, qmail will relay mail for anyone who sends via 127.0.0.1 and for 
-anyone who is able to authenticate with vpopmail.  When you setup your mail 
-client to send mail, make sure you select options like 'Server requires 
-authentication'.  In my case, I set the user as 'vapier@×××××.org' and my 
-password as 'vappw'.  The last detail is to make sure you tell your mail 
-client to use SSL/TLS for SMTP communication. qmail will not let you 
+Assuming you haven't tweaked the netqmail control files at all, netqmail will
+now accept mail for the wh0rd.org virtual domain and for users of the local
+machine.  Furthermore, netqmail will relay mail for anyone who sends via
+127.0.0.1 and for anyone who is able to authenticate with vpopmail.  When you
+setup your mail client to send mail, make sure you select options like 'Server
+requires authentication'.  In my case, I set the user as 'vapier@×××××.org' and
+my password as 'vappw'.  The last detail is to make sure you tell your mail
+client to use SSL/TLS for SMTP communication. netqmail will not let you
 authenticate if the session is not encrypted.
 </p>
 
@@ -528,10 +528,10 @@
 <body>
 
 <p>
-If you run into problems with qmail queues and have a hard time debugging the 
-situation, you may want to look into <uri 
-link="http://qmhandle.sourceforge.net/">qmHandle</uri>.  It's a simple perl 
-program which allows you to view and manage the qmail message queue.  Again, 
+If you run into problems with netqmail queues and have a hard time debugging the
+situation, you may want to look into <uri
+link="http://qmhandle.sourceforge.net/">qmHandle</uri>.  It's a simple perl
+program which allows you to view and manage the netqmail message queue.  Again,
 all you need to do is <c>emerge net-mail/qmhandle</c>.
 </p>
 
@@ -559,16 +559,16 @@
 <body>
 
 <p>
-qmail utilizes ucspi-tcp to handle the incoming connections for qmail.  If you 
-wish to customize these filtering rules, then see the configuration files in 
-<path>/etc/tcprules.d/</path> (older versions of qmail put the files in /etc).  
-There you'll find two files for each service, the configuration file (i.e. 
-tcp.qmail-smtp) and the compiled version of this file that ucspi-tcp uses 
-(i.e. tcp.qmail-smtp.cdb).  Whenever you update the configuration file, you'll 
-have to rebuild the binary version of it. Just run <c>tcprules 
-tcp.qmail-smtp.cdb tcp.qmail-smtp.tmp &lt; tcp.qmail-smtp</c>.  Every time a 
-connection is made to the qmail service, the compiled rules file is re-read, 
-so there's no need to restart the service.
+netqmail utilizes ucspi-tcp to handle the incoming connections for netqmail.  If
+you wish to customize these filtering rules, then see the configuration files in
+<path>/etc/tcprules.d/</path> (older versions put files in <path>/etc</path>).
+There you'll find two files for each service, the configuration file (i.e.
+tcp.qmail-smtp) and the compiled version of this file that ucspi-tcp uses (i.e.
+tcp.qmail-smtp.cdb).  Whenever you update the configuration file, you'll have to
+rebuild the binary version of it. Just run <c>tcprules tcp.qmail-smtp.cdb
+tcp.qmail-smtp.tmp &lt; tcp.qmail-smtp</c>.  Every time a connection is made to
+the netqmail service, the compiled rules file is re-read, so there's no need to
+restart the service.
 </p>
 
 </body>
@@ -699,7 +699,7 @@
 please contact <mail link="vapier@g.o">me</mail> or file a bug with 
 <uri link="http://bugs.gentoo.org/">Gentoo's Bugtracking Website</uri>.  If 
 you have some interesting bits you think would enhance this guide, by all means 
-send it my way for inclusion.  I love qmail and would gladly add stuff that 
+send it my way for inclusion.  I love netqmail and would gladly add stuff that 
 could possibly enhance a user's experience with the mta.
 </p>
 



-- 
gentoo-doc-cvs@g.o mailing list