dot

packages and services management
Log | Files | Refs | README

commit 080900f61611603ce7a2f5c86d5ae6cca484c0d1
parent 586a09ec45986453029995f9e7c4d6d5163883bd
Author: Josuah Demangeon <mail@josuah.net>
Date:   Tue, 10 Jul 2018 00:22:50 +0200

qmail: let it on its (hardcoded) destination path ;_;

Diffstat:
Mbin/s6 | 2+-
Mpack/qmail/build | 13+++++++++----
Ds6/qmail/data/bin/bouncesaying | 2--
Ds6/qmail/data/bin/condredirect | 2--
Ds6/qmail/data/bin/datemail | 2--
Ds6/qmail/data/bin/elq | 2--
Ds6/qmail/data/bin/except | 2--
Ds6/qmail/data/bin/forward | 2--
Ds6/qmail/data/bin/maildir2mbox | 2--
Ds6/qmail/data/bin/maildirmake | 2--
Ds6/qmail/data/bin/maildirwatch | 2--
Ds6/qmail/data/bin/mailsubj | 2--
Ds6/qmail/data/bin/pinq | 2--
Ds6/qmail/data/bin/predate | 2--
Ds6/qmail/data/bin/preline | 2--
Ds6/qmail/data/bin/qail | 2--
Ds6/qmail/data/bin/qbiff | 2--
Ds6/qmail/data/bin/qmail-clean | 2--
Ds6/qmail/data/bin/qmail-getpw | 2--
Ds6/qmail/data/bin/qmail-inject | 2--
Ds6/qmail/data/bin/qmail-local | 2--
Ds6/qmail/data/bin/qmail-lspawn | 2--
Ds6/qmail/data/bin/qmail-newmrh | 2--
Ds6/qmail/data/bin/qmail-newu | 2--
Ds6/qmail/data/bin/qmail-pop3d | 2--
Ds6/qmail/data/bin/qmail-popup | 2--
Ds6/qmail/data/bin/qmail-pw2u | 2--
Ds6/qmail/data/bin/qmail-qmqpc | 2--
Ds6/qmail/data/bin/qmail-qmqpd | 2--
Ds6/qmail/data/bin/qmail-qmtpd | 2--
Ds6/qmail/data/bin/qmail-qread | 2--
Ds6/qmail/data/bin/qmail-qstat | 2--
Ds6/qmail/data/bin/qmail-queue | 2--
Ds6/qmail/data/bin/qmail-remote | 2--
Ds6/qmail/data/bin/qmail-rspawn | 2--
Ds6/qmail/data/bin/qmail-send | 2--
Ds6/qmail/data/bin/qmail-showctl | 2--
Ds6/qmail/data/bin/qmail-smtpd | 2--
Ds6/qmail/data/bin/qmail-start | 2--
Ds6/qmail/data/bin/qmail-tcpok | 2--
Ds6/qmail/data/bin/qmail-tcpto | 2--
Ds6/qmail/data/bin/qreceipt | 2--
Ds6/qmail/data/bin/qsmhook | 2--
Ds6/qmail/data/bin/sendmail | 2--
Ds6/qmail/data/bin/splogger | 2--
Ds6/qmail/data/bin/tcp-env | 2--
Ds6/qmail/data/boot/binm1 | 10----------
Ds6/qmail/data/boot/binm1+df | 11-----------
Ds6/qmail/data/boot/binm2 | 10----------
Ds6/qmail/data/boot/binm2+df | 11-----------
Ds6/qmail/data/boot/binm3 | 10----------
Ds6/qmail/data/boot/binm3+df | 11-----------
Ds6/qmail/data/boot/home | 7-------
Ds6/qmail/data/boot/home+df | 9---------
Ds6/qmail/data/boot/proc | 7-------
Ds6/qmail/data/boot/proc+df | 9---------
Ds6/qmail/data/data/bin/bouncesaying | 0
Ds6/qmail/data/data/bin/condredirect | 0
Ds6/qmail/data/data/bin/datemail | 3---
Ds6/qmail/data/data/bin/elq | 3---
Ds6/qmail/data/data/bin/except | 0
Ds6/qmail/data/data/bin/forward | 0
Ds6/qmail/data/data/bin/maildir2mbox | 0
Ds6/qmail/data/data/bin/maildirmake | 0
Ds6/qmail/data/data/bin/maildirwatch | 0
Ds6/qmail/data/data/bin/mailsubj | 9---------
Ds6/qmail/data/data/bin/pinq | 3---
Ds6/qmail/data/data/bin/predate | 0
Ds6/qmail/data/data/bin/preline | 0
Ds6/qmail/data/data/bin/qail | 3---
Ds6/qmail/data/data/bin/qbiff | 0
Ds6/qmail/data/data/bin/qmail-clean | 0
Ds6/qmail/data/data/bin/qmail-getpw | 0
Ds6/qmail/data/data/bin/qmail-inject | 0
Ds6/qmail/data/data/bin/qmail-local | 0
Ds6/qmail/data/data/bin/qmail-lspawn | 0
Ds6/qmail/data/data/bin/qmail-newmrh | 0
Ds6/qmail/data/data/bin/qmail-newu | 0
Ds6/qmail/data/data/bin/qmail-pop3d | 0
Ds6/qmail/data/data/bin/qmail-popup | 0
Ds6/qmail/data/data/bin/qmail-pw2u | 0
Ds6/qmail/data/data/bin/qmail-qmqpc | 0
Ds6/qmail/data/data/bin/qmail-qmqpd | 0
Ds6/qmail/data/data/bin/qmail-qmtpd | 0
Ds6/qmail/data/data/bin/qmail-qread | 0
Ds6/qmail/data/data/bin/qmail-qstat | 9---------
Ds6/qmail/data/data/bin/qmail-queue | 0
Ds6/qmail/data/data/bin/qmail-remote | 0
Ds6/qmail/data/data/bin/qmail-rspawn | 0
Ds6/qmail/data/data/bin/qmail-send | 0
Ds6/qmail/data/data/bin/qmail-showctl | 0
Ds6/qmail/data/data/bin/qmail-smtpd | 0
Ds6/qmail/data/data/bin/qmail-start | 0
Ds6/qmail/data/data/bin/qmail-tcpok | 0
Ds6/qmail/data/data/bin/qmail-tcpto | 0
Ds6/qmail/data/data/bin/qreceipt | 0
Ds6/qmail/data/data/bin/qsmhook | 0
Ds6/qmail/data/data/bin/sendmail | 0
Ds6/qmail/data/data/bin/splogger | 0
Ds6/qmail/data/data/bin/tcp-env | 0
Ds6/qmail/data/data/boot/binm1 | 10----------
Ds6/qmail/data/data/boot/binm1+df | 11-----------
Ds6/qmail/data/data/boot/binm2 | 10----------
Ds6/qmail/data/data/boot/binm2+df | 11-----------
Ds6/qmail/data/data/boot/binm3 | 10----------
Ds6/qmail/data/data/boot/binm3+df | 11-----------
Ds6/qmail/data/data/boot/home | 7-------
Ds6/qmail/data/data/boot/home+df | 9---------
Ds6/qmail/data/data/boot/proc | 7-------
Ds6/qmail/data/data/boot/proc+df | 9---------
Ds6/qmail/data/data/control/defaultdelivery | 1-
Ds6/qmail/data/data/control/defaultdomain | 1-
Ds6/qmail/data/data/control/locals | 1-
Ds6/qmail/data/data/control/me | 1-
Ds6/qmail/data/data/control/plusdomain | 1-
Ds6/qmail/data/data/control/rcpthosts | 1-
Ds6/qmail/data/data/doc/FAQ | 709-------------------------------------------------------------------------------
Ds6/qmail/data/data/doc/INSTALL | 1-
Ds6/qmail/data/data/doc/INSTALL.alias | 40----------------------------------------
Ds6/qmail/data/data/doc/INSTALL.ctl | 38--------------------------------------
Ds6/qmail/data/data/doc/INSTALL.ids | 72------------------------------------------------------------------------
Ds6/qmail/data/data/doc/INSTALL.maildir | 59-----------------------------------------------------------
Ds6/qmail/data/data/doc/INSTALL.mbox | 53-----------------------------------------------------
Ds6/qmail/data/data/doc/INSTALL.vsm | 50--------------------------------------------------
Ds6/qmail/data/data/doc/PIC.local2alias | 37-------------------------------------
Ds6/qmail/data/data/doc/PIC.local2ext | 41-----------------------------------------
Ds6/qmail/data/data/doc/PIC.local2local | 40----------------------------------------
Ds6/qmail/data/data/doc/PIC.local2rem | 38--------------------------------------
Ds6/qmail/data/data/doc/PIC.local2virt | 44--------------------------------------------
Ds6/qmail/data/data/doc/PIC.nullclient | 38--------------------------------------
Ds6/qmail/data/data/doc/PIC.relaybad | 8--------
Ds6/qmail/data/data/doc/PIC.relaygood | 33---------------------------------
Ds6/qmail/data/data/doc/PIC.rem2local | 36------------------------------------
Ds6/qmail/data/data/doc/REMOVE.binmail | 16----------------
Ds6/qmail/data/data/doc/REMOVE.sendmail | 28----------------------------
Ds6/qmail/data/data/doc/SENDMAIL | 76----------------------------------------------------------------------------
Ds6/qmail/data/data/doc/TEST.deliver | 82-------------------------------------------------------------------------------
Ds6/qmail/data/data/doc/TEST.receive | 41-----------------------------------------
Ds6/qmail/data/data/doc/UPGRADE | 66------------------------------------------------------------------
Ds6/qmail/data/data/queue/lock/sendmutex | 0
Ds6/qmail/data/data/queue/lock/tcpto | 0
Ds6/qmail/data/doc/FAQ | 709-------------------------------------------------------------------------------
Ds6/qmail/data/doc/INSTALL | 1-
Ds6/qmail/data/doc/INSTALL.alias | 40----------------------------------------
Ds6/qmail/data/doc/INSTALL.ctl | 38--------------------------------------
Ds6/qmail/data/doc/INSTALL.ids | 72------------------------------------------------------------------------
Ds6/qmail/data/doc/INSTALL.maildir | 59-----------------------------------------------------------
Ds6/qmail/data/doc/INSTALL.mbox | 53-----------------------------------------------------
Ds6/qmail/data/doc/INSTALL.vsm | 50--------------------------------------------------
Ds6/qmail/data/doc/PIC.local2alias | 37-------------------------------------
Ds6/qmail/data/doc/PIC.local2ext | 41-----------------------------------------
Ds6/qmail/data/doc/PIC.local2local | 40----------------------------------------
Ds6/qmail/data/doc/PIC.local2rem | 38--------------------------------------
Ds6/qmail/data/doc/PIC.local2virt | 44--------------------------------------------
Ds6/qmail/data/doc/PIC.nullclient | 38--------------------------------------
Ds6/qmail/data/doc/PIC.relaybad | 8--------
Ds6/qmail/data/doc/PIC.relaygood | 33---------------------------------
Ds6/qmail/data/doc/PIC.rem2local | 36------------------------------------
Ds6/qmail/data/doc/REMOVE.binmail | 16----------------
Ds6/qmail/data/doc/REMOVE.sendmail | 28----------------------------
Ds6/qmail/data/doc/SENDMAIL | 76----------------------------------------------------------------------------
Ds6/qmail/data/doc/TEST.deliver | 82-------------------------------------------------------------------------------
Ds6/qmail/data/doc/TEST.receive | 41-----------------------------------------
Ds6/qmail/data/doc/UPGRADE | 66------------------------------------------------------------------
Ds6/qmail/data/queue/info/0/... | 0
Ds6/qmail/data/queue/info/1/... | 0
Ds6/qmail/data/queue/info/10/... | 0
Ds6/qmail/data/queue/info/11/... | 0
Ds6/qmail/data/queue/info/12/... | 0
Ds6/qmail/data/queue/info/13/... | 0
Ds6/qmail/data/queue/info/14/... | 0
Ds6/qmail/data/queue/info/15/... | 0
Ds6/qmail/data/queue/info/16/... | 0
Ds6/qmail/data/queue/info/17/... | 0
Ds6/qmail/data/queue/info/18/... | 0
Ds6/qmail/data/queue/info/19/... | 0
Ds6/qmail/data/queue/info/2/... | 0
Ds6/qmail/data/queue/info/20/... | 0
Ds6/qmail/data/queue/info/21/... | 0
Ds6/qmail/data/queue/info/22/... | 0
Ds6/qmail/data/queue/info/3/... | 0
Ds6/qmail/data/queue/info/4/... | 0
Ds6/qmail/data/queue/info/5/... | 0
Ds6/qmail/data/queue/info/6/... | 0
Ds6/qmail/data/queue/info/7/... | 0
Ds6/qmail/data/queue/info/8/... | 0
Ds6/qmail/data/queue/info/9/... | 0
Ds6/qmail/data/queue/local/0/... | 0
Ds6/qmail/data/queue/local/1/... | 0
Ds6/qmail/data/queue/local/10/... | 0
Ds6/qmail/data/queue/local/11/... | 0
Ds6/qmail/data/queue/local/12/... | 0
Ds6/qmail/data/queue/local/13/... | 0
Ds6/qmail/data/queue/local/14/... | 0
Ds6/qmail/data/queue/local/15/... | 0
Ds6/qmail/data/queue/local/16/... | 0
Ds6/qmail/data/queue/local/17/... | 0
Ds6/qmail/data/queue/local/18/... | 0
Ds6/qmail/data/queue/local/19/... | 0
Ds6/qmail/data/queue/local/2/... | 0
Ds6/qmail/data/queue/local/20/... | 0
Ds6/qmail/data/queue/local/21/... | 0
Ds6/qmail/data/queue/local/22/... | 0
Ds6/qmail/data/queue/local/3/... | 0
Ds6/qmail/data/queue/local/4/... | 0
Ds6/qmail/data/queue/local/5/... | 0
Ds6/qmail/data/queue/local/6/... | 0
Ds6/qmail/data/queue/local/7/... | 0
Ds6/qmail/data/queue/local/8/... | 0
Ds6/qmail/data/queue/local/9/... | 0
Ds6/qmail/data/queue/lock/sendmutex | 0
Ds6/qmail/data/queue/lock/tcpto | 0
Ds6/qmail/data/queue/mess/0/... | 0
Ds6/qmail/data/queue/mess/1/... | 0
Ds6/qmail/data/queue/mess/10/... | 0
Ds6/qmail/data/queue/mess/11/... | 0
Ds6/qmail/data/queue/mess/12/... | 0
Ds6/qmail/data/queue/mess/13/... | 0
Ds6/qmail/data/queue/mess/14/... | 0
Ds6/qmail/data/queue/mess/15/... | 0
Ds6/qmail/data/queue/mess/16/... | 0
Ds6/qmail/data/queue/mess/17/... | 0
Ds6/qmail/data/queue/mess/18/... | 0
Ds6/qmail/data/queue/mess/19/... | 0
Ds6/qmail/data/queue/mess/2/... | 0
Ds6/qmail/data/queue/mess/20/... | 0
Ds6/qmail/data/queue/mess/21/... | 0
Ds6/qmail/data/queue/mess/22/... | 0
Ds6/qmail/data/queue/mess/3/... | 0
Ds6/qmail/data/queue/mess/4/... | 0
Ds6/qmail/data/queue/mess/5/... | 0
Ds6/qmail/data/queue/mess/6/... | 0
Ds6/qmail/data/queue/mess/7/... | 0
Ds6/qmail/data/queue/mess/8/... | 0
Ds6/qmail/data/queue/mess/9/... | 0
Ds6/qmail/data/queue/remote/0/... | 0
Ds6/qmail/data/queue/remote/1/... | 0
Ds6/qmail/data/queue/remote/10/... | 0
Ds6/qmail/data/queue/remote/11/... | 0
Ds6/qmail/data/queue/remote/12/... | 0
Ds6/qmail/data/queue/remote/13/... | 0
Ds6/qmail/data/queue/remote/14/... | 0
Ds6/qmail/data/queue/remote/15/... | 0
Ds6/qmail/data/queue/remote/16/... | 0
Ds6/qmail/data/queue/remote/17/... | 0
Ds6/qmail/data/queue/remote/18/... | 0
Ds6/qmail/data/queue/remote/19/... | 0
Ds6/qmail/data/queue/remote/2/... | 0
Ds6/qmail/data/queue/remote/20/... | 0
Ds6/qmail/data/queue/remote/21/... | 0
Ds6/qmail/data/queue/remote/22/... | 0
Ds6/qmail/data/queue/remote/3/... | 0
Ds6/qmail/data/queue/remote/4/... | 0
Ds6/qmail/data/queue/remote/5/... | 0
Ds6/qmail/data/queue/remote/6/... | 0
Ds6/qmail/data/queue/remote/7/... | 0
Ds6/qmail/data/queue/remote/8/... | 0
Ds6/qmail/data/queue/remote/9/... | 0
Ds6/qmail/data/users/... | 0
259 files changed, 10 insertions(+), 3611 deletions(-)

