-Mailman depends on a process called the ``qrunner'' to delivery all -email messages it sees. You must start the qrunner by executing the following -command from the $prefix directory: +Several Mailman features occur on a regular schedule, so you must set up +cron to run the right programs at the right time6.
-
- % bin/mailmanctl start -
-You probably want to start Mailman every time you reboot your system. Exactly -how to do this depends on your operating system. If your OS supports the -chkconfig command (e.g. RedHat and Mandrake Linuxes) you can -do the following (as root, from the Mailman install directory): - -
-
- % cp scripts/mailman /etc/init.d/mailman - % chkconfig --add mailman -
-Note that /etc/init.d may be /etc/rc.d/init.d on some systems. - -
-On Gentoo Linux, you can do the following: - -
-
- % cp scripts/mailman /etc/init.d/mailman - % rc-update add mailman default -
-On Debian, you probably want to use: +If your version of crontab supports the -u option, you must be +root to do this next step. Add $prefix/cron/crontab.in as a +crontab entry by executing these commands:
- % update-rc.d mailman defaults + % cd $prefix/cron + % crontab -u mailman crontab.in
-For Unixes that don't support chkconfig, you might try the
-following set of commands:
+If you used the --with-username option, use that user name
+instead of mailman for the -u argument value. If your
+crontab does not support the -u option, try these commands:
- % cp scripts/mailman /etc/init.d/mailman - % cp misc/mailman /etc/init.d - % cd /etc/rc.d/rc0.d - % ln -s ../init.d/mailman K12mailman - % cd ../rc1.d - % ln -s ../init.d/mailman K12mailman - % cd ../rc2.d - % ln -s ../init.d/mailman S98mailman - % cd ../rc3.d - % ln -s ../init.d/mailman S98mailman - % cd ../rc4.d - % ln -s ../init.d/mailman S98mailman - % cd ../rc5.d - % ln -s ../init.d/mailman S98mailman - % cd ../rc6.d - % ln -s ../init.d/mailman K12mailman + % cd $prefix/cron + % su - mailman + % crontab crontab.in
+
