Now that you've downloaded all the needed packages, we can start the install. At this point you should have a qmailrocks source directory located at /downloads/qmailrocks. If you don't, go back to step 1.

To get things rolling a bit I have altered the qmr_install_freebsd-s1.script to the following lines (sh /downloads/qmailrocks/obsd/users.sh):

First create some directories

cd /downloads/qmailrocks
mkdir -p /var/qmail
mkdir -p /usr/src/qmail

Now create the users

groupadd nofiles
useradd -g nofiles -d /var/qmail/alias -s /sbin/nologin alias 
useradd -g nofiles -d /var/qmail -s /sbin/nologin qmaild
useradd -g nofiles -d /var/qmail -s /sbin/nologin qmaill
useradd -g nofiles -d /var/qmail -s /sbin/nologin qmailp
groupadd qmail
useradd -g qmail -d /var/qmail -s /sbin/nologin qmailq
useradd -g qmail -d /var/qmail -s /sbin/nologin qmailr
useradd -g qmail -d /var/qmail -s /sbin/nologin qmails
groupadd vchkpw
useradd -g vchkpw -m -d /home/vpopmail -s /sbin/nologin vpopmail

cd /usr/src/qmail
tar zxvf /downloads/qmailrocks/qmail-1.03.tar.gz
tar zxvf /downloads/qmailrocks/ucspi-tcp-0.88.tar.gz
mkdir -p /package
chmod 1755 /package
cd /package
tar zxvf /downloads/qmailrocks/daemontools-0.76.tar.gz

mkdir /var/log/qmail
cd /var/log/qmail
mkdir qmail-send qmail-smtpd qmail-pop3d
chown -R qmaill:wheel /var/log/qmail
chmod -R 750 /var/log/qmail

mkdir /var/qmail/supervise
cd /var/qmail/supervise
mkdir -p qmail-smtpd/log qmail-send/log qmail-pop3d/log
chmod +t qmail-smtpd qmail-send qmail-pop3d

echo 211 > /usr/src/qmail/qmail-1.03/conf-split
echo 255 > /usr/src/qmail/qmail-1.03/conf-spawn

If the above went well then you should have the qmail sources in /usr/src/qmail, along with ucspi.

Next we're going to apply the jms (or John Simpson) patch. If you read the qmr mail list at all then you will know who John is, and you will also know a little about his 6x series of patch. As auth without TLS is a bad idea we shall use this in the patch. You may still bypass this using a variable in the run file, it's generally a bad idea and if you need for that is great enough then you will seek out that information yourself. Beware wireless LAN users!

cd /usr/src/qmail/qmail-1.03

We can patch the source in one of two ways:

wget http://www.jms1.net/qmail/patches/qmail-1.03-jms1.6b.patch
patch < ./qmail-1.03-jms1.6b.patch

or as a single command:

wget -O - http://www.jms1.net/qmail/patches/qmail-1.03-jms1.6b.patch | patch

The choice is yours.

We must now make and install the qmail program itself, with patches...

make man
make setup check
./config-fast your_fqdn_hostname (ex: ./config-fast mail.mydomain.com)

If there are no errors, Qmail has been built successfully!

Now, to avoid problems later on we can make the certificates. These are requires so that TLS works...

make cert

# make cert
openssl req -new -x509 -nodes  -out /var/qmail/control/servercert.pem -days 366  -keyout /var/qmail/control/servercert.pem
Generating a 1024 bit RSA private key
......................++++++
.++++++
writing new private key to '/var/qmail/control/servercert.pem'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) []:GB
State or Province Name (full name) []:Berks
Locality Name (eg, city) []:London
Organization Name (eg, company) []:Spindle Spacers Ltd
Organizational Unit Name (eg, section) []:Sysadmin Dept
Common Name (eg, fully qualified host name) []:mail.spindlespacers.com
Email Address []:posty@spindlespacers.com

chmod 640 /var/qmail/control/servercert.pem
chown qmaild.qmail /var/qmail/control/servercert.pem
ln -s /var/qmail/control/servercert.pem /var/qmail/control/clientcert.pem

chown -R vpopmail:qmail /var/qmail/control/clientcert.pem /var/qmail/control/servercert.pem

Now we build ucspi-tcp...

cd /usr/src/qmail/ucspi-tcp-0.88/
make
make setup check

If you don't get any errors, that's it for ucspi-tcp! Now we build the daemontools....

cd /package/admin/daemontools-0.76
package/install

After installation, the script will tell you to reboot to start svscan. This is beacause it adds a single line to /etc/rc.local, that line is:

csh -cf '/command/svscanboot &'

Fell free to run this at the command line to start svscan, that is all that rebooting will do. However, if you feel less confident with your installtion, perhaps this is not on a clean box, then a reboot is not out of the question. Reboot to see what services start up and then change your system to work a little smarter.