diff --git a/bin/s6 b/bin/s6 @@ -1,6 +1,6 @@ #!/bin/sh -e -service=/s6/ +service=/etc/s6/ export PATH="$PATH:/local/bin" case $1 in diff --git a/pack/qmail/build b/pack/qmail/build @@ -1,15 +1,20 @@ #!/bin/sh -ex +DATA=/etc/s6/qmail/data + echo gcc -O2 -include /usr/include/errno.h >conf-cc -echo "$PREFIX" >conf-qmail +echo "$DATA" >conf-qmail touch nroff chmod +x nroff export PATH=$PWD:$PATH +mkdir -p "$DATA/" "$PREFIX/share/" "$PREFIX/bin" make setup check ./config -rm -rf "$PREFIX/alias" "$PREFIX/control" "$PREFIX/queue" "$PREFIX/users" -mkdir -p "$PREFIX/share" -mv "$PREFIX/doc" "$PREFIX/man" "$PREFIX/share" +mv "$DATA/man/" "$PREFIX/share/" +mv "$DATA/bin/"* "$PREFIX/bin/" + +cd "$PREFIX/bin/" +ln -s "$PREFIX/bin/"* "$DATA/bin/" diff --git a/s6/qmail/data/bin/bouncesaying b/s6/qmail/data/bin/bouncesaying @@ -1 +0,0 @@ -/local/bin/bouncesaying- \ No newline at end of file diff --git a/s6/qmail/data/bin/condredirect b/s6/qmail/data/bin/condredirect @@ -1 +0,0 @@ -/local/bin/condredirect- \ No newline at end of file diff --git a/s6/qmail/data/bin/datemail b/s6/qmail/data/bin/datemail @@ -1 +0,0 @@ -/local/bin/datemail- \ No newline at end of file diff --git a/s6/qmail/data/bin/elq b/s6/qmail/data/bin/elq @@ -1 +0,0 @@ -/local/bin/elq- \ No newline at end of file diff --git a/s6/qmail/data/bin/except b/s6/qmail/data/bin/except @@ -1 +0,0 @@ -/local/bin/except- \ No newline at end of file diff --git a/s6/qmail/data/bin/forward b/s6/qmail/data/bin/forward @@ -1 +0,0 @@ -/local/bin/forward- \ No newline at end of file diff --git a/s6/qmail/data/bin/maildir2mbox b/s6/qmail/data/bin/maildir2mbox @@ -1 +0,0 @@ -/local/bin/maildir2mbox- \ No newline at end of file diff --git a/s6/qmail/data/bin/maildirmake b/s6/qmail/data/bin/maildirmake @@ -1 +0,0 @@ -/local/bin/maildirmake- \ No newline at end of file diff --git a/s6/qmail/data/bin/maildirwatch b/s6/qmail/data/bin/maildirwatch @@ -1 +0,0 @@ -/local/bin/maildirwatch- \ No newline at end of file diff --git a/s6/qmail/data/bin/mailsubj b/s6/qmail/data/bin/mailsubj @@ -1 +0,0 @@ -/local/bin/mailsubj- \ No newline at end of file diff --git a/s6/qmail/data/bin/pinq b/s6/qmail/data/bin/pinq @@ -1 +0,0 @@ -/local/bin/pinq- \ No newline at end of file diff --git a/s6/qmail/data/bin/predate b/s6/qmail/data/bin/predate @@ -1 +0,0 @@ -/local/bin/predate- \ No newline at end of file diff --git a/s6/qmail/data/bin/preline b/s6/qmail/data/bin/preline @@ -1 +0,0 @@ -/local/bin/preline- \ No newline at end of file diff --git a/s6/qmail/data/bin/qail b/s6/qmail/data/bin/qail @@ -1 +0,0 @@ -/local/bin/qail- \ No newline at end of file diff --git a/s6/qmail/data/bin/qbiff b/s6/qmail/data/bin/qbiff @@ -1 +0,0 @@ -/local/bin/qbiff- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-clean b/s6/qmail/data/bin/qmail-clean @@ -1 +0,0 @@ -/local/bin/qmail-clean- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-getpw b/s6/qmail/data/bin/qmail-getpw @@ -1 +0,0 @@ -/local/bin/qmail-getpw- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-inject b/s6/qmail/data/bin/qmail-inject @@ -1 +0,0 @@ -/local/bin/qmail-inject- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-local b/s6/qmail/data/bin/qmail-local @@ -1 +0,0 @@ -/local/bin/qmail-local- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-lspawn b/s6/qmail/data/bin/qmail-lspawn @@ -1 +0,0 @@ -/local/bin/qmail-lspawn- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-newmrh b/s6/qmail/data/bin/qmail-newmrh @@ -1 +0,0 @@ -/local/bin/qmail-newmrh- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-newu b/s6/qmail/data/bin/qmail-newu @@ -1 +0,0 @@ -/local/bin/qmail-newu- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-pop3d b/s6/qmail/data/bin/qmail-pop3d @@ -1 +0,0 @@ -/local/bin/qmail-pop3d- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-popup b/s6/qmail/data/bin/qmail-popup @@ -1 +0,0 @@ -/local/bin/qmail-popup- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-pw2u b/s6/qmail/data/bin/qmail-pw2u @@ -1 +0,0 @@ -/local/bin/qmail-pw2u- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-qmqpc b/s6/qmail/data/bin/qmail-qmqpc @@ -1 +0,0 @@ -/local/bin/qmail-qmqpc- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-qmqpd b/s6/qmail/data/bin/qmail-qmqpd @@ -1 +0,0 @@ -/local/bin/qmail-qmqpd- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-qmtpd b/s6/qmail/data/bin/qmail-qmtpd @@ -1 +0,0 @@ -/local/bin/qmail-qmtpd- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-qread b/s6/qmail/data/bin/qmail-qread @@ -1 +0,0 @@ -/local/bin/qmail-qread- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-qstat b/s6/qmail/data/bin/qmail-qstat @@ -1 +0,0 @@ -/local/bin/qmail-qstat- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-queue b/s6/qmail/data/bin/qmail-queue @@ -1 +0,0 @@ -/local/bin/qmail-queue- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-remote b/s6/qmail/data/bin/qmail-remote @@ -1 +0,0 @@ -/local/bin/qmail-remote- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-rspawn b/s6/qmail/data/bin/qmail-rspawn @@ -1 +0,0 @@ -/local/bin/qmail-rspawn- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-send b/s6/qmail/data/bin/qmail-send @@ -1 +0,0 @@ -/local/bin/qmail-send- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-showctl b/s6/qmail/data/bin/qmail-showctl @@ -1 +0,0 @@ -/local/bin/qmail-showctl- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-smtpd b/s6/qmail/data/bin/qmail-smtpd @@ -1 +0,0 @@ -/local/bin/qmail-smtpd- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-start b/s6/qmail/data/bin/qmail-start @@ -1 +0,0 @@ -/local/bin/qmail-start- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-tcpok b/s6/qmail/data/bin/qmail-tcpok @@ -1 +0,0 @@ -/local/bin/qmail-tcpok- \ No newline at end of file diff --git a/s6/qmail/data/bin/qmail-tcpto b/s6/qmail/data/bin/qmail-tcpto @@ -1 +0,0 @@ -/local/bin/qmail-tcpto- \ No newline at end of file diff --git a/s6/qmail/data/bin/qreceipt b/s6/qmail/data/bin/qreceipt @@ -1 +0,0 @@ -/local/bin/qreceipt- \ No newline at end of file diff --git a/s6/qmail/data/bin/qsmhook b/s6/qmail/data/bin/qsmhook @@ -1 +0,0 @@ -/local/bin/qsmhook- \ No newline at end of file diff --git a/s6/qmail/data/bin/sendmail b/s6/qmail/data/bin/sendmail @@ -1 +0,0 @@ -/local/bin/sendmail- \ No newline at end of file diff --git a/s6/qmail/data/bin/splogger b/s6/qmail/data/bin/splogger @@ -1 +0,0 @@ -/local/bin/splogger- \ No newline at end of file diff --git a/s6/qmail/data/bin/tcp-env b/s6/qmail/data/bin/tcp-env @@ -1 +0,0 @@ -/local/bin/tcp-env- \ No newline at end of file diff --git a/s6/qmail/data/boot/binm1 b/s6/qmail/data/boot/binm1 @@ -1,10 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using binmail to deliver messages to /var/spool/mail/$USER by default. -# Using BSD 4.4 binmail interface: /usr/libexec/mail.local -r - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start \ -'|preline -f /usr/libexec/mail.local -r "${SENDER:-MAILER-DAEMON}" -d "$USER"' \ -splogger qmail diff --git a/s6/qmail/data/boot/binm1+df b/s6/qmail/data/boot/binm1+df @@ -1,11 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using dot-forward to support sendmail-style ~/.forward files. -# Using binmail to deliver messages to /var/spool/mail/$USER by default. -# Using BSD 4.4 binmail interface: /usr/libexec/mail.local -r - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start '|dot-forward .forward -|preline -f /usr/libexec/mail.local -r "${SENDER:-MAILER-DAEMON}" -d "$USER"' \ -splogger qmail diff --git a/s6/qmail/data/boot/binm2 b/s6/qmail/data/boot/binm2 @@ -1,10 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using binmail to deliver messages to /var/spool/mail/$USER by default. -# Using SVR4 binmail interface: /bin/mail -r - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start \ -'|preline -f /bin/mail -r "${SENDER:-MAILER-DAEMON}" -d "$USER"' \ -splogger qmail diff --git a/s6/qmail/data/boot/binm2+df b/s6/qmail/data/boot/binm2+df @@ -1,11 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using dot-forward to support sendmail-style ~/.forward files. -# Using binmail to deliver messages to /var/spool/mail/$USER by default. -# Using SVR4 binmail interface: /bin/mail -r - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start '|dot-forward .forward -|preline -f /bin/mail -r "${SENDER:-MAILER-DAEMON}" -d "$USER"' \ -splogger qmail diff --git a/s6/qmail/data/boot/binm3 b/s6/qmail/data/boot/binm3 @@ -1,10 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using binmail to deliver messages to /var/spool/mail/$USER by default. -# Using V7 binmail interface: /bin/mail -f - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start \ -'|preline -f /bin/mail -f "${SENDER:-MAILER-DAEMON}" -d "$USER"' \ -splogger qmail diff --git a/s6/qmail/data/boot/binm3+df b/s6/qmail/data/boot/binm3+df @@ -1,11 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using dot-forward to support sendmail-style ~/.forward files. -# Using binmail to deliver messages to /var/spool/mail/$USER by default. -# Using V7 binmail interface: /bin/mail -f - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start '|dot-forward .forward -|preline -f /bin/mail -f "${SENDER:-MAILER-DAEMON}" -d "$USER"' \ -splogger qmail diff --git a/s6/qmail/data/boot/home b/s6/qmail/data/boot/home @@ -1,7 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using qmail-local to deliver messages to ~/Mailbox by default. - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start ./Mailbox splogger qmail diff --git a/s6/qmail/data/boot/home+df b/s6/qmail/data/boot/home+df @@ -1,9 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using dot-forward to support sendmail-style ~/.forward files. -# Using qmail-local to deliver messages to ~/Mailbox by default. - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start '|dot-forward .forward -./Mailbox' splogger qmail diff --git a/s6/qmail/data/boot/proc b/s6/qmail/data/boot/proc @@ -1,7 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using procmail to deliver messages to /var/spool/mail/$USER by default. - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start '|preline procmail' splogger qmail diff --git a/s6/qmail/data/boot/proc+df b/s6/qmail/data/boot/proc+df @@ -1,9 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using dot-forward to support sendmail-style ~/.forward files. -# Using procmail to deliver messages to /var/spool/mail/$USER by default. - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start '|dot-forward .forward -|preline procmail' splogger qmail diff --git a/s6/qmail/data/data/bin/bouncesaying b/s6/qmail/data/data/bin/bouncesaying Binary files differ. diff --git a/s6/qmail/data/data/bin/condredirect b/s6/qmail/data/data/bin/condredirect Binary files differ. diff --git a/s6/qmail/data/data/bin/datemail b/s6/qmail/data/data/bin/datemail @@ -1,3 +0,0 @@ -#!/bin/sh -# WARNING: This file was auto-generated. Do not edit! -exec /s6/qmail/data/bin/predate /s6/qmail/data/bin/sendmail ${1+"$@"} diff --git a/s6/qmail/data/data/bin/elq b/s6/qmail/data/data/bin/elq @@ -1,3 +0,0 @@ -#!/bin/sh -# WARNING: This file was auto-generated. Do not edit! -/s6/qmail/data/bin/maildir2mbox && exec elm ${1+"$@"} diff --git a/s6/qmail/data/data/bin/except b/s6/qmail/data/data/bin/except Binary files differ. diff --git a/s6/qmail/data/data/bin/forward b/s6/qmail/data/data/bin/forward Binary files differ. diff --git a/s6/qmail/data/data/bin/maildir2mbox b/s6/qmail/data/data/bin/maildir2mbox Binary files differ. diff --git a/s6/qmail/data/data/bin/maildirmake b/s6/qmail/data/data/bin/maildirmake Binary files differ. diff --git a/s6/qmail/data/data/bin/maildirwatch b/s6/qmail/data/data/bin/maildirwatch Binary files differ. diff --git a/s6/qmail/data/data/bin/mailsubj b/s6/qmail/data/data/bin/mailsubj @@ -1,9 +0,0 @@ -#!/bin/sh -# WARNING: This file was auto-generated. Do not edit! -subject="$1" -shift -( echo Subject: "$subject" - echo To: ${1+"$@"} - echo '' - cat -) | /s6/qmail/data/bin/qmail-inject diff --git a/s6/qmail/data/data/bin/pinq b/s6/qmail/data/data/bin/pinq @@ -1,3 +0,0 @@ -#!/bin/sh -# WARNING: This file was auto-generated. Do not edit! -/s6/qmail/data/bin/maildir2mbox && exec pine ${1+"$@"} diff --git a/s6/qmail/data/data/bin/predate b/s6/qmail/data/data/bin/predate Binary files differ. diff --git a/s6/qmail/data/data/bin/preline b/s6/qmail/data/data/bin/preline Binary files differ. diff --git a/s6/qmail/data/data/bin/qail b/s6/qmail/data/data/bin/qail @@ -1,3 +0,0 @@ -#!/bin/sh -# WARNING: This file was auto-generated. Do not edit! -/s6/qmail/data/bin/maildir2mbox && exec Mail ${1+"$@"} diff --git a/s6/qmail/data/data/bin/qbiff b/s6/qmail/data/data/bin/qbiff Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-clean b/s6/qmail/data/data/bin/qmail-clean Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-getpw b/s6/qmail/data/data/bin/qmail-getpw Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-inject b/s6/qmail/data/data/bin/qmail-inject Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-local b/s6/qmail/data/data/bin/qmail-local Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-lspawn b/s6/qmail/data/data/bin/qmail-lspawn Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-newmrh b/s6/qmail/data/data/bin/qmail-newmrh Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-newu b/s6/qmail/data/data/bin/qmail-newu Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-pop3d b/s6/qmail/data/data/bin/qmail-pop3d Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-popup b/s6/qmail/data/data/bin/qmail-popup Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-pw2u b/s6/qmail/data/data/bin/qmail-pw2u Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-qmqpc b/s6/qmail/data/data/bin/qmail-qmqpc Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-qmqpd b/s6/qmail/data/data/bin/qmail-qmqpd Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-qmtpd b/s6/qmail/data/data/bin/qmail-qmtpd Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-qread b/s6/qmail/data/data/bin/qmail-qread Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-qstat b/s6/qmail/data/data/bin/qmail-qstat @@ -1,9 +0,0 @@ -#!/bin/sh -# WARNING: This file was auto-generated. Do not edit! -cd /s6/qmail/data -messdirs=`echo queue/mess/* | wc -w` -messfiles=`find queue/mess/* -print | wc -w` -tododirs=`echo queue/todo | wc -w` -todofiles=`find queue/todo -print | wc -w` -echo messages in queue: `expr $messfiles - $messdirs` -echo messages in queue but not yet preprocessed: `expr $todofiles - $tododirs` diff --git a/s6/qmail/data/data/bin/qmail-queue b/s6/qmail/data/data/bin/qmail-queue Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-remote b/s6/qmail/data/data/bin/qmail-remote Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-rspawn b/s6/qmail/data/data/bin/qmail-rspawn Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-send b/s6/qmail/data/data/bin/qmail-send Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-showctl b/s6/qmail/data/data/bin/qmail-showctl Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-smtpd b/s6/qmail/data/data/bin/qmail-smtpd Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-start b/s6/qmail/data/data/bin/qmail-start Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-tcpok b/s6/qmail/data/data/bin/qmail-tcpok Binary files differ. diff --git a/s6/qmail/data/data/bin/qmail-tcpto b/s6/qmail/data/data/bin/qmail-tcpto Binary files differ. diff --git a/s6/qmail/data/data/bin/qreceipt b/s6/qmail/data/data/bin/qreceipt Binary files differ. diff --git a/s6/qmail/data/data/bin/qsmhook b/s6/qmail/data/data/bin/qsmhook Binary files differ. diff --git a/s6/qmail/data/data/bin/sendmail b/s6/qmail/data/data/bin/sendmail Binary files differ. diff --git a/s6/qmail/data/data/bin/splogger b/s6/qmail/data/data/bin/splogger Binary files differ. diff --git a/s6/qmail/data/data/bin/tcp-env b/s6/qmail/data/data/bin/tcp-env Binary files differ. diff --git a/s6/qmail/data/data/boot/binm1 b/s6/qmail/data/data/boot/binm1 @@ -1,10 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using binmail to deliver messages to /var/spool/mail/$USER by default. -# Using BSD 4.4 binmail interface: /usr/libexec/mail.local -r - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start \ -'|preline -f /usr/libexec/mail.local -r "${SENDER:-MAILER-DAEMON}" -d "$USER"' \ -splogger qmail diff --git a/s6/qmail/data/data/boot/binm1+df b/s6/qmail/data/data/boot/binm1+df @@ -1,11 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using dot-forward to support sendmail-style ~/.forward files. -# Using binmail to deliver messages to /var/spool/mail/$USER by default. -# Using BSD 4.4 binmail interface: /usr/libexec/mail.local -r - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start '|dot-forward .forward -|preline -f /usr/libexec/mail.local -r "${SENDER:-MAILER-DAEMON}" -d "$USER"' \ -splogger qmail diff --git a/s6/qmail/data/data/boot/binm2 b/s6/qmail/data/data/boot/binm2 @@ -1,10 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using binmail to deliver messages to /var/spool/mail/$USER by default. -# Using SVR4 binmail interface: /bin/mail -r - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start \ -'|preline -f /bin/mail -r "${SENDER:-MAILER-DAEMON}" -d "$USER"' \ -splogger qmail diff --git a/s6/qmail/data/data/boot/binm2+df b/s6/qmail/data/data/boot/binm2+df @@ -1,11 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using dot-forward to support sendmail-style ~/.forward files. -# Using binmail to deliver messages to /var/spool/mail/$USER by default. -# Using SVR4 binmail interface: /bin/mail -r - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start '|dot-forward .forward -|preline -f /bin/mail -r "${SENDER:-MAILER-DAEMON}" -d "$USER"' \ -splogger qmail diff --git a/s6/qmail/data/data/boot/binm3 b/s6/qmail/data/data/boot/binm3 @@ -1,10 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using binmail to deliver messages to /var/spool/mail/$USER by default. -# Using V7 binmail interface: /bin/mail -f - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start \ -'|preline -f /bin/mail -f "${SENDER:-MAILER-DAEMON}" -d "$USER"' \ -splogger qmail diff --git a/s6/qmail/data/data/boot/binm3+df b/s6/qmail/data/data/boot/binm3+df @@ -1,11 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using dot-forward to support sendmail-style ~/.forward files. -# Using binmail to deliver messages to /var/spool/mail/$USER by default. -# Using V7 binmail interface: /bin/mail -f - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start '|dot-forward .forward -|preline -f /bin/mail -f "${SENDER:-MAILER-DAEMON}" -d "$USER"' \ -splogger qmail diff --git a/s6/qmail/data/data/boot/home b/s6/qmail/data/data/boot/home @@ -1,7 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using qmail-local to deliver messages to ~/Mailbox by default. - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start ./Mailbox splogger qmail diff --git a/s6/qmail/data/data/boot/home+df b/s6/qmail/data/data/boot/home+df @@ -1,9 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using dot-forward to support sendmail-style ~/.forward files. -# Using qmail-local to deliver messages to ~/Mailbox by default. - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start '|dot-forward .forward -./Mailbox' splogger qmail diff --git a/s6/qmail/data/data/boot/proc b/s6/qmail/data/data/boot/proc @@ -1,7 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using procmail to deliver messages to /var/spool/mail/$USER by default. - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start '|preline procmail' splogger qmail diff --git a/s6/qmail/data/data/boot/proc+df b/s6/qmail/data/data/boot/proc+df @@ -1,9 +0,0 @@ -#!/bin/sh - -# Using splogger to send the log through syslog. -# Using dot-forward to support sendmail-style ~/.forward files. -# Using procmail to deliver messages to /var/spool/mail/$USER by default. - -exec env - PATH="/s6/qmail/data/bin:$PATH" \ -qmail-start '|dot-forward .forward -|preline procmail' splogger qmail diff --git a/s6/qmail/data/data/control/defaultdelivery b/s6/qmail/data/data/control/defaultdelivery @@ -1 +0,0 @@ -./mail/ diff --git a/s6/qmail/data/data/control/defaultdomain b/s6/qmail/data/data/control/defaultdomain @@ -1 +0,0 @@ -josuah.net diff --git a/s6/qmail/data/data/control/locals b/s6/qmail/data/data/control/locals @@ -1 +0,0 @@ -josuah.net diff --git a/s6/qmail/data/data/control/me b/s6/qmail/data/data/control/me @@ -1 +0,0 @@ -josuah.net diff --git a/s6/qmail/data/data/control/plusdomain b/s6/qmail/data/data/control/plusdomain @@ -1 +0,0 @@ -josuah.net diff --git a/s6/qmail/data/data/control/rcpthosts b/s6/qmail/data/data/control/rcpthosts @@ -1 +0,0 @@ -josuahn.net diff --git a/s6/qmail/data/data/doc/FAQ b/s6/qmail/data/data/doc/FAQ @@ -1,709 +0,0 @@ -See http://cr.yp.to/qmail/faq.html for newer FAQs not included in this -document, and http://qmail.org/ for qmail community contributions. - -1. Controlling the appearance of outgoing messages -1.1. How do I set up host masquerading? -1.2. How do I set up user masquerading? -1.3. How do I set up Mail-Followup-To automatically? - -2. Routing outgoing messages -2.1. How do I send local messages to another host? -2.2. How do I set up a null client? -2.3. How do I send outgoing mail through UUCP? -2.4. How do I set up a separate queue for a SLIP/PPP link? -2.5. How do I deal with ``CNAME lookup failed temporarily''? - -3. Routing incoming messages by host -3.1. How do I receive mail for another host name? -3.2. How do I set up a virtual domain? -3.3. How do I set up several virtual domains for one user? - -4. Routing incoming messages by user -4.1. How do I forward unrecognized usernames to another host? -4.2. How do I set up a mailing list? -4.3. How do I use majordomo with qmail? -4.4. How do I use procmail with qmail? -4.5. How do I use elm's filter with qmail? -4.6. How do I create aliases with dots? -4.7. How do I use sendmail's .forward files with qmail? -4.8. How do I use sendmail's /etc/aliases with qmail? -4.9. How do I make qmail defer messages during NFS or NIS outages? -4.10. How do I change which account controls an address? - -5. Setting up servers -5.1. How do I run qmail-smtpd under tcpserver? -5.2. How do I set up qmail-qmtpd? -5.3. How do I set up qmail-pop3d? -5.4. How do I allow selected clients to use this host as a relay? -5.5. How do I fix up messages from broken SMTP clients? -5.6. How do I set up qmail-qmqpd? - -6. Configuring MUAs to work with qmail -6.1. How do I make BSD mail generate a Date with the local time zone? -6.2. How do I make pine work with qmail? -6.3. How do I make MH work with qmail? -6.4. How do I stop Sun's dtcm from hanging? - -7. Managing the mail system -7.1. How do I safely stop qmail-send? -7.2. How do I manually run the queue? -7.3. How do I rejuvenate a message? -7.4. How do I organize a big network? -7.5. How do I back up and restore the queue disk? -7.6. How do I run a supervised copy of qmail? -7.7. How do I avoid syslog? - -8. Miscellany -8.1. How do I tell qmail to do more deliveries at once? -8.2. How do I keep a copy of all incoming and outgoing mail messages? -8.3. How do I switch slowly from sendmail to qmail? - - - -1. Controlling the appearance of outgoing messages - - -1.1. How do I set up host masquerading? All the users on this host, -zippy.af.mil, are users on af.mil. When joe sends a message to fred, the -message should say ``From: joe@af.mil'' and ``To: fred@af.mil'', without -``zippy'' anywhere. - -Answer: echo af.mil > /var/qmail/control/defaulthost; chmod 644 -/var/qmail/control/defaulthost. - - -1.2. How do I set up user masquerading? I'd like my own From lines to -show boss@af.mil rather than god@heaven.af.mil. - -Answer: Add MAILHOST=af.mil and MAILUSER=boss to your environment. To -override From lines supplied by your MUA, add QMAILINJECT=f to your -environment. - - -1.3. How do I set up Mail-Followup-To automatically? When I send a -message to the sos@heaven.af.mil mailing list, I'd like to include -``Mail-Followup-To: sos@heaven.af.mil''. - -Answer: Add QMAILMFTFILE=$HOME/.lists to your environment, and put -sos@heaven.af.mil into ~/.lists. - - - -2. Routing outgoing messages - - -2.1. How do I send local messages to another host? All the mail for -af.mil should be delivered to our disk server, pokey.af.mil. I've set up -an MX from af.mil to pokey.af.mil, but when a user on the af.mil host -sends a message to boss@af.mil, af.mil tries to deliver it locally. How -do I stop that? - -Answer: Remove af.mil from /var/qmail/control/locals. If qmail-send is -running, give it a HUP. Make sure the MX is set up properly before you -do this. Also make sure that pokey can receive mail for af.mil---see -question 3.1. - - -2.2. How do I set up a null client? I'd like zippy.af.mil to -send all mail to bigbang.af.mil. - -Answer: echo :bigbang.af.mil > /var/qmail/control/smtproutes; -chmod 644 /var/qmail/control/smtproutes. Disable local delivery as in -question 2.1. Turn off qmail-smtpd in /etc/inetd.conf. - - -2.3. How do I send outgoing mail through UUCP? I need qmail to send all -outgoing mail via UUCP to my upstream UUCP site, gonzo. - -Answer: Put - - :alias-uucp - -into control/virtualdomains and - - |preline -df /usr/bin/uux - -r -gC - -a"${SENDER:-MAILER-DAEMON}" gonzo!rmail "($DEFAULT@$HOST)" - -(all on one line) into ~alias/.qmail-uucp-default. (For some UUCP -software you will need to use -d instead of -df.) If qmail-send is -running, give it a HUP. - - -2.4. How do I set up a separate queue for a SLIP/PPP link? - -Answer: Use serialmail (http://pobox.com/~djb/serialmail.html). - - -2.5. How do I deal with ``CNAME lookup failed temporarily''? The log -showed that a message was deferred for this reason. Why is qmail doing -CNAME lookups, anyway? - -Answer: The SMTP standard does not permit aliased hostnames, so qmail -has to do a CNAME lookup in DNS for every recipient host. If the -relevant DNS server is down, qmail defers the message. It will try again -soon. - - - -3. Routing incoming messages by host - - -3.1. How do I receive mail for another host name? I'd like our disk -server, pokey.af.mil, to receive mail addressed to af.mil. I've set up -an MX from af.mil to pokey.af.mil, but how do I get pokey to treat -af.mil as a name for the local host? - -Answer: Add af.mil to /var/qmail/control/locals and to -/var/qmail/control/rcpthosts. If qmail-send is running, give it a HUP -(or do svc -h /var/run/qmail if qmail is supervised). - - -3.2. How do I set up a virtual domain? I'd like any mail for -nowhere.mil, including root@nowhere.mil and postmaster@nowhere.mil and -so on, to be delivered to Bob. I've set up the MX already. - -Answer: Put - - nowhere.mil:bob - -into control/virtualdomains. Add nowhere.mil to control/rcpthosts. If -qmail-send is running, give it a HUP (or do svc -h /var/run/qmail if -qmail is supervised). - -Now mail for whatever@nowhere.mil will be delivered locally to -bob-whatever. Bob can set up ~bob/.qmail-default to catch all the -possible addresses, ~bob/.qmail-info to catch info@nowhere.mil, etc. - - -3.3. How do I set up several virtual domains for one user? Bob wants -another virtual domain, everywhere.org, but he wants to handle -nowhere.mil users and everywhere.org users differently. How can we do -that without setting up a second account? - -Answer: Put two lines into control/virtualdomains: - - nowhere.mil:bob-nowhere - everywhere.org:bob-everywhere - -Add nowhere.mil and everywhere.org to control/rcpthosts. If qmail-send -is running, give it a HUP (or do svc -h /var/run/qmail if qmail is -supervised). - -Now Bob can set up separate .qmail-nowhere-* and everywhere-* files. He -can even set up .qmail-nowhere-default and .qmail-everywhere-default. - - - -4. Routing incoming messages by user - - -4.1. How do I forward unrecognized usernames to another host? I'd like -to set up a LUSER_RELAY pointing at bigbang.af.mil. - -Answer: Put - - | forward "$LOCAL"@bigbang.af.mil - -into ~alias/.qmail-default. - - -4.2. How do I set up a mailing list? I'd like me-sos@my.host.name to be -forwarded to a bunch of people. - -Answer: Put a list of addresses into ~me/.qmail-sos, one per line. Then -incoming mail for me-sos will be forwarded to each of those addresses. -You should also touch ~me/.qmail-sos-owner so that bounces come back to -you rather than the original sender. - -Alternative: ezmlm (http://pobox.com/~djb/ezmlm.html) is a modern -mailing list manager, supporting automatic subscriptions, confirmations, -archives, fully automatic bounce handling (including warnings to -subscribers saying which messages they've missed), and more. - - -4.3. How do I use majordomo with qmail? - -Answer: See ftp://ftp.eyrie.org/pub/software/majordomo/mjqmail and -http://www.qmail.org for various methods. majordomo 2.0 is expected to -support qmail directly. - -Beware that majordomo's lists are not crashproof. - - - -4.4. How do I use procmail with qmail? - -Answer: Put - - | preline procmail - -into ~/.qmail. You'll have to use a full path for procmail unless -procmail is in the system's startup PATH. Note that procmail will try to -deliver to /var/spool/mail/$USER by default; to change this, see -INSTALL.mbox. - - -4.5. How do I use elm's filter with qmail? - -Answer: Put - - | preline filter - -into ~/.qmail. You'll have to use a full path for filter unless filter -is in the system's startup PATH. - - -4.6. How do I create aliases with dots? I tried setting up -~alias/.qmail-P.D.Q.Bach, but it doesn't do anything. - -Answer: Use .qmail-p:d:q:bach. Dots are converted to colons, and -uppercase is converted to lowercase. - - -4.7. How do I use sendmail's .forward files with qmail? - -Answer: Install the dot-forward package -(http://pobox.com/~djb/dot-forward.html). - - -4.8. How do I use sendmail's /etc/aliases with qmail? - -Answer: Install the fastforward package -(http://pobox.com/~djb/fastforward.html). - - -4.9. How do I make qmail defer messages during NFS or NIS outages? If -~joe suddenly disappears, I'd like mail for joe to be deferred. - -Answer: Build a qmail-users database, so that qmail no longer checks -home directories and the password database. This takes three steps. -First, put your complete user list (including local and NIS passwords) -into /var/qmail/users/passwd. Second, run - - # qmail-pw2u -h < /var/qmail/users/passwd > /var/qmail/users/assign - -Here -h means that every user must have a home directory; if you happen -to run qmail-pw2u during an NFS outage, it will print an error message -and stop. Third, run - - # qmail-newu - -Make sure to rebuild the database whenever you change your user list. - - -4.10. How do I change which account controls an address? I set up -~alias/.qmail-www, but qmail is looking at ~www/.qmail instead. - -Answer: If you do - - # chown root ~www - -then qmail will no longer consider www to be a user; see qmail-getpw.0. -For more precise control over address assignments, see qmail-users.0. - - - -5. Setting up servers - - -5.1. How do I run qmail-smtpd under tcpserver? inetd is barfing at high -loads, cutting off service for ten-minute stretches. I'd also like -better connection logging. - -Answer: First, install the tcpserver program, part of the ucspi-tcp -package (http://pobox.com/~djb/ucspi-tcp.html). Second, remove the smtp -line from /etc/inetd.conf, and put the line - - tcpserver -u 7770 -g 2108 0 smtp /var/qmail/bin/qmail-smtpd & - -into your system startup files. Replace 7770 with your qmaild uid, and -replace 2108 with your nofiles gid. Don't forget the &. The change will -take effect at your next reboot. - -By default, tcpserver allows at most 40 simultaneous qmail-smtpd -processes. To raise this limit to 400, use tcpserver -c 400. To keep -track of who's connecting and for how long, run (on two lines) - - tcpserver -v -u 7770 -g 2108 0 smtp /var/qmail/bin/qmail-smtpd \ - 2>&1 | /var/qmail/bin/splogger smtpd 3 & - - -5.2. How do I set up qmail-qmtpd? - -Answer: Two steps. First, put a - - qmtp 209/tcp - -line into /etc/services. Second, put (all on one line) - - qmtp stream tcp nowait qmaild - /var/qmail/bin/tcp-env tcp-env /var/qmail/bin/qmail-qmtpd - -into /etc/inetd.conf, and give inetd a HUP. - -If you have tcpserver installed, skip the inetd step, and set up - - tcpserver -u 7770 -g 2108 0 qmtp /var/qmail/bin/qmail-qmtpd & - -replacing 7770 and 2108 with the qmaild uid and nofiles gid. See -question 5.1 for more details on tcpserver. - - -5.3. How do I set up qmail-pop3d? My old POP server works with mbox -delivery; I'd like to switch to maildir delivery. - -Answer: Four steps. First, install the checkpassword program -(http://pobox.com/~djb/checkpwd.html). Second, make sure you have a - - pop3 110/tcp - -line in /etc/services. Third, put (all on one line, including -qmail-popup twice) - - pop3 stream tcp nowait root - /var/qmail/bin/qmail-popup qmail-popup - YOURHOST /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir - -into /etc/inetd.conf, and give inetd a HUP; replace YOURHOST with your -host's fully qualified domain name. Fourth, set up Maildir delivery for -any user who wants to read mail via POP. - -If you have tcpserver installed, skip the inetd step, and set up (on two -lines) - - tcpserver 0 pop3 /var/qmail/bin/qmail-popup YOURHOST \ - /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir & - -replacing YOURHOST with your host's fully qualified domain name. See -question 5.1 for more details on tcpserver. - -Security note: pop3d should be used only within a secure network; -otherwise an eavesdropper can steal passwords. - - -5.4. How do I allow selected clients to use this host as a relay? I see -that qmail-smtpd rejects messages to any host not listed in -control/rcpthosts. - -Answer: Three steps. First, install tcp-wrappers, available separately, -including hosts_options. Second, change your qmail-smtpd line in -inetd.conf to - - smtp stream tcp nowait qmaild /usr/local/bin/tcpd - /var/qmail/bin/tcp-env /var/qmail/bin/qmail-smtpd - -(all on one line) and give inetd a HUP. Third, in tcpd's hosts.allow, -make a line setting the environment variable RELAYCLIENT to the empty -string for the selected clients: - - tcp-env: 1.2.3.4, 1.2.3.5: setenv = RELAYCLIENT - -Here 1.2.3.4 and 1.2.3.5 are the clients' IP addresses. qmail-smtpd -ignores control/rcpthosts when RELAYCLIENT is set. (It also appends -RELAYCLIENT to each envelope recipient address. See question 5.5 for an -application.) - -Alternative procedure, if you are using tcpserver 0.80 or above: Create -/etc/tcp.smtp containing - - 1.2.3.6:allow,RELAYCLIENT="" - 127.:allow,RELAYCLIENT="" - -to allow clients with IP addresses 1.2.3.6 and 127.*. Run - - tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp - -Finally, insert - - -x /etc/tcp.smtp.cdb - -after tcpserver in your qmail-smtpd invocation. - - -5.5. How do I fix up messages from broken SMTP clients? - -Answer: Three steps. First, put - - | bouncesaying 'Permission denied' [ "@$HOST" != "@fixme" ] - | qmail-inject -f "$SENDER" -- "$DEFAULT" - -into ~alias/.qmail-fixup-default. Second, put - - fixme:fixup - -into /var/qmail/control/virtualdomains, and give qmail-send a HUP. -Third, follow the procedure in question 5.4, but set RELAYCLIENT to the -string ``@fixme'': - - tcp-env: 1.2.3.6, 1.2.3.7: setenv = RELAYCLIENT @fixme - -Here 1.2.3.6 and 1.2.3.7 are the clients' IP addresses. If you are using -tcpserver instead of inetd and tcpd, put - - 1.2.3.6:allow,RELAYCLIENT="@fixme" - 1.2.3.7:allow,RELAYCLIENT="@fixme" - -into /etc/tcp.smtp, and run tcprules as in question 5.4. - - -5.6. How do I set up qmail-qmqpd? I'd like to allow fast queueing of -outgoing mail from authorized clients. - -Answer: Make sure you have installed tcpserver 0.80 or above. Create -/etc/qmqp.tcp in tcprules format to allow connections from authorized -hosts. For example, if queueing is allowed from 1.2.3.*: - - 1.2.3.:allow - :deny - -Convert /etc/qmqp.tcp to /etc/qmqp.cdb: - - tcprules /etc/qmqp.cdb /etc/qmqp.tmp < /etc/qmqp.tcp - -Finally, set up - - tcpserver -x /etc/qmqp.cdb -u 7770 -g 2108 0 628 /var/qmail/bin/qmail-qmqpd & - -replacing 7770 and 2108 with the qmaild uid and nofiles gid. See -question 5.1 for more details on tcpserver. - - - -6. Configuring MUAs to work with qmail - - -6.1. How do I make BSD mail generate a Date with the local time zone? -When I send mail, I'd rather use the local time zone than GMT, since -some MUAs don't know how to display Date in the receiver's time zone. - -Answer: Put - - set sendmail=/var/qmail/bin/datemail - -into your .mailrc or your system-wide Mail.rc. Beware that BSD mail is -neither secure nor reliable. - - -6.2. How do I make pine work with qmail? - -Answer: Put - - sendmail-path=/usr/lib/sendmail -oem -oi -t - -into /usr/local/lib/pine.conf. (This will work with sendmail too.) -Beware that pine is neither secure nor reliable. - - -6.3. How do I make MH work with qmail? - -Answer: Put - - postproc: /usr/mh/lib/spost - -into each user's .mh_profile. (This will work with sendmail too.) Beware -that MH is neither secure nor reliable. - - -6.4. How do I stop Sun's dtcm from hanging? - -Answer: There is a novice programming error in dtcm, known as ``failure -to close the output side of the pipe in the child.'' Sun has, at the -time of this writing, not yet provided a patch. Sorry. - - - -7. Managing the mail system - - -7.1. How do I safely stop qmail-send? Back when we were running -sendmail, it was always tricky to kill sendmail without risking the loss -of current deliveries; what should I do with qmail-send? - -Answer: Go ahead and kill the qmail-send process. It will shut down -cleanly. Wait for ``exiting'' to show up in the log. To restart qmail, -run /var/qmail/rc the same way it is run from your system boot scripts, -with the proper PATH, resource limits, etc. - -Alternative, if qmail is supervised: svc -t /var/run/qmail. The -supervise process will kill qmail, wait for it to stop, and restart it. -Use -d instead of -t if you don't want qmail to restart automatically; -to manually restart it, use -u. - - -7.2. How do I manually run the queue? I'd like qmail to try delivering -all the remote messages right now. - -Answer: Give the qmail-send process an ALRM. (Do svc -a /var/run/qmail -if qmail is supervised.) - -You may want to run qmail-tcpok first, to guarantee that qmail-remote -will try all addresses. Normally, if an address fails repeatedly, -qmail-remote leaves it alone for an hour. - - -7.3. How do I rejuvenate a message? Somebody broke into Eric's computer -again; it's going to be down for at least another two days. I know Eric -has been expecting an important message---in fact, I see it sitting here -in /var/qmail/queue/mess/15/26902. It's been in the queue for six days; -how can I make sure it isn't bounced tomorrow? - -Answer: Just touch /var/qmail/queue/info/15/26902. (This is the only -form of queue modification that's safe while qmail is running.) - - -7.4. How do I organize a big network? I have a lot of machines, and I -don't know where to start. - -Answer: First, choose the domain name where your users will receive -mail. This is normally the shortest domain name you control. If you are -in charge of *.movie.edu, you can use addresses like joe@movie.edu. - -Second, choose the machine that will know what to do with different -users at movie.edu. Set up a host name in DNS for this machine: - - mailhost.movie.edu IN A 1.2.3.4 - 4.3.2.1.in-addr.arpa IN PTR mailhost.movie.edu - -Here 1.2.3.4 is the IP address of that machine. - -Third, make a list of machines where mail should end up. For example, if -mail for Bob should end up on Bob's workstation, put Bob's workstation -onto the list. For each of these machines, set up a host name in DNS: - - bobshost.movie.edu IN A 1.2.3.7 - 7.3.2.1.in-addr.arpa IN PTR bobshost.movie.edu - -Fourth, install qmail on bobshost.movie.edu. qmail will automatically -configure itself to accept messages for bob@bobshost.movie.edu and -deliver them to ~bob/Mailbox on bobshost. Do the same for the other -machines where mail should end up. - -Fifth, install qmail on mailhost.movie.edu. Put - - movie.edu:alias-movie - -into control/virtualdomains on mailhost. Then forward bob@movie.edu to -bob@bobshost.movie.edu, by putting - - bob@bobshost.movie.edu - -into ~alias/.qmail-movie-bob. Do the same for other users. - -Sixth, put movie.edu into control/rcpthosts on mailhost.movie.edu, so -that mailhost.movie.edu will accept messages for users at movie.edu. - -Seventh, set up an MX record in DNS to deliver movie.edu messages to -mailhost: - - movie.edu IN MX 10 mailhost.movie.edu - -Eighth, on all your machines, put movie.edu into control/defaulthost. - - -7.5. How do I back up and restore the queue disk? - -Answer: You can't. - -One difficulty is that you can't get a consistent snapshot of the queue -while qmail-send is running. Another difficulty is that messages in the -queue must have filenames that match their inode numbers. - -However, the big problem is that backups---even twice-daily backups--- -are far too unreliable for mail. If your disk dies, there will be very -little overlap between the messages saved in the last backup and the -messages that were lost. - -There are several ways to add real reliability to a mail server. Battery -backups will keep your server alive, letting you park the disk to avoid -a head crash, when the power goes out. Solid-state disks have their own -battery backups. RAID boxes let you replace dead disks without losing -any data. - - -7.6. How do I run a supervised copy of qmail? svc sounds useful. - -Answer: Install daemontools (http://pobox.com/~djb/daemontools.html). -Create a /var/run/qmail directory. Change - - /var/qmail/rc - -to - - supervise /var/run/qmail /var/qmail/rc - -in your boot scripts. Make sure that supervise is in the startup PATH. -Now you can use svc to stop or restart qmail, and svstat to check -whether qmail is running. - - -7.7. How do I avoid syslog? It chews up a lot of CPU time and isn't -reliable. - -Answer: Install daemontools (http://pobox.com/~djb/daemontools.html). -Make a /var/log/qmail directory, owned by qmaill, mode 2700. Do - - qmail-start ./Mailbox /usr/local/bin/accustamp \ - | setuser qmaill /usr/local/bin/cyclog /var/log/qmail & - -in /var/qmail/rc. - -If you are logging tcpserver connections, make a /var/log/smtpd -directory, and use cyclog /var/log/smtpd for tcpserver. You shouldn't -run several copies of cyclog with the same log directory. - -By default, cyclog keeps 10 automatically rotated log files, each -containing up to 100KB of log data. To keep 20 files with 1MB each, use -cyclog -s 1000000 -n 20. - - - -8. Miscellany - - -8.1. How do I tell qmail to do more deliveries at once? It's running -only 20 parallel qmail-remote processes. - -Answer: Decide how many deliveries you want to allow at once. Put that -number into control/concurrencyremote. Restart qmail-send as in question -7.1. If your system has resource limits, make sure you set the -descriptors limit to at least double the concurrency plus 5; otherwise -you'll get lots of unnecessary deferrals whenever a big burst of mail -shows up. Note that qmail also imposes a compile-time concurrency limit, -120 by default; this is set in conf-spawn. - - -8.2. How do I keep a copy of all incoming and outgoing mail messages? - -Answer: Set QUEUE_EXTRA to "Tlog\0" and QUEUE_EXTRALEN to 5 in extra.h. -Recompile qmail. Put ./msg-log into ~alias/.qmail-log. - -You can also use QUEUE_EXTRA to, e.g., record the Message-ID of every -message: run - - | awk '/^$/ { exit } /^[mM][eE][sS][sS][aA][gG][eE]-/ { print }' - -from ~alias/.qmail-log. - - -8.3. How do I switch slowly from sendmail to qmail? I'm thinking of -moving the heaven.af.mil network over to qmail, but first I'd like to -give my users a chance to try out qmail without affecting current -sendmail deliveries. We're using NFS. - -Answer: Find a host in your network, say pc.heaven.af.mil, that isn't -running an SMTP server. (If addresses at pc.heaven.af.mil are used, you -should already have an MX pointing pc.heaven.af.mil to your mail hub.) - -Set up a new MX record pointing lists.heaven.af.mil to pc.heaven.af.mil. -Install qmail on pc.heaven.af.mil. Replace pc with lists in the control -files. Make the qmail man pages available on all your machines. - -Now tell your users about qmail. A user can forward joe@heaven.af.mil to -joe@lists.heaven.af.mil to get ~/Mailbox delivery; he can set up .qmail -files; he can start running his own mailing lists @lists.heaven.af.mil. - -When you're ready to turn sendmail off, you can set up pc.heaven.af.mil -as your new mail hub. Add heaven.af.mil to control/locals, and change -the heaven.af.mil MX to point to pc.heaven.af.mil. Make sure you leave -lists.heaven.af.mil in control/locals so that transition addresses will -continue to work. diff --git a/s6/qmail/data/data/doc/INSTALL b/s6/qmail/data/data/doc/INSTALL @@ -1 +0,0 @@ -See http://lifewithqmail.org/lwq.html diff --git a/s6/qmail/data/data/doc/INSTALL.alias b/s6/qmail/data/data/doc/INSTALL.alias @@ -1,40 +0,0 @@ -qmail lets each user control all addresses of the form user-anything. -Addresses that don't start with a username are controlled by a special -user, alias. Delivery instructions for foo go into ~alias/.qmail-foo; -delivery instructions for user-foo go into ~user/.qmail-foo. See -dot-qmail.0 for the full story. - -qmail doesn't have any built-in support for /etc/aliases. If you have a -big /etc/aliases and you'd like to keep it, install the fastforward -package, available separately. /etc/aliases should already include the -aliases discussed below---Postmaster, MAILER-DAEMON, and root. - -If you don't have a big /etc/aliases, you'll find it easier to use -qmail's native alias mechanism. Here's a checklist of aliases you should -set up right now. - -* Postmaster. You're not an Internet citizen if this address doesn't -work. Simply touch (and chmod 644) ~alias/.qmail-postmaster; any mail -for Postmaster will be delivered to ~alias/Mailbox. - -* MAILER-DAEMON. Not required, but users sometimes respond to bounce -messages. Touch (and chmod 644) ~alias/.qmail-mailer-daemon. - -* root. Under qmail, root never receives mail. Your system may generate -mail messages to root every night; if you don't have an alias for root, -those messages will bounce. (They'll end up double-bouncing to the -postmaster.) Set up an alias for root in ~alias/.qmail-root. .qmail -files are similar to .forward files, but beware that they are strictly -line-oriented---see dot-qmail.0 for details. - -* Other non-user accounts. Under qmail, non-user accounts don't get -mail; ``user'' means a non-root account that owns ~account. Set up -aliases for any non-user accounts that normally receive mail. - -Note that special accounts such as ftp, www, and uucp should always have -home directories owned by root. - -* Default. If you want, you can touch ~alias/.qmail-default to catch -everything else. Beware: this will also catch typos and other addresses -that should probably be bounced instead. It won't catch addresses that -start with a user name---the user can set up his own ~/.qmail-default. diff --git a/s6/qmail/data/data/doc/INSTALL.ctl b/s6/qmail/data/data/doc/INSTALL.ctl @@ -1,38 +0,0 @@ -As you've seen, qmail has essentially no pre-compilation configuration. -You should never have to recompile it unless you want to change the -qmail home directory, usernames, or uids. - -qmail does allow quite a bit of easy post-installation configuration. If -you care how your machine greets other machines via SMTP, for example, -you can put an appropriate line into /var/qmail/control/smtpgreeting. - -But this is all optional---if control/smtpgreeting doesn't exist, qmail -will do something reasonable by default. You shouldn't worry much about -configuration right now. You can always come back and tune things later. - -There's one big exception. You MUST tell qmail your hostname. Just run -the config-fast script: - - # ./config-fast your.full.host.name - -config-fast puts your.full.host.name into control/me. It also puts it -into control/locals and control/rcpthosts, so that qmail will accept -mail for your.full.host.name. - -You can instead use the config script, which looks up your host name in -DNS: - - # ./config - -config also looks up your local IP addresses in DNS to decide which -hosts to accept mail for. - -(Why doesn't qmail do these lookups on the fly? This was a deliberate -design decision. qmail does all its local functions---header rewriting, -checking if a recipient is local, etc.---without talking to the network. -The point is that qmail can continue accepting and delivering local mail -even if your network connection goes down.) - -Next, read through FAQ for information on setting up optional features -like masquerading. If you really want to learn right now what all the -configuration possibilities are, see qmail-control.0. diff --git a/s6/qmail/data/data/doc/INSTALL.ids b/s6/qmail/data/data/doc/INSTALL.ids @@ -1,72 +0,0 @@ -Here's how to set up the qmail groups and the qmail users. - -On some systems there are commands that make this easy. Solaris and -Linux: - - # groupadd nofiles - # useradd -g nofiles -d /var/qmail/alias alias - # useradd -g nofiles -d /var/qmail qmaild - # useradd -g nofiles -d /var/qmail qmaill - # useradd -g nofiles -d /var/qmail qmailp - # groupadd qmail - # useradd -g qmail -d /var/qmail qmailq - # useradd -g qmail -d /var/qmail qmailr - # useradd -g qmail -d /var/qmail qmails - -FreeBSD 2.2: - - # pw groupadd nofiles - # pw useradd alias -g nofiles -d /var/qmail/alias -s /nonexistent - # pw useradd qmaild -g nofiles -d /var/qmail -s /nonexistent - # pw useradd qmaill -g nofiles -d /var/qmail -s /nonexistent - # pw useradd qmailp -g nofiles -d /var/qmail -s /nonexistent - # pw groupadd qmail - # pw useradd qmailq -g qmail -d /var/qmail -s /nonexistent - # pw useradd qmailr -g qmail -d /var/qmail -s /nonexistent - # pw useradd qmails -g qmail -d /var/qmail -s /nonexistent - -BSDI 2.0: - - # addgroup nofiles - # adduser -g nofiles -H/var/qmail/alias -G,,, -s/dev/null -P'*' alias - # adduser -g nofiles -H/var/qmail -G,,, -s/dev/null -P'*' qmaild - # adduser -g nofiles -H/var/qmail -G,,, -s/dev/null -P'*' qmaill - # adduser -g nofiles -H/var/qmail -G,,, -s/dev/null -P'*' qmailp - # addgroup qmail - # adduser -g qmail -H/var/qmail -G,,, -s/dev/null -P'*' qmailq - # adduser -g qmail -H/var/qmail -G,,, -s/dev/null -P'*' qmailr - # adduser -g qmail -H/var/qmail -G,,, -s/dev/null -P'*' qmails - -AIX: - - # mkgroup -A nofiles - # mkuser pgrp=nofiles home=/var/qmail/alias shell=/bin/true alias - # mkuser pgrp=nofiles home=/var/qmail shell=/bin/true qmaild - # mkuser pgrp=nofiles home=/var/qmail shell=/bin/true qmaill - # mkuser pgrp=nofiles home=/var/qmail shell=/bin/true qmailp - # mkgroup -A qmail - # mkuser pgrp=qmail home=/var/qmail shell=/bin/true qmailq - # mkuser pgrp=qmail home=/var/qmail shell=/bin/true qmailr - # mkuser pgrp=qmail home=/var/qmail shell=/bin/true qmails - -On other systems, you will have to edit /etc/group and /etc/passwd -manually. First add two new lines to /etc/group, something like - - qmail:*:2107: - nofiles:*:2108: - -where 2107 and 2108 are different from the other gids in /etc/group. -Next (using vipw) add six new lines to /etc/passwd, something like - - alias:*:7790:2108::/var/qmail/alias:/bin/true - qmaild:*:7791:2108::/var/qmail:/bin/true - qmaill:*:7792:2108::/var/qmail:/bin/true - qmailp:*:7793:2108::/var/qmail:/bin/true - qmailq:*:7794:2107::/var/qmail:/bin/true - qmailr:*:7795:2107::/var/qmail:/bin/true - qmails:*:7796:2107::/var/qmail:/bin/true - -where 7790 through 7796 are _new_ uids, 2107 is the qmail gid, and 2108 -is the nofiles gid. Make sure you use the nofiles gid for qmaild, -qmaill, qmailp, and alias, and the qmail gid for qmailq, qmailr, and -qmails. diff --git a/s6/qmail/data/data/doc/INSTALL.maildir b/s6/qmail/data/data/doc/INSTALL.maildir @@ -1,59 +0,0 @@ -This file points out some reasons that you might want to switch from -mbox format to a new format, maildir. - - -1. The trouble with mbox - -The mbox format---the format of ~user/Mailbox, understood by BSD Mail -and lots of other MUAs---is inherently unreliable. - -Think about it: what happens if the system crashes while a program is -appending a new message to ~user/Mailbox? The message will be truncated. -Even worse, if it was truncated in the middle of a line, it will end up -being merged with the next message! Sure, the mailer understands that it -wasn't successful, so it'll try delivering the message again later, but -it can't fix your corrupted mbox. - -Other formats, such as mh folders, are just as unreliable. - -qmail supports maildir, a crashproof format for incoming mail messages. -maildir is fast and easy for MUAs to use. Even better, maildir works -wonders over NFS---see below. - -I don't want to cram maildir down people's throats, so it's not the -default. Nevertheless, I encourage you to start asking for maildir -versions of your favorite MUAs, and to switch over to maildir as soon as -you can. - - -2. Sun's Network F_ail_u_re System - -Anyone who tells you that mail can be safely delivered in mbox format -over NFS is pulling your leg---as explained above, mbox format is -inherently unreliable even on a single machine. - -Anyway, NFS is the most unreliable computing environment ever invented, -and qmail doesn't even pretend to support mbox over NFS. - -You should switch to maildir, which works fine over NFS without any -locking. You can safely read your mail over NFS if it's in maildir -format. Any number of machines can deliver mail to you at the same time. -(On the other hand, for efficiency, it's better to get NFS out of the -picture---your mail should be delivered on the server that contains your -home directory.) - -Here's how to set up qmail to use maildir for your incoming mail: - - % maildirmake $HOME/Maildir - % echo ./Maildir/ > ~/.qmail - -Make sure you include the trailing slash on Maildir/. - -The system administrator can set up Maildir as the default for everybody -by creating a maildir in the new-user template directory and replacing -./Mailbox with ./Maildir/ in /var/qmail/rc. - -Until your MUA supports maildir, you'll probably want to convert maildir -format to (gaaack) mbox format. I've supplied a maildir2mbox utility -that does the trick, along with some tiny qail and elq and pinq wrappers -that call maildir2mbox before calling Mail or elm or pine. diff --git a/s6/qmail/data/data/doc/INSTALL.mbox b/s6/qmail/data/data/doc/INSTALL.mbox @@ -1,53 +0,0 @@ -The qmail package includes a local delivery agent, qmail-local, which -provides user-controlled mailing lists, cross-host alias loop detection, -and many other important qmail features. - -There's one important difference between qmail-local and binmail: -qmail-local delivers mail by default into ~user/Mailbox, rather than -/var/spool/mail/user. It uses mbox format, with lockf locking on systems -that don't have flock (HP/UX, Solaris), and flock locking otherwise. - -This file explains how to switch your system to ~user/Mailbox. You -aren't required to do this; for further discussion of /var/spool/mail, -and an explanation of how to continue using binmail for local -deliveries, see INSTALL.vsm. - -The basic procedure for switching to ~user/Mailbox is simple: - - * Move each /var/spool/mail/user to ~user/Mailbox. For safety, do - this in single-user mode. - - * As root, set up a symbolic link from /var/spool/mail/user to - ~user/Mailbox for each user. /var/spool/mail should be mode 1777, - so users will not be able to accidentally remove these links. - -A few mail programs are unable to handle symbolic links, so you will -have to configure them to look at ~user/Mailbox directly: - - * procmail: Change SYSTEM_MBOX in config.h and recompile; or, with - recent versions, define MAILSPOOLHOME in src/authenticate.c. - -An alternative to symbolic links is hlfsd. Consult the documentation for -hlfsd if it is included in your operating system. - -If /var/spool/mail is large, you can gain extra speed by configuring -all your mail software to look at ~user/Mailbox directly: - - * Most MUAs: Put ``setenv MAIL $HOME/Mailbox'' in your system-wide - .cshrc and ``MAIL=$HOME/Mailbox; export MAIL'' in your system-wide - .profile. - - * elm: Change "mailbox" to "Mailbox" around line 388 of newmbox.c and - recompile. (elm looks at $MAIL, but without this change elm will - fail if two users try to read mail simultaneously.) - - * pine: Put ``inbox-path=Mailbox'' in your system-wide pine.conf. - (For pine versions more recent than 3.91, see also FAQ 6.2.) - - * qpopper 2.2: Change /.mail to /Mailbox in pop_dropcopy.c and - recompile with -DHOMEDIRMAIL in CFLAGS. - -Some vendors, in a misguided attempt to solve the security problems of -/var/spool/mail, have made all their mail software setgid mail. After -you move the mailboxes, you can---and, for security, should---remove -those setgid-mail bits. diff --git a/s6/qmail/data/data/doc/INSTALL.vsm b/s6/qmail/data/data/doc/INSTALL.vsm @@ -1,50 +0,0 @@ -UNIX has traditionally delivered mail into a central spool directory, -/var/spool/mail. (The original name was /usr/spool/mail; some systems -now use /var/mail.) There are two basic problems with /var/spool/mail: - - * It's slow. On systems with thousands of users, /var/spool/mail has - thousands of entries. A few UNIX systems support fast operations on - large directories, but most don't. - - * It's insecure. Writing code that works safely in a world-writable - directory is not easy. See, for example, CERT advisory 95:02. - -These may not be problems at your site, so you may want to leave your -mailboxes in /var/spool/mail. - -This file explains several ways that you can configure qmail to use -existing /var/spool/mail delivery tools. Please note that I do not vouch -for the security or reliability of any of those tools. - - -1. What to configure - -The qmail system is started from /var/qmail/rc with - - qmail-start ./Mailbox splogger qmail - -The first argument to qmail-start, ./Mailbox, is the default delivery -instruction. You can change it to run a program such as binmail or -procmail. (See dot-qmail.0 for the format of delivery instructions.) - - -2. Using procmail - -You may already have installed procmail for mail filtering. procmail -delivers to /var/spool/mail by default. - -To set up qmail to use procmail, simply copy /var/qmail/boot/proc to -/var/qmail/rc. - -Note that procmail must be in your system's boot PATH; if it isn't, you -will have edit /var/qmail/rc to include the full path. - - -3. Using sendmail's delivery agent - -sendmail uses binmail to deliver to /var/spool/mail. binmail is shipped -with the operating system as /bin/mail or /usr/libexec/mail.local. - -There is some variation in binmail syntax among systems. The most common -interfaces are shown in /var/qmail/boot/binm1, /var/qmail/boot/binm2, -and /var/qmail/boot/binm3. diff --git a/s6/qmail/data/data/doc/PIC.local2alias b/s6/qmail/data/data/doc/PIC.local2alias @@ -1,37 +0,0 @@ - Original message: - - To: help - Hi. - -qmail-inject Fill in the complete envelope and header: - - | (envelope) from joe@heaven.af.mil to help@heaven.af.mil - | From: joe@heaven.af.mil - | To: help@heaven.af.mil - | - | Hi. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, help@heaven.af.mil. - | Is heaven.af.mil in locals? Yes. - | Deliver locally to help@heaven.af.mil. - V - -qmail-lspawn ./Mailbox - - | Look at mailbox name, help. - | Is help listed in qmail-users? No. - | Is there a help account? No. - | Give control of the message to alias. - | Run qmail-local. - V - -qmail-local alias ~alias help - help heaven.af.mil joe@heaven.af.mil ./Mailbox - - Does ~alias/.qmail-help exist? Yes: "john". - Forward message to john. diff --git a/s6/qmail/data/data/doc/PIC.local2ext b/s6/qmail/data/data/doc/PIC.local2ext @@ -1,41 +0,0 @@ - Original message: - - To: fred-sos - Hi. - -qmail-inject Fill in the complete envelope and header: - - | (envelope) from joe@heaven.af.mil to fred-sos@heaven.af.mil - | From: joe@heaven.af.mil - | To: fred-sos@heaven.af.mil - | - | Hi. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, fred-sos@heaven.af.mil. - | Is heaven.af.mil in locals? Yes. - | Deliver locally to fred-sos@heaven.af.mil. - V - -qmail-lspawn ./Mailbox - - | Look at mailbox name, fred-sos. - | Is fred-sos listed in qmail-users? No. - | Is there a fred-sos account? No. - | Is there a fred account? Yes. - | Is fred's uid nonzero? Yes. - | Is ~fred visible to the qmailp user? Yes. - | Is ~fred owned by fred? Yes. - | Give control of the message to fred. - | Run qmail-local. - V - -qmail-local fred ~fred fred-sos - sos heaven.af.mil joe@heaven.af.mil ./Mailbox - - Does ~fred/.qmail-sos exist? Yes: "./Extramail". - Write message to ./Extramail in mbox format. diff --git a/s6/qmail/data/data/doc/PIC.local2local b/s6/qmail/data/data/doc/PIC.local2local @@ -1,40 +0,0 @@ - Original message: - - To: fred - Hi. - -qmail-inject Fill in the complete envelope and header: - - | (envelope) from joe@heaven.af.mil to fred@heaven.af.mil - | From: joe@heaven.af.mil - | To: fred@heaven.af.mil - | - | Hi. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, fred@heaven.af.mil. - | Is heaven.af.mil in locals? Yes. - | Deliver locally to fred@heaven.af.mil. - V - -qmail-lspawn ./Mailbox - - | Look at mailbox name, fred. - | Is fred listed in qmail-users? No. - | Is there a fred account? Yes. - | Is fred's uid nonzero? Yes. - | Is ~fred visible to the qmailp user? Yes. - | Is ~fred owned by fred? Yes. - | Give control of the message to fred. - | Run qmail-local. - V - -qmail-local fred ~fred fred '' '' heaven.af.mil joe@heaven.af.mil ./Mailbox - - Does ~fred/.qmail exist? No. - Write message to ./Mailbox in mbox format. diff --git a/s6/qmail/data/data/doc/PIC.local2rem b/s6/qmail/data/data/doc/PIC.local2rem @@ -1,38 +0,0 @@ - Original message: - - To: bill@irs.gov - Hi. - -qmail-inject Fill in the complete envelope and header: - - | (envelope) from joe@heaven.af.mil to bill@irs.gov - | From: joe@heaven.af.mil - | To: bill@irs.gov - | - | Hi. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, bill@irs.gov. - | Is irs.gov in locals? No. - | Is bill@irs.gov in virtualdomains? No. - | Is irs.gov in virtualdomains? No. - | Is .gov in virtualdomains? No. - | Deliver remotely to bill@irs.gov. - V - -qmail-rspawn Run qmail-remote. - - | - V - -qmail-remote Look at host name, irs.gov. - Is irs.gov listed in smtproutes? No. - Look up DNS MX/A for irs.gov and connect to it by SMTP: - - MAIL FROM:<joe@heaven.af.mil> - RCPT TO:<bill@irs.gov> diff --git a/s6/qmail/data/data/doc/PIC.local2virt b/s6/qmail/data/data/doc/PIC.local2virt @@ -1,44 +0,0 @@ - Original message: - - To: dude@tommy.gov - Hi. - -qmail-inject Fill in the complete envelope and header: - - | (envelope) from joe@heaven.af.mil to dude@tommy.gov - | From: joe@heaven.af.mil - | To: dude@tommy.gov - | - | Hi. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, dude@tommy.gov. - | Is tommy.gov in locals? No. - | Is dude@tommy.gov in virtualdomains? No. - | Is tommy.gov in virtualdomains? Yes: "tommy.gov:fred". - | Deliver locally to fred-dude@tommy.gov. - V - -qmail-lspawn ./Mailbox - - | Look at mailbox name, fred-dude. - | Is fred-dude listed in qmail-users? No. - | Is there a fred-dude account? No. - | Is there a fred account? Yes. - | Is fred's uid nonzero? Yes. - | Is ~fred visible to the qmailp user? Yes. - | Is ~fred owned by fred? Yes. - | Give control of the message to fred. - | Run qmail-local. - V - -qmail-local fred ~fred fred-dude - dude tommy.gov joe@heaven.af.mil ./Mailbox - - Does ~fred/.qmail-dude exist? No. - Does ~fred/.qmail-default exist? Yes: "./Mail.tommy". - Write message to ./Mail.tommy in mbox format. diff --git a/s6/qmail/data/data/doc/PIC.nullclient b/s6/qmail/data/data/doc/PIC.nullclient @@ -1,38 +0,0 @@ - Original message: - - To: bill@irs.gov - Hi. - -qmail-inject Fill in the complete envelope and header: - - | (envelope) from joe@heaven.af.mil to bill@irs.gov - | From: joe@heaven.af.mil - | To: bill@irs.gov - | - | Hi. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, bill@irs.gov. - | Is irs.gov in locals? No. - | Is bill@irs.gov in virtualdomains? No. - | Is irs.gov in virtualdomains? No. - | Is .gov in virtualdomains? No. - | Deliver remotely to bill@irs.gov. - V - -qmail-rspawn Run qmail-remote. - - | - V - -qmail-remote Look at host name, irs.gov. - Is irs.gov listed in smtproutes? Yes: ":bigbang.af.mil". - Look up DNS A for bigbang.af.mil and connect by SMTP: - - MAIL FROM:<joe@heaven.af.mil> - RCPT TO:<bill@irs.gov> diff --git a/s6/qmail/data/data/doc/PIC.relaybad b/s6/qmail/data/data/doc/PIC.relaybad @@ -1,8 +0,0 @@ -qmail-smtpd Receive message by SMTP from another host: - - MAIL FROM:<spammer@aol.com> - RCPT TO:<bill@irs.gov> - - Is $RELAYCLIENT set? No. - Is irs.gov in rcpthosts? No. - Reject RCPT. diff --git a/s6/qmail/data/data/doc/PIC.relaygood b/s6/qmail/data/data/doc/PIC.relaygood @@ -1,33 +0,0 @@ -qmail-smtpd Receive message by SMTP from another host: - - | MAIL FROM:<joe@heaven.af.mil> - | RCPT TO:<bill@irs.gov> - | - | Is $RELAYCLIENT set? Yes: "". - | Accept RCPT. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, bill@irs.gov. - | Is irs.gov in locals? No. - | Is bill@irs.gov in virtualdomains? No. - | Is irs.gov in virtualdomains? No. - | Is .gov in virtualdomains? No. - | Deliver remotely to bill@irs.gov. - V - -qmail-rspawn Run qmail-remote. - - | - V - -qmail-remote Look at host name, irs.gov. - Is irs.gov listed in smtproutes? No. - Look up DNS MX/A for irs.gov and connect to it by SMTP: - - MAIL FROM:<joe@heaven.af.mil> - RCPT TO:<bill@irs.gov> diff --git a/s6/qmail/data/data/doc/PIC.rem2local b/s6/qmail/data/data/doc/PIC.rem2local @@ -1,36 +0,0 @@ -qmail-smtpd Receive message by SMTP from another host: - - | MAIL FROM:<bill@irs.gov> - | RCPT TO:<joe@heaven.af.mil> - | - | Is $RELAYCLIENT set? No. - | Is heaven.af.mil in rcpthosts? Yes. - | Accept RCPT. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, joe@heaven.af.mil. - | Is heaven.af.mil in locals? Yes. - | Deliver locally to joe@heaven.af.mil. - V - -qmail-lspawn ./Mailbox - - | Look at mailbox name, joe. - | Is joe listed in qmail-users? No. - | Is there a joe account? Yes. - | Is joe's uid nonzero? Yes. - | Is ~joe visible to the qmailp user? Yes. - | Is ~joe owned by joe? Yes. - | Give control of the message to joe. - | Run qmail-local. - V - -qmail-local joe ~joe joe '' '' heaven.af.mil bill@irs.gov ./Mailbox - - Does ~joe/.qmail exist? No. - Write message to ./Mailbox in mbox format. diff --git a/s6/qmail/data/data/doc/REMOVE.binmail b/s6/qmail/data/data/doc/REMOVE.binmail @@ -1,16 +0,0 @@ -Here's how to remove binmail from your system. Don't do this if you have -configured qmail to use binmail for local delivery. - - -1. Find the binmail binary on your system: /usr/libexec/mail.local if - that exists, otherwise /bin/mail. - -2. Remove permissions from the binmail binary: - # chmod 0 /usr/libexec/mail.local - -3. If the binmail binary was /bin/mail, make sure that ``mail'' still - invokes a usable mailer. Under SVR4 you may want to link mail to - mailx. - -4. Comment out the comsat line in /etc/inetd.conf, and kill -HUP your - inetd. diff --git a/s6/qmail/data/data/doc/REMOVE.sendmail b/s6/qmail/data/data/doc/REMOVE.sendmail @@ -1,28 +0,0 @@ -Here's how to remove sendmail from your system. - -1. Find sendmail in your boot scripts. It's usually in either /etc/rc or - /etc/init.d/sendmail. It looks like - sendmail -bd -q15m - -q15m means that it should run the queue every 15 minutes; you may - see a different number. Comment out this line. - -2. Kill the sendmail daemon. You should first kill -STOP the daemon; if - any children are running, you should kill -CONT, wait, kill -STOP - again, and repeat ad nauseam. If there aren't any children, kill - -TERM and then kill -CONT. - -3. Check whether you have any messages in the sendmail queue, - /var/spool/mqueue. If you do, you will have to try flushing them with - sendmail.bak -q. If necessary, wait a while and run sendmail.bak -q - again. Repeat until the queue is empty. This may take several days. - -4. Remove the setuid bit on the sendmail binary, to prevent local users - from gaining extra privileges through sendmail's security holes. The - binary may be at several different locations: - # chmod 0 /usr/lib/sendmail - # chmod 0 /usr/sbin/sendmail - # chmod 0 /usr/lib/sendmail.mx - -5. Move the sendmail binary out of the way: - # mv /usr/lib/sendmail /usr/lib/sendmail.bak - # mv /usr/sbin/sendmail /usr/sbin/sendmail.bak diff --git a/s6/qmail/data/data/doc/SENDMAIL b/s6/qmail/data/data/doc/SENDMAIL @@ -1,76 +0,0 @@ -This document explains what you, as a user, will notice when the system -switches from sendmail to qmail. - -This is a global document, part of the qmail package, not reflecting the -decisions made by your system administrator. For details on - - * which local delivery agent qmail is configured to use, - * whether qmail is configured to use dot-forward, - * whether ezmlm is installed, - * whether fastforward is installed, and - * all other local configuration features, - -see your local sendmail-qmail upgrade announcement (which your system -administrator may have placed into /var/qmail/doc/ANNOUNCE). - - ---- Mailbox location - -If your system administrator has configured qmail to use binmail for -local deliveries, your mailbox will be in /var/spool/mail/you, just as -it was under sendmail. - -If your system administrator has configured qmail to use qmail-local for -local deliveries, your mailbox will be moved to ~you/Mailbox. There is a -symbolic link from /var/spool/mail/you to ~you/Mailbox, so your mail -reader will find the mailbox at its new location. - - ---- Loop control - -qmail-local automatically adds a Delivered-To field at the top of every -delivered message. It uses Delivered-To to prevent mail forwarding -loops, including cross-host mailing-list loops. - - ---- Outgoing messages - -qmail lets you use environment variables to control the appearance of -your outgoing mail, supplementing the features offered by your MUA. For -example, qmail-inject will set up Mail-Followup-To for you automatically -if you tell it which mailing lists you are subscribed to. See -qmail-inject(8) for a complete list of features. - -If you're at (say) sun.ee.movie.edu, qmail lets you type joe@mac for -joe@mac.ee.movie.edu, and joe@mac+ for joe@mac.movie.edu without the ee. -sendmail has a different interpretation of hostnames without dots. - - ---- Forwarding and mailing lists - -qmail gives you the power to set up your own mailing lists without -pestering your system administrator. - -Under qmail, you are in charge of all addresses of the form -you-anything. The delivery of you-anything is controlled by -~you/.qmail-anything, a file in your home directory. - -For example, if you want to set up a bug-of-the-month-club mailing list, -you can put a list of addresses into ~you/.qmail-botmc. Any mail to -you-botmc will be forwarded to all of those addresses. Mail directly to -you is controlled by ~you/.qmail. You can even set up a catch-all, -~you/.qmail-default, to handle unknown you- addresses. - -See dot-qmail(5) for the complete story. Beware that the syntax of -.qmail is different from the syntax of sendmail's .forward file. - -If your system administrator has configured qmail to use the dot-forward -compatibility tool, you can put forwarding addresses (and programs) into -.forward the same way you did with sendmail. - -If your system administrator has installed ezmlm, you can use ezmlm-make -to instantly set up a professional-quality mailing list, handling -subscriptions and archives automatically. - -If your system administrator has installed fastforward, you can easily -manage a large database of forwarding addresses. diff --git a/s6/qmail/data/data/doc/TEST.deliver b/s6/qmail/data/data/doc/TEST.deliver @@ -1,82 +0,0 @@ -You can do several tests of qmail delivery without setting up qmail to -accept messages through SMTP or through /usr/lib/sendmail: - -1. After you start qmail, look for a - qmail: status: local 0/10 remote 0/20 - line in syslog. qmail-send always prints either ``cannot start'' or - ``status''. (The big number is a splogger timestamp.) - -2. Do a ps and look for the qmail daemons. There should be four of - them, all idle: qmail-send, running as qmails; qmail-lspawn, running - as root; qmail-rspawn, running as qmailr; and qmail-clean, running - as qmailq. You will also see splogger, running as qmaill. - -3. Local-local test: Send yourself an empty message. (Replace ``me'' - with your username. Make sure to include the ``to:'' colon.) - % echo to: me | /var/qmail/bin/qmail-inject - The message will show up immediately in your mailbox, and syslog - will show something like this: - qmail: new msg 53 - qmail: info msg 53: bytes 246 from <me@domain> qp 20345 uid 666 - qmail: starting delivery 1: msg 53 to local me@domain - qmail: status: local 1/10 remote 0/20 - qmail: delivery 1: success: did_1+0+0/ - qmail: status: local 0/10 remote 0/20 - qmail: end msg 53 - (53 is an inode number; 20345 is a process ID; your numbers will - probably be different.) - -4. Local-error test: Send a message to a nonexistent local address. - % echo to: nonexistent | /var/qmail/bin/qmail-inject - qmail: new msg 53 - qmail: info msg 53: bytes 246 from <me@domain> qp 20351 uid 666 - qmail: starting delivery 2: msg 53 to local nonexistent@domain - qmail: status: local 1/10 remote 0/20 - qmail: delivery 2: failure: No_such_address.__#5.1.1_/ - qmail: status: local 0/10 remote 0/20 - qmail: bounce msg 53 qp 20357 - qmail: end msg 53 - qmail: new msg 54 - qmail: info msg 54: bytes 743 from <> qp 20357 uid 666 - qmail: starting delivery 3: msg 54 to local me@domain - qmail: status: local 1/10 remote 0/20 - qmail: delivery 3: success: did_1+0+0/ - qmail: status: local 0/10 remote 0/20 - qmail: end msg 54 - You will now have a bounce message in your mailbox. - -5. Local-remote test: Send an empty message to your account on another - machine. - % echo to: me@wherever | /var/qmail/bin/qmail-inject - qmail: new msg 53 - qmail: info msg 53: bytes 246 from <me@domain> qp 20372 uid 666 - qmail: starting delivery 4: msg 53 to remote me@wherever - qmail: status: local 0/10 remote 1/20 - qmail: delivery 4: success: 1.2.3.4_accepted_message./... - qmail: status: local 0/10 remote 0/20 - qmail: end msg 53 - There will be a pause between ``starting delivery'' and ``success''; - SMTP is slow. Check that the message is in your mailbox on the other - machine. - -6. Local-postmaster test: Send mail to postmaster, any capitalization. - % echo to: POSTmaster | /var/qmail/bin/qmail-inject - Look for the message in the alias mailbox, normally ~alias/Mailbox. - -7. Double-bounce test: Send a message with a completely bad envelope. - % /var/qmail/bin/qmail-inject -f nonexistent - To: unknownuser - Subject: testing - - This is a test. This is only a test. - % - (Use end-of-file, not dot, to end the message.) Look for the double - bounce in the alias mailbox. - -8. Group membership test: - % cat > ~me/.qmail-groups - |groups >> MYGROUPS; exit 0 - % /var/qmail/bin/qmail-inject me-groups < /dev/null - % cat ~me/MYGROUPS - MYGROUPS will show your normal gid and nothing else. (Under Solaris, - make sure to use /usr/ucb/groups; /usr/bin/groups is broken.) diff --git a/s6/qmail/data/data/doc/TEST.receive b/s6/qmail/data/data/doc/TEST.receive @@ -1,41 +0,0 @@ -You can do several tests of messages entering the qmail system: - -1. SMTP server test: Forge some mail locally via SMTP. Replace ``me'' - with your username and ``domain'' with your host's name. - % telnet 127.0.0.1 25 - Trying 127.0.0.1... - Connected to 127.0.0.1. - Escape character is '^]'. - 220 domain ESMTP - helo dude - 250 domain - mail <me@domain> - 250 ok - rcpt <me@domain> - 250 ok - data - 354 go ahead - Subject: testing - - This is a test. - . - 250 ok 812345679 qp 12345 - quit - 221 domain - Connection closed by foreign host. - % - Look for the message in your mailbox. (Note for programmers: Most - SMTP servers need more text after MAIL and RCPT. See RFC 821.) - -2. Remote-local test: Send yourself some mail from another machine. - Look for the message in your mailbox. - -3. Remote-error test: Send some mail from another machine to - nonexistent@domain. Look for a bounce message in the remote mailbox. - -4. UA test: Try sending mail, first to a local account, then to a - remote account, with your normal user agent. - -5. Remote-postmaster test: Send mail from another machine to - PoStMaStEr@domain. Look for the message in the alias mailbox, - normally ~alias/Mailbox. diff --git a/s6/qmail/data/data/doc/UPGRADE b/s6/qmail/data/data/doc/UPGRADE @@ -1,66 +0,0 @@ -SAVE COPIES OF YOUR OUTGOING MAIL! Like any other piece of software (and -information generally), the qmail system comes with NO WARRANTY. It's -much more secure and reliable than sendmail, but that's not saying much. - - -Here's how to upgrade to netqmail 1.05. This procedure will overwrite the -old qmail binaries. Furthermore, it may begin delivering messages from -the queue before you have had a chance to test it. - - -WARNING for upgrades from 1.00 or 1.01: qlist has been split into a -separate package. You can obtain it from http://pobox.com/~djb/qlist.html -if you have any users who need it. - -WARNING for upgrades from 1.01: recipientmap is gone. The virtualdomains -mechanism has been expanded to support virtual users. - - -Before starting, compare conf* to your old conf*, and make any necessary -changes. You can copy conf* from 1.02 or 1.03. - - -How to install: - - 1. Compile the programs and create the formatted man pages: - # make it man - - 2. Inform your users that mail will not be accepted for a few minutes. - - 3. Disable deliveries by killing your old qmail-send. Wait for it to - print ``exiting'' in the log. - - 4. Disable SMTP service by commenting out the smtp line in inetd.conf; - kill -HUP your inetd. (If you are using tcpserver, simply kill -STOP - your tcpserver. If you are running a QMTP server, disable that too.) - Wait for current qmail-smtpd processes to die. - - 5. Install the new binaries and man pages: - # make setup check - - 6. If your boot scripts are using qmail-start instead of /var/qmail/rc: - Copy /var/qmail/boot/home to /var/qmail/rc. (Use home+df instead if - you have installed dot-forward; use proc or proc+df if you are using - procmail by default for local deliveries.) Compare /var/qmail/rc to - your qmail-start boot line, and edit /var/qmail/rc if necessary. - Replace your qmail-start boot line with - csh -cf '/var/qmail/rc &' - - 7. Reenable deliveries: - # csh -cf '/var/qmail/rc &' - - 8. Read TEST.deliver. - - 9. Reenable SMTP service by restoring the smtp line in inetd.conf; kill - -HUP your inetd. (If you are using tcpserver, simply kill -CONT your - tcpserver. If you are running a QMTP server, reenable that too.) - -10. Read TEST.receive. - - -That's it! To report success: - % ( echo 'First M. Last'; cat `cat SYSDEPS` ) | mail djb-qst@cr.yp.to -Replace First M. Last with your name. - -If you have questions about qmail, join the qmail mailing list; see -http://pobox.com/~djb/qmail.html. diff --git a/s6/qmail/data/data/queue/lock/sendmutex b/s6/qmail/data/data/queue/lock/sendmutex diff --git a/s6/qmail/data/data/queue/lock/tcpto b/s6/qmail/data/data/queue/lock/tcpto Binary files differ. diff --git a/s6/qmail/data/doc/FAQ b/s6/qmail/data/doc/FAQ @@ -1,709 +0,0 @@ -See http://cr.yp.to/qmail/faq.html for newer FAQs not included in this -document, and http://qmail.org/ for qmail community contributions. - -1. Controlling the appearance of outgoing messages -1.1. How do I set up host masquerading? -1.2. How do I set up user masquerading? -1.3. How do I set up Mail-Followup-To automatically? - -2. Routing outgoing messages -2.1. How do I send local messages to another host? -2.2. How do I set up a null client? -2.3. How do I send outgoing mail through UUCP? -2.4. How do I set up a separate queue for a SLIP/PPP link? -2.5. How do I deal with ``CNAME lookup failed temporarily''? - -3. Routing incoming messages by host -3.1. How do I receive mail for another host name? -3.2. How do I set up a virtual domain? -3.3. How do I set up several virtual domains for one user? - -4. Routing incoming messages by user -4.1. How do I forward unrecognized usernames to another host? -4.2. How do I set up a mailing list? -4.3. How do I use majordomo with qmail? -4.4. How do I use procmail with qmail? -4.5. How do I use elm's filter with qmail? -4.6. How do I create aliases with dots? -4.7. How do I use sendmail's .forward files with qmail? -4.8. How do I use sendmail's /etc/aliases with qmail? -4.9. How do I make qmail defer messages during NFS or NIS outages? -4.10. How do I change which account controls an address? - -5. Setting up servers -5.1. How do I run qmail-smtpd under tcpserver? -5.2. How do I set up qmail-qmtpd? -5.3. How do I set up qmail-pop3d? -5.4. How do I allow selected clients to use this host as a relay? -5.5. How do I fix up messages from broken SMTP clients? -5.6. How do I set up qmail-qmqpd? - -6. Configuring MUAs to work with qmail -6.1. How do I make BSD mail generate a Date with the local time zone? -6.2. How do I make pine work with qmail? -6.3. How do I make MH work with qmail? -6.4. How do I stop Sun's dtcm from hanging? - -7. Managing the mail system -7.1. How do I safely stop qmail-send? -7.2. How do I manually run the queue? -7.3. How do I rejuvenate a message? -7.4. How do I organize a big network? -7.5. How do I back up and restore the queue disk? -7.6. How do I run a supervised copy of qmail? -7.7. How do I avoid syslog? - -8. Miscellany -8.1. How do I tell qmail to do more deliveries at once? -8.2. How do I keep a copy of all incoming and outgoing mail messages? -8.3. How do I switch slowly from sendmail to qmail? - - - -1. Controlling the appearance of outgoing messages - - -1.1. How do I set up host masquerading? All the users on this host, -zippy.af.mil, are users on af.mil. When joe sends a message to fred, the -message should say ``From: joe@af.mil'' and ``To: fred@af.mil'', without -``zippy'' anywhere. - -Answer: echo af.mil > /var/qmail/control/defaulthost; chmod 644 -/var/qmail/control/defaulthost. - - -1.2. How do I set up user masquerading? I'd like my own From lines to -show boss@af.mil rather than god@heaven.af.mil. - -Answer: Add MAILHOST=af.mil and MAILUSER=boss to your environment. To -override From lines supplied by your MUA, add QMAILINJECT=f to your -environment. - - -1.3. How do I set up Mail-Followup-To automatically? When I send a -message to the sos@heaven.af.mil mailing list, I'd like to include -``Mail-Followup-To: sos@heaven.af.mil''. - -Answer: Add QMAILMFTFILE=$HOME/.lists to your environment, and put -sos@heaven.af.mil into ~/.lists. - - - -2. Routing outgoing messages - - -2.1. How do I send local messages to another host? All the mail for -af.mil should be delivered to our disk server, pokey.af.mil. I've set up -an MX from af.mil to pokey.af.mil, but when a user on the af.mil host -sends a message to boss@af.mil, af.mil tries to deliver it locally. How -do I stop that? - -Answer: Remove af.mil from /var/qmail/control/locals. If qmail-send is -running, give it a HUP. Make sure the MX is set up properly before you -do this. Also make sure that pokey can receive mail for af.mil---see -question 3.1. - - -2.2. How do I set up a null client? I'd like zippy.af.mil to -send all mail to bigbang.af.mil. - -Answer: echo :bigbang.af.mil > /var/qmail/control/smtproutes; -chmod 644 /var/qmail/control/smtproutes. Disable local delivery as in -question 2.1. Turn off qmail-smtpd in /etc/inetd.conf. - - -2.3. How do I send outgoing mail through UUCP? I need qmail to send all -outgoing mail via UUCP to my upstream UUCP site, gonzo. - -Answer: Put - - :alias-uucp - -into control/virtualdomains and - - |preline -df /usr/bin/uux - -r -gC - -a"${SENDER:-MAILER-DAEMON}" gonzo!rmail "($DEFAULT@$HOST)" - -(all on one line) into ~alias/.qmail-uucp-default. (For some UUCP -software you will need to use -d instead of -df.) If qmail-send is -running, give it a HUP. - - -2.4. How do I set up a separate queue for a SLIP/PPP link? - -Answer: Use serialmail (http://pobox.com/~djb/serialmail.html). - - -2.5. How do I deal with ``CNAME lookup failed temporarily''? The log -showed that a message was deferred for this reason. Why is qmail doing -CNAME lookups, anyway? - -Answer: The SMTP standard does not permit aliased hostnames, so qmail -has to do a CNAME lookup in DNS for every recipient host. If the -relevant DNS server is down, qmail defers the message. It will try again -soon. - - - -3. Routing incoming messages by host - - -3.1. How do I receive mail for another host name? I'd like our disk -server, pokey.af.mil, to receive mail addressed to af.mil. I've set up -an MX from af.mil to pokey.af.mil, but how do I get pokey to treat -af.mil as a name for the local host? - -Answer: Add af.mil to /var/qmail/control/locals and to -/var/qmail/control/rcpthosts. If qmail-send is running, give it a HUP -(or do svc -h /var/run/qmail if qmail is supervised). - - -3.2. How do I set up a virtual domain? I'd like any mail for -nowhere.mil, including root@nowhere.mil and postmaster@nowhere.mil and -so on, to be delivered to Bob. I've set up the MX already. - -Answer: Put - - nowhere.mil:bob - -into control/virtualdomains. Add nowhere.mil to control/rcpthosts. If -qmail-send is running, give it a HUP (or do svc -h /var/run/qmail if -qmail is supervised). - -Now mail for whatever@nowhere.mil will be delivered locally to -bob-whatever. Bob can set up ~bob/.qmail-default to catch all the -possible addresses, ~bob/.qmail-info to catch info@nowhere.mil, etc. - - -3.3. How do I set up several virtual domains for one user? Bob wants -another virtual domain, everywhere.org, but he wants to handle -nowhere.mil users and everywhere.org users differently. How can we do -that without setting up a second account? - -Answer: Put two lines into control/virtualdomains: - - nowhere.mil:bob-nowhere - everywhere.org:bob-everywhere - -Add nowhere.mil and everywhere.org to control/rcpthosts. If qmail-send -is running, give it a HUP (or do svc -h /var/run/qmail if qmail is -supervised). - -Now Bob can set up separate .qmail-nowhere-* and everywhere-* files. He -can even set up .qmail-nowhere-default and .qmail-everywhere-default. - - - -4. Routing incoming messages by user - - -4.1. How do I forward unrecognized usernames to another host? I'd like -to set up a LUSER_RELAY pointing at bigbang.af.mil. - -Answer: Put - - | forward "$LOCAL"@bigbang.af.mil - -into ~alias/.qmail-default. - - -4.2. How do I set up a mailing list? I'd like me-sos@my.host.name to be -forwarded to a bunch of people. - -Answer: Put a list of addresses into ~me/.qmail-sos, one per line. Then -incoming mail for me-sos will be forwarded to each of those addresses. -You should also touch ~me/.qmail-sos-owner so that bounces come back to -you rather than the original sender. - -Alternative: ezmlm (http://pobox.com/~djb/ezmlm.html) is a modern -mailing list manager, supporting automatic subscriptions, confirmations, -archives, fully automatic bounce handling (including warnings to -subscribers saying which messages they've missed), and more. - - -4.3. How do I use majordomo with qmail? - -Answer: See ftp://ftp.eyrie.org/pub/software/majordomo/mjqmail and -http://www.qmail.org for various methods. majordomo 2.0 is expected to -support qmail directly. - -Beware that majordomo's lists are not crashproof. - - - -4.4. How do I use procmail with qmail? - -Answer: Put - - | preline procmail - -into ~/.qmail. You'll have to use a full path for procmail unless -procmail is in the system's startup PATH. Note that procmail will try to -deliver to /var/spool/mail/$USER by default; to change this, see -INSTALL.mbox. - - -4.5. How do I use elm's filter with qmail? - -Answer: Put - - | preline filter - -into ~/.qmail. You'll have to use a full path for filter unless filter -is in the system's startup PATH. - - -4.6. How do I create aliases with dots? I tried setting up -~alias/.qmail-P.D.Q.Bach, but it doesn't do anything. - -Answer: Use .qmail-p:d:q:bach. Dots are converted to colons, and -uppercase is converted to lowercase. - - -4.7. How do I use sendmail's .forward files with qmail? - -Answer: Install the dot-forward package -(http://pobox.com/~djb/dot-forward.html). - - -4.8. How do I use sendmail's /etc/aliases with qmail? - -Answer: Install the fastforward package -(http://pobox.com/~djb/fastforward.html). - - -4.9. How do I make qmail defer messages during NFS or NIS outages? If -~joe suddenly disappears, I'd like mail for joe to be deferred. - -Answer: Build a qmail-users database, so that qmail no longer checks -home directories and the password database. This takes three steps. -First, put your complete user list (including local and NIS passwords) -into /var/qmail/users/passwd. Second, run - - # qmail-pw2u -h < /var/qmail/users/passwd > /var/qmail/users/assign - -Here -h means that every user must have a home directory; if you happen -to run qmail-pw2u during an NFS outage, it will print an error message -and stop. Third, run - - # qmail-newu - -Make sure to rebuild the database whenever you change your user list. - - -4.10. How do I change which account controls an address? I set up -~alias/.qmail-www, but qmail is looking at ~www/.qmail instead. - -Answer: If you do - - # chown root ~www - -then qmail will no longer consider www to be a user; see qmail-getpw.0. -For more precise control over address assignments, see qmail-users.0. - - - -5. Setting up servers - - -5.1. How do I run qmail-smtpd under tcpserver? inetd is barfing at high -loads, cutting off service for ten-minute stretches. I'd also like -better connection logging. - -Answer: First, install the tcpserver program, part of the ucspi-tcp -package (http://pobox.com/~djb/ucspi-tcp.html). Second, remove the smtp -line from /etc/inetd.conf, and put the line - - tcpserver -u 7770 -g 2108 0 smtp /var/qmail/bin/qmail-smtpd & - -into your system startup files. Replace 7770 with your qmaild uid, and -replace 2108 with your nofiles gid. Don't forget the &. The change will -take effect at your next reboot. - -By default, tcpserver allows at most 40 simultaneous qmail-smtpd -processes. To raise this limit to 400, use tcpserver -c 400. To keep -track of who's connecting and for how long, run (on two lines) - - tcpserver -v -u 7770 -g 2108 0 smtp /var/qmail/bin/qmail-smtpd \ - 2>&1 | /var/qmail/bin/splogger smtpd 3 & - - -5.2. How do I set up qmail-qmtpd? - -Answer: Two steps. First, put a - - qmtp 209/tcp - -line into /etc/services. Second, put (all on one line) - - qmtp stream tcp nowait qmaild - /var/qmail/bin/tcp-env tcp-env /var/qmail/bin/qmail-qmtpd - -into /etc/inetd.conf, and give inetd a HUP. - -If you have tcpserver installed, skip the inetd step, and set up - - tcpserver -u 7770 -g 2108 0 qmtp /var/qmail/bin/qmail-qmtpd & - -replacing 7770 and 2108 with the qmaild uid and nofiles gid. See -question 5.1 for more details on tcpserver. - - -5.3. How do I set up qmail-pop3d? My old POP server works with mbox -delivery; I'd like to switch to maildir delivery. - -Answer: Four steps. First, install the checkpassword program -(http://pobox.com/~djb/checkpwd.html). Second, make sure you have a - - pop3 110/tcp - -line in /etc/services. Third, put (all on one line, including -qmail-popup twice) - - pop3 stream tcp nowait root - /var/qmail/bin/qmail-popup qmail-popup - YOURHOST /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir - -into /etc/inetd.conf, and give inetd a HUP; replace YOURHOST with your -host's fully qualified domain name. Fourth, set up Maildir delivery for -any user who wants to read mail via POP. - -If you have tcpserver installed, skip the inetd step, and set up (on two -lines) - - tcpserver 0 pop3 /var/qmail/bin/qmail-popup YOURHOST \ - /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir & - -replacing YOURHOST with your host's fully qualified domain name. See -question 5.1 for more details on tcpserver. - -Security note: pop3d should be used only within a secure network; -otherwise an eavesdropper can steal passwords. - - -5.4. How do I allow selected clients to use this host as a relay? I see -that qmail-smtpd rejects messages to any host not listed in -control/rcpthosts. - -Answer: Three steps. First, install tcp-wrappers, available separately, -including hosts_options. Second, change your qmail-smtpd line in -inetd.conf to - - smtp stream tcp nowait qmaild /usr/local/bin/tcpd - /var/qmail/bin/tcp-env /var/qmail/bin/qmail-smtpd - -(all on one line) and give inetd a HUP. Third, in tcpd's hosts.allow, -make a line setting the environment variable RELAYCLIENT to the empty -string for the selected clients: - - tcp-env: 1.2.3.4, 1.2.3.5: setenv = RELAYCLIENT - -Here 1.2.3.4 and 1.2.3.5 are the clients' IP addresses. qmail-smtpd -ignores control/rcpthosts when RELAYCLIENT is set. (It also appends -RELAYCLIENT to each envelope recipient address. See question 5.5 for an -application.) - -Alternative procedure, if you are using tcpserver 0.80 or above: Create -/etc/tcp.smtp containing - - 1.2.3.6:allow,RELAYCLIENT="" - 127.:allow,RELAYCLIENT="" - -to allow clients with IP addresses 1.2.3.6 and 127.*. Run - - tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp - -Finally, insert - - -x /etc/tcp.smtp.cdb - -after tcpserver in your qmail-smtpd invocation. - - -5.5. How do I fix up messages from broken SMTP clients? - -Answer: Three steps. First, put - - | bouncesaying 'Permission denied' [ "@$HOST" != "@fixme" ] - | qmail-inject -f "$SENDER" -- "$DEFAULT" - -into ~alias/.qmail-fixup-default. Second, put - - fixme:fixup - -into /var/qmail/control/virtualdomains, and give qmail-send a HUP. -Third, follow the procedure in question 5.4, but set RELAYCLIENT to the -string ``@fixme'': - - tcp-env: 1.2.3.6, 1.2.3.7: setenv = RELAYCLIENT @fixme - -Here 1.2.3.6 and 1.2.3.7 are the clients' IP addresses. If you are using -tcpserver instead of inetd and tcpd, put - - 1.2.3.6:allow,RELAYCLIENT="@fixme" - 1.2.3.7:allow,RELAYCLIENT="@fixme" - -into /etc/tcp.smtp, and run tcprules as in question 5.4. - - -5.6. How do I set up qmail-qmqpd? I'd like to allow fast queueing of -outgoing mail from authorized clients. - -Answer: Make sure you have installed tcpserver 0.80 or above. Create -/etc/qmqp.tcp in tcprules format to allow connections from authorized -hosts. For example, if queueing is allowed from 1.2.3.*: - - 1.2.3.:allow - :deny - -Convert /etc/qmqp.tcp to /etc/qmqp.cdb: - - tcprules /etc/qmqp.cdb /etc/qmqp.tmp < /etc/qmqp.tcp - -Finally, set up - - tcpserver -x /etc/qmqp.cdb -u 7770 -g 2108 0 628 /var/qmail/bin/qmail-qmqpd & - -replacing 7770 and 2108 with the qmaild uid and nofiles gid. See -question 5.1 for more details on tcpserver. - - - -6. Configuring MUAs to work with qmail - - -6.1. How do I make BSD mail generate a Date with the local time zone? -When I send mail, I'd rather use the local time zone than GMT, since -some MUAs don't know how to display Date in the receiver's time zone. - -Answer: Put - - set sendmail=/var/qmail/bin/datemail - -into your .mailrc or your system-wide Mail.rc. Beware that BSD mail is -neither secure nor reliable. - - -6.2. How do I make pine work with qmail? - -Answer: Put - - sendmail-path=/usr/lib/sendmail -oem -oi -t - -into /usr/local/lib/pine.conf. (This will work with sendmail too.) -Beware that pine is neither secure nor reliable. - - -6.3. How do I make MH work with qmail? - -Answer: Put - - postproc: /usr/mh/lib/spost - -into each user's .mh_profile. (This will work with sendmail too.) Beware -that MH is neither secure nor reliable. - - -6.4. How do I stop Sun's dtcm from hanging? - -Answer: There is a novice programming error in dtcm, known as ``failure -to close the output side of the pipe in the child.'' Sun has, at the -time of this writing, not yet provided a patch. Sorry. - - - -7. Managing the mail system - - -7.1. How do I safely stop qmail-send? Back when we were running -sendmail, it was always tricky to kill sendmail without risking the loss -of current deliveries; what should I do with qmail-send? - -Answer: Go ahead and kill the qmail-send process. It will shut down -cleanly. Wait for ``exiting'' to show up in the log. To restart qmail, -run /var/qmail/rc the same way it is run from your system boot scripts, -with the proper PATH, resource limits, etc. - -Alternative, if qmail is supervised: svc -t /var/run/qmail. The -supervise process will kill qmail, wait for it to stop, and restart it. -Use -d instead of -t if you don't want qmail to restart automatically; -to manually restart it, use -u. - - -7.2. How do I manually run the queue? I'd like qmail to try delivering -all the remote messages right now. - -Answer: Give the qmail-send process an ALRM. (Do svc -a /var/run/qmail -if qmail is supervised.) - -You may want to run qmail-tcpok first, to guarantee that qmail-remote -will try all addresses. Normally, if an address fails repeatedly, -qmail-remote leaves it alone for an hour. - - -7.3. How do I rejuvenate a message? Somebody broke into Eric's computer -again; it's going to be down for at least another two days. I know Eric -has been expecting an important message---in fact, I see it sitting here -in /var/qmail/queue/mess/15/26902. It's been in the queue for six days; -how can I make sure it isn't bounced tomorrow? - -Answer: Just touch /var/qmail/queue/info/15/26902. (This is the only -form of queue modification that's safe while qmail is running.) - - -7.4. How do I organize a big network? I have a lot of machines, and I -don't know where to start. - -Answer: First, choose the domain name where your users will receive -mail. This is normally the shortest domain name you control. If you are -in charge of *.movie.edu, you can use addresses like joe@movie.edu. - -Second, choose the machine that will know what to do with different -users at movie.edu. Set up a host name in DNS for this machine: - - mailhost.movie.edu IN A 1.2.3.4 - 4.3.2.1.in-addr.arpa IN PTR mailhost.movie.edu - -Here 1.2.3.4 is the IP address of that machine. - -Third, make a list of machines where mail should end up. For example, if -mail for Bob should end up on Bob's workstation, put Bob's workstation -onto the list. For each of these machines, set up a host name in DNS: - - bobshost.movie.edu IN A 1.2.3.7 - 7.3.2.1.in-addr.arpa IN PTR bobshost.movie.edu - -Fourth, install qmail on bobshost.movie.edu. qmail will automatically -configure itself to accept messages for bob@bobshost.movie.edu and -deliver them to ~bob/Mailbox on bobshost. Do the same for the other -machines where mail should end up. - -Fifth, install qmail on mailhost.movie.edu. Put - - movie.edu:alias-movie - -into control/virtualdomains on mailhost. Then forward bob@movie.edu to -bob@bobshost.movie.edu, by putting - - bob@bobshost.movie.edu - -into ~alias/.qmail-movie-bob. Do the same for other users. - -Sixth, put movie.edu into control/rcpthosts on mailhost.movie.edu, so -that mailhost.movie.edu will accept messages for users at movie.edu. - -Seventh, set up an MX record in DNS to deliver movie.edu messages to -mailhost: - - movie.edu IN MX 10 mailhost.movie.edu - -Eighth, on all your machines, put movie.edu into control/defaulthost. - - -7.5. How do I back up and restore the queue disk? - -Answer: You can't. - -One difficulty is that you can't get a consistent snapshot of the queue -while qmail-send is running. Another difficulty is that messages in the -queue must have filenames that match their inode numbers. - -However, the big problem is that backups---even twice-daily backups--- -are far too unreliable for mail. If your disk dies, there will be very -little overlap between the messages saved in the last backup and the -messages that were lost. - -There are several ways to add real reliability to a mail server. Battery -backups will keep your server alive, letting you park the disk to avoid -a head crash, when the power goes out. Solid-state disks have their own -battery backups. RAID boxes let you replace dead disks without losing -any data. - - -7.6. How do I run a supervised copy of qmail? svc sounds useful. - -Answer: Install daemontools (http://pobox.com/~djb/daemontools.html). -Create a /var/run/qmail directory. Change - - /var/qmail/rc - -to - - supervise /var/run/qmail /var/qmail/rc - -in your boot scripts. Make sure that supervise is in the startup PATH. -Now you can use svc to stop or restart qmail, and svstat to check -whether qmail is running. - - -7.7. How do I avoid syslog? It chews up a lot of CPU time and isn't -reliable. - -Answer: Install daemontools (http://pobox.com/~djb/daemontools.html). -Make a /var/log/qmail directory, owned by qmaill, mode 2700. Do - - qmail-start ./Mailbox /usr/local/bin/accustamp \ - | setuser qmaill /usr/local/bin/cyclog /var/log/qmail & - -in /var/qmail/rc. - -If you are logging tcpserver connections, make a /var/log/smtpd -directory, and use cyclog /var/log/smtpd for tcpserver. You shouldn't -run several copies of cyclog with the same log directory. - -By default, cyclog keeps 10 automatically rotated log files, each -containing up to 100KB of log data. To keep 20 files with 1MB each, use -cyclog -s 1000000 -n 20. - - - -8. Miscellany - - -8.1. How do I tell qmail to do more deliveries at once? It's running -only 20 parallel qmail-remote processes. - -Answer: Decide how many deliveries you want to allow at once. Put that -number into control/concurrencyremote. Restart qmail-send as in question -7.1. If your system has resource limits, make sure you set the -descriptors limit to at least double the concurrency plus 5; otherwise -you'll get lots of unnecessary deferrals whenever a big burst of mail -shows up. Note that qmail also imposes a compile-time concurrency limit, -120 by default; this is set in conf-spawn. - - -8.2. How do I keep a copy of all incoming and outgoing mail messages? - -Answer: Set QUEUE_EXTRA to "Tlog\0" and QUEUE_EXTRALEN to 5 in extra.h. -Recompile qmail. Put ./msg-log into ~alias/.qmail-log. - -You can also use QUEUE_EXTRA to, e.g., record the Message-ID of every -message: run - - | awk '/^$/ { exit } /^[mM][eE][sS][sS][aA][gG][eE]-/ { print }' - -from ~alias/.qmail-log. - - -8.3. How do I switch slowly from sendmail to qmail? I'm thinking of -moving the heaven.af.mil network over to qmail, but first I'd like to -give my users a chance to try out qmail without affecting current -sendmail deliveries. We're using NFS. - -Answer: Find a host in your network, say pc.heaven.af.mil, that isn't -running an SMTP server. (If addresses at pc.heaven.af.mil are used, you -should already have an MX pointing pc.heaven.af.mil to your mail hub.) - -Set up a new MX record pointing lists.heaven.af.mil to pc.heaven.af.mil. -Install qmail on pc.heaven.af.mil. Replace pc with lists in the control -files. Make the qmail man pages available on all your machines. - -Now tell your users about qmail. A user can forward joe@heaven.af.mil to -joe@lists.heaven.af.mil to get ~/Mailbox delivery; he can set up .qmail -files; he can start running his own mailing lists @lists.heaven.af.mil. - -When you're ready to turn sendmail off, you can set up pc.heaven.af.mil -as your new mail hub. Add heaven.af.mil to control/locals, and change -the heaven.af.mil MX to point to pc.heaven.af.mil. Make sure you leave -lists.heaven.af.mil in control/locals so that transition addresses will -continue to work. diff --git a/s6/qmail/data/doc/INSTALL b/s6/qmail/data/doc/INSTALL @@ -1 +0,0 @@ -See http://lifewithqmail.org/lwq.html diff --git a/s6/qmail/data/doc/INSTALL.alias b/s6/qmail/data/doc/INSTALL.alias @@ -1,40 +0,0 @@ -qmail lets each user control all addresses of the form user-anything. -Addresses that don't start with a username are controlled by a special -user, alias. Delivery instructions for foo go into ~alias/.qmail-foo; -delivery instructions for user-foo go into ~user/.qmail-foo. See -dot-qmail.0 for the full story. - -qmail doesn't have any built-in support for /etc/aliases. If you have a -big /etc/aliases and you'd like to keep it, install the fastforward -package, available separately. /etc/aliases should already include the -aliases discussed below---Postmaster, MAILER-DAEMON, and root. - -If you don't have a big /etc/aliases, you'll find it easier to use -qmail's native alias mechanism. Here's a checklist of aliases you should -set up right now. - -* Postmaster. You're not an Internet citizen if this address doesn't -work. Simply touch (and chmod 644) ~alias/.qmail-postmaster; any mail -for Postmaster will be delivered to ~alias/Mailbox. - -* MAILER-DAEMON. Not required, but users sometimes respond to bounce -messages. Touch (and chmod 644) ~alias/.qmail-mailer-daemon. - -* root. Under qmail, root never receives mail. Your system may generate -mail messages to root every night; if you don't have an alias for root, -those messages will bounce. (They'll end up double-bouncing to the -postmaster.) Set up an alias for root in ~alias/.qmail-root. .qmail -files are similar to .forward files, but beware that they are strictly -line-oriented---see dot-qmail.0 for details. - -* Other non-user accounts. Under qmail, non-user accounts don't get -mail; ``user'' means a non-root account that owns ~account. Set up -aliases for any non-user accounts that normally receive mail. - -Note that special accounts such as ftp, www, and uucp should always have -home directories owned by root. - -* Default. If you want, you can touch ~alias/.qmail-default to catch -everything else. Beware: this will also catch typos and other addresses -that should probably be bounced instead. It won't catch addresses that -start with a user name---the user can set up his own ~/.qmail-default. diff --git a/s6/qmail/data/doc/INSTALL.ctl b/s6/qmail/data/doc/INSTALL.ctl @@ -1,38 +0,0 @@ -As you've seen, qmail has essentially no pre-compilation configuration. -You should never have to recompile it unless you want to change the -qmail home directory, usernames, or uids. - -qmail does allow quite a bit of easy post-installation configuration. If -you care how your machine greets other machines via SMTP, for example, -you can put an appropriate line into /var/qmail/control/smtpgreeting. - -But this is all optional---if control/smtpgreeting doesn't exist, qmail -will do something reasonable by default. You shouldn't worry much about -configuration right now. You can always come back and tune things later. - -There's one big exception. You MUST tell qmail your hostname. Just run -the config-fast script: - - # ./config-fast your.full.host.name - -config-fast puts your.full.host.name into control/me. It also puts it -into control/locals and control/rcpthosts, so that qmail will accept -mail for your.full.host.name. - -You can instead use the config script, which looks up your host name in -DNS: - - # ./config - -config also looks up your local IP addresses in DNS to decide which -hosts to accept mail for. - -(Why doesn't qmail do these lookups on the fly? This was a deliberate -design decision. qmail does all its local functions---header rewriting, -checking if a recipient is local, etc.---without talking to the network. -The point is that qmail can continue accepting and delivering local mail -even if your network connection goes down.) - -Next, read through FAQ for information on setting up optional features -like masquerading. If you really want to learn right now what all the -configuration possibilities are, see qmail-control.0. diff --git a/s6/qmail/data/doc/INSTALL.ids b/s6/qmail/data/doc/INSTALL.ids @@ -1,72 +0,0 @@ -Here's how to set up the qmail groups and the qmail users. - -On some systems there are commands that make this easy. Solaris and -Linux: - - # groupadd nofiles - # useradd -g nofiles -d /var/qmail/alias alias - # useradd -g nofiles -d /var/qmail qmaild - # useradd -g nofiles -d /var/qmail qmaill - # useradd -g nofiles -d /var/qmail qmailp - # groupadd qmail - # useradd -g qmail -d /var/qmail qmailq - # useradd -g qmail -d /var/qmail qmailr - # useradd -g qmail -d /var/qmail qmails - -FreeBSD 2.2: - - # pw groupadd nofiles - # pw useradd alias -g nofiles -d /var/qmail/alias -s /nonexistent - # pw useradd qmaild -g nofiles -d /var/qmail -s /nonexistent - # pw useradd qmaill -g nofiles -d /var/qmail -s /nonexistent - # pw useradd qmailp -g nofiles -d /var/qmail -s /nonexistent - # pw groupadd qmail - # pw useradd qmailq -g qmail -d /var/qmail -s /nonexistent - # pw useradd qmailr -g qmail -d /var/qmail -s /nonexistent - # pw useradd qmails -g qmail -d /var/qmail -s /nonexistent - -BSDI 2.0: - - # addgroup nofiles - # adduser -g nofiles -H/var/qmail/alias -G,,, -s/dev/null -P'*' alias - # adduser -g nofiles -H/var/qmail -G,,, -s/dev/null -P'*' qmaild - # adduser -g nofiles -H/var/qmail -G,,, -s/dev/null -P'*' qmaill - # adduser -g nofiles -H/var/qmail -G,,, -s/dev/null -P'*' qmailp - # addgroup qmail - # adduser -g qmail -H/var/qmail -G,,, -s/dev/null -P'*' qmailq - # adduser -g qmail -H/var/qmail -G,,, -s/dev/null -P'*' qmailr - # adduser -g qmail -H/var/qmail -G,,, -s/dev/null -P'*' qmails - -AIX: - - # mkgroup -A nofiles - # mkuser pgrp=nofiles home=/var/qmail/alias shell=/bin/true alias - # mkuser pgrp=nofiles home=/var/qmail shell=/bin/true qmaild - # mkuser pgrp=nofiles home=/var/qmail shell=/bin/true qmaill - # mkuser pgrp=nofiles home=/var/qmail shell=/bin/true qmailp - # mkgroup -A qmail - # mkuser pgrp=qmail home=/var/qmail shell=/bin/true qmailq - # mkuser pgrp=qmail home=/var/qmail shell=/bin/true qmailr - # mkuser pgrp=qmail home=/var/qmail shell=/bin/true qmails - -On other systems, you will have to edit /etc/group and /etc/passwd -manually. First add two new lines to /etc/group, something like - - qmail:*:2107: - nofiles:*:2108: - -where 2107 and 2108 are different from the other gids in /etc/group. -Next (using vipw) add six new lines to /etc/passwd, something like - - alias:*:7790:2108::/var/qmail/alias:/bin/true - qmaild:*:7791:2108::/var/qmail:/bin/true - qmaill:*:7792:2108::/var/qmail:/bin/true - qmailp:*:7793:2108::/var/qmail:/bin/true - qmailq:*:7794:2107::/var/qmail:/bin/true - qmailr:*:7795:2107::/var/qmail:/bin/true - qmails:*:7796:2107::/var/qmail:/bin/true - -where 7790 through 7796 are _new_ uids, 2107 is the qmail gid, and 2108 -is the nofiles gid. Make sure you use the nofiles gid for qmaild, -qmaill, qmailp, and alias, and the qmail gid for qmailq, qmailr, and -qmails. diff --git a/s6/qmail/data/doc/INSTALL.maildir b/s6/qmail/data/doc/INSTALL.maildir @@ -1,59 +0,0 @@ -This file points out some reasons that you might want to switch from -mbox format to a new format, maildir. - - -1. The trouble with mbox - -The mbox format---the format of ~user/Mailbox, understood by BSD Mail -and lots of other MUAs---is inherently unreliable. - -Think about it: what happens if the system crashes while a program is -appending a new message to ~user/Mailbox? The message will be truncated. -Even worse, if it was truncated in the middle of a line, it will end up -being merged with the next message! Sure, the mailer understands that it -wasn't successful, so it'll try delivering the message again later, but -it can't fix your corrupted mbox. - -Other formats, such as mh folders, are just as unreliable. - -qmail supports maildir, a crashproof format for incoming mail messages. -maildir is fast and easy for MUAs to use. Even better, maildir works -wonders over NFS---see below. - -I don't want to cram maildir down people's throats, so it's not the -default. Nevertheless, I encourage you to start asking for maildir -versions of your favorite MUAs, and to switch over to maildir as soon as -you can. - - -2. Sun's Network F_ail_u_re System - -Anyone who tells you that mail can be safely delivered in mbox format -over NFS is pulling your leg---as explained above, mbox format is -inherently unreliable even on a single machine. - -Anyway, NFS is the most unreliable computing environment ever invented, -and qmail doesn't even pretend to support mbox over NFS. - -You should switch to maildir, which works fine over NFS without any -locking. You can safely read your mail over NFS if it's in maildir -format. Any number of machines can deliver mail to you at the same time. -(On the other hand, for efficiency, it's better to get NFS out of the -picture---your mail should be delivered on the server that contains your -home directory.) - -Here's how to set up qmail to use maildir for your incoming mail: - - % maildirmake $HOME/Maildir - % echo ./Maildir/ > ~/.qmail - -Make sure you include the trailing slash on Maildir/. - -The system administrator can set up Maildir as the default for everybody -by creating a maildir in the new-user template directory and replacing -./Mailbox with ./Maildir/ in /var/qmail/rc. - -Until your MUA supports maildir, you'll probably want to convert maildir -format to (gaaack) mbox format. I've supplied a maildir2mbox utility -that does the trick, along with some tiny qail and elq and pinq wrappers -that call maildir2mbox before calling Mail or elm or pine. diff --git a/s6/qmail/data/doc/INSTALL.mbox b/s6/qmail/data/doc/INSTALL.mbox @@ -1,53 +0,0 @@ -The qmail package includes a local delivery agent, qmail-local, which -provides user-controlled mailing lists, cross-host alias loop detection, -and many other important qmail features. - -There's one important difference between qmail-local and binmail: -qmail-local delivers mail by default into ~user/Mailbox, rather than -/var/spool/mail/user. It uses mbox format, with lockf locking on systems -that don't have flock (HP/UX, Solaris), and flock locking otherwise. - -This file explains how to switch your system to ~user/Mailbox. You -aren't required to do this; for further discussion of /var/spool/mail, -and an explanation of how to continue using binmail for local -deliveries, see INSTALL.vsm. - -The basic procedure for switching to ~user/Mailbox is simple: - - * Move each /var/spool/mail/user to ~user/Mailbox. For safety, do - this in single-user mode. - - * As root, set up a symbolic link from /var/spool/mail/user to - ~user/Mailbox for each user. /var/spool/mail should be mode 1777, - so users will not be able to accidentally remove these links. - -A few mail programs are unable to handle symbolic links, so you will -have to configure them to look at ~user/Mailbox directly: - - * procmail: Change SYSTEM_MBOX in config.h and recompile; or, with - recent versions, define MAILSPOOLHOME in src/authenticate.c. - -An alternative to symbolic links is hlfsd. Consult the documentation for -hlfsd if it is included in your operating system. - -If /var/spool/mail is large, you can gain extra speed by configuring -all your mail software to look at ~user/Mailbox directly: - - * Most MUAs: Put ``setenv MAIL $HOME/Mailbox'' in your system-wide - .cshrc and ``MAIL=$HOME/Mailbox; export MAIL'' in your system-wide - .profile. - - * elm: Change "mailbox" to "Mailbox" around line 388 of newmbox.c and - recompile. (elm looks at $MAIL, but without this change elm will - fail if two users try to read mail simultaneously.) - - * pine: Put ``inbox-path=Mailbox'' in your system-wide pine.conf. - (For pine versions more recent than 3.91, see also FAQ 6.2.) - - * qpopper 2.2: Change /.mail to /Mailbox in pop_dropcopy.c and - recompile with -DHOMEDIRMAIL in CFLAGS. - -Some vendors, in a misguided attempt to solve the security problems of -/var/spool/mail, have made all their mail software setgid mail. After -you move the mailboxes, you can---and, for security, should---remove -those setgid-mail bits. diff --git a/s6/qmail/data/doc/INSTALL.vsm b/s6/qmail/data/doc/INSTALL.vsm @@ -1,50 +0,0 @@ -UNIX has traditionally delivered mail into a central spool directory, -/var/spool/mail. (The original name was /usr/spool/mail; some systems -now use /var/mail.) There are two basic problems with /var/spool/mail: - - * It's slow. On systems with thousands of users, /var/spool/mail has - thousands of entries. A few UNIX systems support fast operations on - large directories, but most don't. - - * It's insecure. Writing code that works safely in a world-writable - directory is not easy. See, for example, CERT advisory 95:02. - -These may not be problems at your site, so you may want to leave your -mailboxes in /var/spool/mail. - -This file explains several ways that you can configure qmail to use -existing /var/spool/mail delivery tools. Please note that I do not vouch -for the security or reliability of any of those tools. - - -1. What to configure - -The qmail system is started from /var/qmail/rc with - - qmail-start ./Mailbox splogger qmail - -The first argument to qmail-start, ./Mailbox, is the default delivery -instruction. You can change it to run a program such as binmail or -procmail. (See dot-qmail.0 for the format of delivery instructions.) - - -2. Using procmail - -You may already have installed procmail for mail filtering. procmail -delivers to /var/spool/mail by default. - -To set up qmail to use procmail, simply copy /var/qmail/boot/proc to -/var/qmail/rc. - -Note that procmail must be in your system's boot PATH; if it isn't, you -will have edit /var/qmail/rc to include the full path. - - -3. Using sendmail's delivery agent - -sendmail uses binmail to deliver to /var/spool/mail. binmail is shipped -with the operating system as /bin/mail or /usr/libexec/mail.local. - -There is some variation in binmail syntax among systems. The most common -interfaces are shown in /var/qmail/boot/binm1, /var/qmail/boot/binm2, -and /var/qmail/boot/binm3. diff --git a/s6/qmail/data/doc/PIC.local2alias b/s6/qmail/data/doc/PIC.local2alias @@ -1,37 +0,0 @@ - Original message: - - To: help - Hi. - -qmail-inject Fill in the complete envelope and header: - - | (envelope) from joe@heaven.af.mil to help@heaven.af.mil - | From: joe@heaven.af.mil - | To: help@heaven.af.mil - | - | Hi. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, help@heaven.af.mil. - | Is heaven.af.mil in locals? Yes. - | Deliver locally to help@heaven.af.mil. - V - -qmail-lspawn ./Mailbox - - | Look at mailbox name, help. - | Is help listed in qmail-users? No. - | Is there a help account? No. - | Give control of the message to alias. - | Run qmail-local. - V - -qmail-local alias ~alias help - help heaven.af.mil joe@heaven.af.mil ./Mailbox - - Does ~alias/.qmail-help exist? Yes: "john". - Forward message to john. diff --git a/s6/qmail/data/doc/PIC.local2ext b/s6/qmail/data/doc/PIC.local2ext @@ -1,41 +0,0 @@ - Original message: - - To: fred-sos - Hi. - -qmail-inject Fill in the complete envelope and header: - - | (envelope) from joe@heaven.af.mil to fred-sos@heaven.af.mil - | From: joe@heaven.af.mil - | To: fred-sos@heaven.af.mil - | - | Hi. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, fred-sos@heaven.af.mil. - | Is heaven.af.mil in locals? Yes. - | Deliver locally to fred-sos@heaven.af.mil. - V - -qmail-lspawn ./Mailbox - - | Look at mailbox name, fred-sos. - | Is fred-sos listed in qmail-users? No. - | Is there a fred-sos account? No. - | Is there a fred account? Yes. - | Is fred's uid nonzero? Yes. - | Is ~fred visible to the qmailp user? Yes. - | Is ~fred owned by fred? Yes. - | Give control of the message to fred. - | Run qmail-local. - V - -qmail-local fred ~fred fred-sos - sos heaven.af.mil joe@heaven.af.mil ./Mailbox - - Does ~fred/.qmail-sos exist? Yes: "./Extramail". - Write message to ./Extramail in mbox format. diff --git a/s6/qmail/data/doc/PIC.local2local b/s6/qmail/data/doc/PIC.local2local @@ -1,40 +0,0 @@ - Original message: - - To: fred - Hi. - -qmail-inject Fill in the complete envelope and header: - - | (envelope) from joe@heaven.af.mil to fred@heaven.af.mil - | From: joe@heaven.af.mil - | To: fred@heaven.af.mil - | - | Hi. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, fred@heaven.af.mil. - | Is heaven.af.mil in locals? Yes. - | Deliver locally to fred@heaven.af.mil. - V - -qmail-lspawn ./Mailbox - - | Look at mailbox name, fred. - | Is fred listed in qmail-users? No. - | Is there a fred account? Yes. - | Is fred's uid nonzero? Yes. - | Is ~fred visible to the qmailp user? Yes. - | Is ~fred owned by fred? Yes. - | Give control of the message to fred. - | Run qmail-local. - V - -qmail-local fred ~fred fred '' '' heaven.af.mil joe@heaven.af.mil ./Mailbox - - Does ~fred/.qmail exist? No. - Write message to ./Mailbox in mbox format. diff --git a/s6/qmail/data/doc/PIC.local2rem b/s6/qmail/data/doc/PIC.local2rem @@ -1,38 +0,0 @@ - Original message: - - To: bill@irs.gov - Hi. - -qmail-inject Fill in the complete envelope and header: - - | (envelope) from joe@heaven.af.mil to bill@irs.gov - | From: joe@heaven.af.mil - | To: bill@irs.gov - | - | Hi. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, bill@irs.gov. - | Is irs.gov in locals? No. - | Is bill@irs.gov in virtualdomains? No. - | Is irs.gov in virtualdomains? No. - | Is .gov in virtualdomains? No. - | Deliver remotely to bill@irs.gov. - V - -qmail-rspawn Run qmail-remote. - - | - V - -qmail-remote Look at host name, irs.gov. - Is irs.gov listed in smtproutes? No. - Look up DNS MX/A for irs.gov and connect to it by SMTP: - - MAIL FROM:<joe@heaven.af.mil> - RCPT TO:<bill@irs.gov> diff --git a/s6/qmail/data/doc/PIC.local2virt b/s6/qmail/data/doc/PIC.local2virt @@ -1,44 +0,0 @@ - Original message: - - To: dude@tommy.gov - Hi. - -qmail-inject Fill in the complete envelope and header: - - | (envelope) from joe@heaven.af.mil to dude@tommy.gov - | From: joe@heaven.af.mil - | To: dude@tommy.gov - | - | Hi. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, dude@tommy.gov. - | Is tommy.gov in locals? No. - | Is dude@tommy.gov in virtualdomains? No. - | Is tommy.gov in virtualdomains? Yes: "tommy.gov:fred". - | Deliver locally to fred-dude@tommy.gov. - V - -qmail-lspawn ./Mailbox - - | Look at mailbox name, fred-dude. - | Is fred-dude listed in qmail-users? No. - | Is there a fred-dude account? No. - | Is there a fred account? Yes. - | Is fred's uid nonzero? Yes. - | Is ~fred visible to the qmailp user? Yes. - | Is ~fred owned by fred? Yes. - | Give control of the message to fred. - | Run qmail-local. - V - -qmail-local fred ~fred fred-dude - dude tommy.gov joe@heaven.af.mil ./Mailbox - - Does ~fred/.qmail-dude exist? No. - Does ~fred/.qmail-default exist? Yes: "./Mail.tommy". - Write message to ./Mail.tommy in mbox format. diff --git a/s6/qmail/data/doc/PIC.nullclient b/s6/qmail/data/doc/PIC.nullclient @@ -1,38 +0,0 @@ - Original message: - - To: bill@irs.gov - Hi. - -qmail-inject Fill in the complete envelope and header: - - | (envelope) from joe@heaven.af.mil to bill@irs.gov - | From: joe@heaven.af.mil - | To: bill@irs.gov - | - | Hi. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, bill@irs.gov. - | Is irs.gov in locals? No. - | Is bill@irs.gov in virtualdomains? No. - | Is irs.gov in virtualdomains? No. - | Is .gov in virtualdomains? No. - | Deliver remotely to bill@irs.gov. - V - -qmail-rspawn Run qmail-remote. - - | - V - -qmail-remote Look at host name, irs.gov. - Is irs.gov listed in smtproutes? Yes: ":bigbang.af.mil". - Look up DNS A for bigbang.af.mil and connect by SMTP: - - MAIL FROM:<joe@heaven.af.mil> - RCPT TO:<bill@irs.gov> diff --git a/s6/qmail/data/doc/PIC.relaybad b/s6/qmail/data/doc/PIC.relaybad @@ -1,8 +0,0 @@ -qmail-smtpd Receive message by SMTP from another host: - - MAIL FROM:<spammer@aol.com> - RCPT TO:<bill@irs.gov> - - Is $RELAYCLIENT set? No. - Is irs.gov in rcpthosts? No. - Reject RCPT. diff --git a/s6/qmail/data/doc/PIC.relaygood b/s6/qmail/data/doc/PIC.relaygood @@ -1,33 +0,0 @@ -qmail-smtpd Receive message by SMTP from another host: - - | MAIL FROM:<joe@heaven.af.mil> - | RCPT TO:<bill@irs.gov> - | - | Is $RELAYCLIENT set? Yes: "". - | Accept RCPT. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, bill@irs.gov. - | Is irs.gov in locals? No. - | Is bill@irs.gov in virtualdomains? No. - | Is irs.gov in virtualdomains? No. - | Is .gov in virtualdomains? No. - | Deliver remotely to bill@irs.gov. - V - -qmail-rspawn Run qmail-remote. - - | - V - -qmail-remote Look at host name, irs.gov. - Is irs.gov listed in smtproutes? No. - Look up DNS MX/A for irs.gov and connect to it by SMTP: - - MAIL FROM:<joe@heaven.af.mil> - RCPT TO:<bill@irs.gov> diff --git a/s6/qmail/data/doc/PIC.rem2local b/s6/qmail/data/doc/PIC.rem2local @@ -1,36 +0,0 @@ -qmail-smtpd Receive message by SMTP from another host: - - | MAIL FROM:<bill@irs.gov> - | RCPT TO:<joe@heaven.af.mil> - | - | Is $RELAYCLIENT set? No. - | Is heaven.af.mil in rcpthosts? Yes. - | Accept RCPT. - V - -qmail-queue Store message safely on disk. - Trigger qmail-send. - | - V - -qmail-send Look at envelope recipient, joe@heaven.af.mil. - | Is heaven.af.mil in locals? Yes. - | Deliver locally to joe@heaven.af.mil. - V - -qmail-lspawn ./Mailbox - - | Look at mailbox name, joe. - | Is joe listed in qmail-users? No. - | Is there a joe account? Yes. - | Is joe's uid nonzero? Yes. - | Is ~joe visible to the qmailp user? Yes. - | Is ~joe owned by joe? Yes. - | Give control of the message to joe. - | Run qmail-local. - V - -qmail-local joe ~joe joe '' '' heaven.af.mil bill@irs.gov ./Mailbox - - Does ~joe/.qmail exist? No. - Write message to ./Mailbox in mbox format. diff --git a/s6/qmail/data/doc/REMOVE.binmail b/s6/qmail/data/doc/REMOVE.binmail @@ -1,16 +0,0 @@ -Here's how to remove binmail from your system. Don't do this if you have -configured qmail to use binmail for local delivery. - - -1. Find the binmail binary on your system: /usr/libexec/mail.local if - that exists, otherwise /bin/mail. - -2. Remove permissions from the binmail binary: - # chmod 0 /usr/libexec/mail.local - -3. If the binmail binary was /bin/mail, make sure that ``mail'' still - invokes a usable mailer. Under SVR4 you may want to link mail to - mailx. - -4. Comment out the comsat line in /etc/inetd.conf, and kill -HUP your - inetd. diff --git a/s6/qmail/data/doc/REMOVE.sendmail b/s6/qmail/data/doc/REMOVE.sendmail @@ -1,28 +0,0 @@ -Here's how to remove sendmail from your system. - -1. Find sendmail in your boot scripts. It's usually in either /etc/rc or - /etc/init.d/sendmail. It looks like - sendmail -bd -q15m - -q15m means that it should run the queue every 15 minutes; you may - see a different number. Comment out this line. - -2. Kill the sendmail daemon. You should first kill -STOP the daemon; if - any children are running, you should kill -CONT, wait, kill -STOP - again, and repeat ad nauseam. If there aren't any children, kill - -TERM and then kill -CONT. - -3. Check whether you have any messages in the sendmail queue, - /var/spool/mqueue. If you do, you will have to try flushing them with - sendmail.bak -q. If necessary, wait a while and run sendmail.bak -q - again. Repeat until the queue is empty. This may take several days. - -4. Remove the setuid bit on the sendmail binary, to prevent local users - from gaining extra privileges through sendmail's security holes. The - binary may be at several different locations: - # chmod 0 /usr/lib/sendmail - # chmod 0 /usr/sbin/sendmail - # chmod 0 /usr/lib/sendmail.mx - -5. Move the sendmail binary out of the way: - # mv /usr/lib/sendmail /usr/lib/sendmail.bak - # mv /usr/sbin/sendmail /usr/sbin/sendmail.bak diff --git a/s6/qmail/data/doc/SENDMAIL b/s6/qmail/data/doc/SENDMAIL @@ -1,76 +0,0 @@ -This document explains what you, as a user, will notice when the system -switches from sendmail to qmail. - -This is a global document, part of the qmail package, not reflecting the -decisions made by your system administrator. For details on - - * which local delivery agent qmail is configured to use, - * whether qmail is configured to use dot-forward, - * whether ezmlm is installed, - * whether fastforward is installed, and - * all other local configuration features, - -see your local sendmail-qmail upgrade announcement (which your system -administrator may have placed into /var/qmail/doc/ANNOUNCE). - - ---- Mailbox location - -If your system administrator has configured qmail to use binmail for -local deliveries, your mailbox will be in /var/spool/mail/you, just as -it was under sendmail. - -If your system administrator has configured qmail to use qmail-local for -local deliveries, your mailbox will be moved to ~you/Mailbox. There is a -symbolic link from /var/spool/mail/you to ~you/Mailbox, so your mail -reader will find the mailbox at its new location. - - ---- Loop control - -qmail-local automatically adds a Delivered-To field at the top of every -delivered message. It uses Delivered-To to prevent mail forwarding -loops, including cross-host mailing-list loops. - - ---- Outgoing messages - -qmail lets you use environment variables to control the appearance of -your outgoing mail, supplementing the features offered by your MUA. For -example, qmail-inject will set up Mail-Followup-To for you automatically -if you tell it which mailing lists you are subscribed to. See -qmail-inject(8) for a complete list of features. - -If you're at (say) sun.ee.movie.edu, qmail lets you type joe@mac for -joe@mac.ee.movie.edu, and joe@mac+ for joe@mac.movie.edu without the ee. -sendmail has a different interpretation of hostnames without dots. - - ---- Forwarding and mailing lists - -qmail gives you the power to set up your own mailing lists without -pestering your system administrator. - -Under qmail, you are in charge of all addresses of the form -you-anything. The delivery of you-anything is controlled by -~you/.qmail-anything, a file in your home directory. - -For example, if you want to set up a bug-of-the-month-club mailing list, -you can put a list of addresses into ~you/.qmail-botmc. Any mail to -you-botmc will be forwarded to all of those addresses. Mail directly to -you is controlled by ~you/.qmail. You can even set up a catch-all, -~you/.qmail-default, to handle unknown you- addresses. - -See dot-qmail(5) for the complete story. Beware that the syntax of -.qmail is different from the syntax of sendmail's .forward file. - -If your system administrator has configured qmail to use the dot-forward -compatibility tool, you can put forwarding addresses (and programs) into -.forward the same way you did with sendmail. - -If your system administrator has installed ezmlm, you can use ezmlm-make -to instantly set up a professional-quality mailing list, handling -subscriptions and archives automatically. - -If your system administrator has installed fastforward, you can easily -manage a large database of forwarding addresses. diff --git a/s6/qmail/data/doc/TEST.deliver b/s6/qmail/data/doc/TEST.deliver @@ -1,82 +0,0 @@ -You can do several tests of qmail delivery without setting up qmail to -accept messages through SMTP or through /usr/lib/sendmail: - -1. After you start qmail, look for a - qmail: status: local 0/10 remote 0/20 - line in syslog. qmail-send always prints either ``cannot start'' or - ``status''. (The big number is a splogger timestamp.) - -2. Do a ps and look for the qmail daemons. There should be four of - them, all idle: qmail-send, running as qmails; qmail-lspawn, running - as root; qmail-rspawn, running as qmailr; and qmail-clean, running - as qmailq. You will also see splogger, running as qmaill. - -3. Local-local test: Send yourself an empty message. (Replace ``me'' - with your username. Make sure to include the ``to:'' colon.) - % echo to: me | /var/qmail/bin/qmail-inject - The message will show up immediately in your mailbox, and syslog - will show something like this: - qmail: new msg 53 - qmail: info msg 53: bytes 246 from <me@domain> qp 20345 uid 666 - qmail: starting delivery 1: msg 53 to local me@domain - qmail: status: local 1/10 remote 0/20 - qmail: delivery 1: success: did_1+0+0/ - qmail: status: local 0/10 remote 0/20 - qmail: end msg 53 - (53 is an inode number; 20345 is a process ID; your numbers will - probably be different.) - -4. Local-error test: Send a message to a nonexistent local address. - % echo to: nonexistent | /var/qmail/bin/qmail-inject - qmail: new msg 53 - qmail: info msg 53: bytes 246 from <me@domain> qp 20351 uid 666 - qmail: starting delivery 2: msg 53 to local nonexistent@domain - qmail: status: local 1/10 remote 0/20 - qmail: delivery 2: failure: No_such_address.__#5.1.1_/ - qmail: status: local 0/10 remote 0/20 - qmail: bounce msg 53 qp 20357 - qmail: end msg 53 - qmail: new msg 54 - qmail: info msg 54: bytes 743 from <> qp 20357 uid 666 - qmail: starting delivery 3: msg 54 to local me@domain - qmail: status: local 1/10 remote 0/20 - qmail: delivery 3: success: did_1+0+0/ - qmail: status: local 0/10 remote 0/20 - qmail: end msg 54 - You will now have a bounce message in your mailbox. - -5. Local-remote test: Send an empty message to your account on another - machine. - % echo to: me@wherever | /var/qmail/bin/qmail-inject - qmail: new msg 53 - qmail: info msg 53: bytes 246 from <me@domain> qp 20372 uid 666 - qmail: starting delivery 4: msg 53 to remote me@wherever - qmail: status: local 0/10 remote 1/20 - qmail: delivery 4: success: 1.2.3.4_accepted_message./... - qmail: status: local 0/10 remote 0/20 - qmail: end msg 53 - There will be a pause between ``starting delivery'' and ``success''; - SMTP is slow. Check that the message is in your mailbox on the other - machine. - -6. Local-postmaster test: Send mail to postmaster, any capitalization. - % echo to: POSTmaster | /var/qmail/bin/qmail-inject - Look for the message in the alias mailbox, normally ~alias/Mailbox. - -7. Double-bounce test: Send a message with a completely bad envelope. - % /var/qmail/bin/qmail-inject -f nonexistent - To: unknownuser - Subject: testing - - This is a test. This is only a test. - % - (Use end-of-file, not dot, to end the message.) Look for the double - bounce in the alias mailbox. - -8. Group membership test: - % cat > ~me/.qmail-groups - |groups >> MYGROUPS; exit 0 - % /var/qmail/bin/qmail-inject me-groups < /dev/null - % cat ~me/MYGROUPS - MYGROUPS will show your normal gid and nothing else. (Under Solaris, - make sure to use /usr/ucb/groups; /usr/bin/groups is broken.) diff --git a/s6/qmail/data/doc/TEST.receive b/s6/qmail/data/doc/TEST.receive @@ -1,41 +0,0 @@ -You can do several tests of messages entering the qmail system: - -1. SMTP server test: Forge some mail locally via SMTP. Replace ``me'' - with your username and ``domain'' with your host's name. - % telnet 127.0.0.1 25 - Trying 127.0.0.1... - Connected to 127.0.0.1. - Escape character is '^]'. - 220 domain ESMTP - helo dude - 250 domain - mail <me@domain> - 250 ok - rcpt <me@domain> - 250 ok - data - 354 go ahead - Subject: testing - - This is a test. - . - 250 ok 812345679 qp 12345 - quit - 221 domain - Connection closed by foreign host. - % - Look for the message in your mailbox. (Note for programmers: Most - SMTP servers need more text after MAIL and RCPT. See RFC 821.) - -2. Remote-local test: Send yourself some mail from another machine. - Look for the message in your mailbox. - -3. Remote-error test: Send some mail from another machine to - nonexistent@domain. Look for a bounce message in the remote mailbox. - -4. UA test: Try sending mail, first to a local account, then to a - remote account, with your normal user agent. - -5. Remote-postmaster test: Send mail from another machine to - PoStMaStEr@domain. Look for the message in the alias mailbox, - normally ~alias/Mailbox. diff --git a/s6/qmail/data/doc/UPGRADE b/s6/qmail/data/doc/UPGRADE @@ -1,66 +0,0 @@ -SAVE COPIES OF YOUR OUTGOING MAIL! Like any other piece of software (and -information generally), the qmail system comes with NO WARRANTY. It's -much more secure and reliable than sendmail, but that's not saying much. - - -Here's how to upgrade to netqmail 1.05. This procedure will overwrite the -old qmail binaries. Furthermore, it may begin delivering messages from -the queue before you have had a chance to test it. - - -WARNING for upgrades from 1.00 or 1.01: qlist has been split into a -separate package. You can obtain it from http://pobox.com/~djb/qlist.html -if you have any users who need it. - -WARNING for upgrades from 1.01: recipientmap is gone. The virtualdomains -mechanism has been expanded to support virtual users. - - -Before starting, compare conf* to your old conf*, and make any necessary -changes. You can copy conf* from 1.02 or 1.03. - - -How to install: - - 1. Compile the programs and create the formatted man pages: - # make it man - - 2. Inform your users that mail will not be accepted for a few minutes. - - 3. Disable deliveries by killing your old qmail-send. Wait for it to - print ``exiting'' in the log. - - 4. Disable SMTP service by commenting out the smtp line in inetd.conf; - kill -HUP your inetd. (If you are using tcpserver, simply kill -STOP - your tcpserver. If you are running a QMTP server, disable that too.) - Wait for current qmail-smtpd processes to die. - - 5. Install the new binaries and man pages: - # make setup check - - 6. If your boot scripts are using qmail-start instead of /var/qmail/rc: - Copy /var/qmail/boot/home to /var/qmail/rc. (Use home+df instead if - you have installed dot-forward; use proc or proc+df if you are using - procmail by default for local deliveries.) Compare /var/qmail/rc to - your qmail-start boot line, and edit /var/qmail/rc if necessary. - Replace your qmail-start boot line with - csh -cf '/var/qmail/rc &' - - 7. Reenable deliveries: - # csh -cf '/var/qmail/rc &' - - 8. Read TEST.deliver. - - 9. Reenable SMTP service by restoring the smtp line in inetd.conf; kill - -HUP your inetd. (If you are using tcpserver, simply kill -CONT your - tcpserver. If you are running a QMTP server, reenable that too.) - -10. Read TEST.receive. - - -That's it! To report success: - % ( echo 'First M. Last'; cat `cat SYSDEPS` ) | mail djb-qst@cr.yp.to -Replace First M. Last with your name. - -If you have questions about qmail, join the qmail mailing list; see -http://pobox.com/~djb/qmail.html. diff --git a/s6/qmail/data/queue/info/0/... b/s6/qmail/data/queue/info/0/... diff --git a/s6/qmail/data/queue/info/1/... b/s6/qmail/data/queue/info/1/... diff --git a/s6/qmail/data/queue/info/10/... b/s6/qmail/data/queue/info/10/... diff --git a/s6/qmail/data/queue/info/11/... b/s6/qmail/data/queue/info/11/... diff --git a/s6/qmail/data/queue/info/12/... b/s6/qmail/data/queue/info/12/... diff --git a/s6/qmail/data/queue/info/13/... b/s6/qmail/data/queue/info/13/... diff --git a/s6/qmail/data/queue/info/14/... b/s6/qmail/data/queue/info/14/... diff --git a/s6/qmail/data/queue/info/15/... b/s6/qmail/data/queue/info/15/... diff --git a/s6/qmail/data/queue/info/16/... b/s6/qmail/data/queue/info/16/... diff --git a/s6/qmail/data/queue/info/17/... b/s6/qmail/data/queue/info/17/... diff --git a/s6/qmail/data/queue/info/18/... b/s6/qmail/data/queue/info/18/... diff --git a/s6/qmail/data/queue/info/19/... b/s6/qmail/data/queue/info/19/... diff --git a/s6/qmail/data/queue/info/2/... b/s6/qmail/data/queue/info/2/... diff --git a/s6/qmail/data/queue/info/20/... b/s6/qmail/data/queue/info/20/... diff --git a/s6/qmail/data/queue/info/21/... b/s6/qmail/data/queue/info/21/... diff --git a/s6/qmail/data/queue/info/22/... b/s6/qmail/data/queue/info/22/... diff --git a/s6/qmail/data/queue/info/3/... b/s6/qmail/data/queue/info/3/... diff --git a/s6/qmail/data/queue/info/4/... b/s6/qmail/data/queue/info/4/... diff --git a/s6/qmail/data/queue/info/5/... b/s6/qmail/data/queue/info/5/... diff --git a/s6/qmail/data/queue/info/6/... b/s6/qmail/data/queue/info/6/... diff --git a/s6/qmail/data/queue/info/7/... b/s6/qmail/data/queue/info/7/... diff --git a/s6/qmail/data/queue/info/8/... b/s6/qmail/data/queue/info/8/... diff --git a/s6/qmail/data/queue/info/9/... b/s6/qmail/data/queue/info/9/... diff --git a/s6/qmail/data/queue/local/0/... b/s6/qmail/data/queue/local/0/... diff --git a/s6/qmail/data/queue/local/1/... b/s6/qmail/data/queue/local/1/... diff --git a/s6/qmail/data/queue/local/10/... b/s6/qmail/data/queue/local/10/... diff --git a/s6/qmail/data/queue/local/11/... b/s6/qmail/data/queue/local/11/... diff --git a/s6/qmail/data/queue/local/12/... b/s6/qmail/data/queue/local/12/... diff --git a/s6/qmail/data/queue/local/13/... b/s6/qmail/data/queue/local/13/... diff --git a/s6/qmail/data/queue/local/14/... b/s6/qmail/data/queue/local/14/... diff --git a/s6/qmail/data/queue/local/15/... b/s6/qmail/data/queue/local/15/... diff --git a/s6/qmail/data/queue/local/16/... b/s6/qmail/data/queue/local/16/... diff --git a/s6/qmail/data/queue/local/17/... b/s6/qmail/data/queue/local/17/... diff --git a/s6/qmail/data/queue/local/18/... b/s6/qmail/data/queue/local/18/... diff --git a/s6/qmail/data/queue/local/19/... b/s6/qmail/data/queue/local/19/... diff --git a/s6/qmail/data/queue/local/2/... b/s6/qmail/data/queue/local/2/... diff --git a/s6/qmail/data/queue/local/20/... b/s6/qmail/data/queue/local/20/... diff --git a/s6/qmail/data/queue/local/21/... b/s6/qmail/data/queue/local/21/... diff --git a/s6/qmail/data/queue/local/22/... b/s6/qmail/data/queue/local/22/... diff --git a/s6/qmail/data/queue/local/3/... b/s6/qmail/data/queue/local/3/... diff --git a/s6/qmail/data/queue/local/4/... b/s6/qmail/data/queue/local/4/... diff --git a/s6/qmail/data/queue/local/5/... b/s6/qmail/data/queue/local/5/... diff --git a/s6/qmail/data/queue/local/6/... b/s6/qmail/data/queue/local/6/... diff --git a/s6/qmail/data/queue/local/7/... b/s6/qmail/data/queue/local/7/... diff --git a/s6/qmail/data/queue/local/8/... b/s6/qmail/data/queue/local/8/... diff --git a/s6/qmail/data/queue/local/9/... b/s6/qmail/data/queue/local/9/... diff --git a/s6/qmail/data/queue/lock/sendmutex b/s6/qmail/data/queue/lock/sendmutex diff --git a/s6/qmail/data/queue/lock/tcpto b/s6/qmail/data/queue/lock/tcpto Binary files differ. diff --git a/s6/qmail/data/queue/mess/0/... b/s6/qmail/data/queue/mess/0/... diff --git a/s6/qmail/data/queue/mess/1/... b/s6/qmail/data/queue/mess/1/... diff --git a/s6/qmail/data/queue/mess/10/... b/s6/qmail/data/queue/mess/10/... diff --git a/s6/qmail/data/queue/mess/11/... b/s6/qmail/data/queue/mess/11/... diff --git a/s6/qmail/data/queue/mess/12/... b/s6/qmail/data/queue/mess/12/... diff --git a/s6/qmail/data/queue/mess/13/... b/s6/qmail/data/queue/mess/13/... diff --git a/s6/qmail/data/queue/mess/14/... b/s6/qmail/data/queue/mess/14/... diff --git a/s6/qmail/data/queue/mess/15/... b/s6/qmail/data/queue/mess/15/... diff --git a/s6/qmail/data/queue/mess/16/... b/s6/qmail/data/queue/mess/16/... diff --git a/s6/qmail/data/queue/mess/17/... b/s6/qmail/data/queue/mess/17/... diff --git a/s6/qmail/data/queue/mess/18/... b/s6/qmail/data/queue/mess/18/... diff --git a/s6/qmail/data/queue/mess/19/... b/s6/qmail/data/queue/mess/19/... diff --git a/s6/qmail/data/queue/mess/2/... b/s6/qmail/data/queue/mess/2/... diff --git a/s6/qmail/data/queue/mess/20/... b/s6/qmail/data/queue/mess/20/... diff --git a/s6/qmail/data/queue/mess/21/... b/s6/qmail/data/queue/mess/21/... diff --git a/s6/qmail/data/queue/mess/22/... b/s6/qmail/data/queue/mess/22/... diff --git a/s6/qmail/data/queue/mess/3/... b/s6/qmail/data/queue/mess/3/... diff --git a/s6/qmail/data/queue/mess/4/... b/s6/qmail/data/queue/mess/4/... diff --git a/s6/qmail/data/queue/mess/5/... b/s6/qmail/data/queue/mess/5/... diff --git a/s6/qmail/data/queue/mess/6/... b/s6/qmail/data/queue/mess/6/... diff --git a/s6/qmail/data/queue/mess/7/... b/s6/qmail/data/queue/mess/7/... diff --git a/s6/qmail/data/queue/mess/8/... b/s6/qmail/data/queue/mess/8/... diff --git a/s6/qmail/data/queue/mess/9/... b/s6/qmail/data/queue/mess/9/... diff --git a/s6/qmail/data/queue/remote/0/... b/s6/qmail/data/queue/remote/0/... diff --git a/s6/qmail/data/queue/remote/1/... b/s6/qmail/data/queue/remote/1/... diff --git a/s6/qmail/data/queue/remote/10/... b/s6/qmail/data/queue/remote/10/... diff --git a/s6/qmail/data/queue/remote/11/... b/s6/qmail/data/queue/remote/11/... diff --git a/s6/qmail/data/queue/remote/12/... b/s6/qmail/data/queue/remote/12/... diff --git a/s6/qmail/data/queue/remote/13/... b/s6/qmail/data/queue/remote/13/... diff --git a/s6/qmail/data/queue/remote/14/... b/s6/qmail/data/queue/remote/14/... diff --git a/s6/qmail/data/queue/remote/15/... b/s6/qmail/data/queue/remote/15/... diff --git a/s6/qmail/data/queue/remote/16/... b/s6/qmail/data/queue/remote/16/... diff --git a/s6/qmail/data/queue/remote/17/... b/s6/qmail/data/queue/remote/17/... diff --git a/s6/qmail/data/queue/remote/18/... b/s6/qmail/data/queue/remote/18/... diff --git a/s6/qmail/data/queue/remote/19/... b/s6/qmail/data/queue/remote/19/... diff --git a/s6/qmail/data/queue/remote/2/... b/s6/qmail/data/queue/remote/2/... diff --git a/s6/qmail/data/queue/remote/20/... b/s6/qmail/data/queue/remote/20/... diff --git a/s6/qmail/data/queue/remote/21/... b/s6/qmail/data/queue/remote/21/... diff --git a/s6/qmail/data/queue/remote/22/... b/s6/qmail/data/queue/remote/22/... diff --git a/s6/qmail/data/queue/remote/3/... b/s6/qmail/data/queue/remote/3/... diff --git a/s6/qmail/data/queue/remote/4/... b/s6/qmail/data/queue/remote/4/... diff --git a/s6/qmail/data/queue/remote/5/... b/s6/qmail/data/queue/remote/5/... diff --git a/s6/qmail/data/queue/remote/6/... b/s6/qmail/data/queue/remote/6/... diff --git a/s6/qmail/data/queue/remote/7/... b/s6/qmail/data/queue/remote/7/... diff --git a/s6/qmail/data/queue/remote/8/... b/s6/qmail/data/queue/remote/8/... diff --git a/s6/qmail/data/queue/remote/9/... b/s6/qmail/data/queue/remote/9/... diff --git a/s6/qmail/data/users/... b/s6/qmail/data/users/...