I cannot start the saslauthd daemon. My server is running the latest Ubuntu Server (9.10) with Bind9 and the default LAMP stack, Postfix, and Courier-IMAP/Courier-POP3. As part of a disaster recovery process, I recently re-installed the aforementioned software, and imported data and configuration files related to an ecommerce website which crashed. The authoritative master nameserver and the PHP/MySQL/myphpadmin website are functioning perfectly. In an endeavor to save energy (electrical, not administrative), I decided to migrate my mail services to the aforementioned server by selectively following steps 15 and 16 in "The Perfect Server - Ubuntu Karmic Koala (Ubuntu 9.10) [ISPConfig 2] - Page 5." http://www.howtoforge.com/perfect-se...ispconfig-2-p5
Here is some information from the command line:
root@black:/# uname -a
Linux black 2.6.31-17-server #54-Ubuntu SMP Thu Dec 10 18:06:56 UTC 2009 x86_64 GNU/Linux
root@black:/# service saslauthd start
/etc/default/saslauthd: 55: -m: not found
* Starting SASL Authentication Daemon saslauthd * No run directory defined for saslauthd, not starting
root@black:/# cat /etc/default/saslauthd
# Settings for saslauthd daemon
# Please read /usr/share/doc/sasl2-bin/README.Debian for details.
# Should saslauthd run automatically on startup? (default: no)
# Description of this saslauthd instance. Recommended.
# (suggestion: SASL Authentication Daemon)
DESC="SASL Authentication Daemon"
# Short name of this saslauthd instance. Strongly recommended.
# (suggestion: saslauthd)
# Which authentication mechanisms should saslauthd use? (default: pam)
# Available options in this Debian package:
# getpwent -- use the getpwent() library function
# kerberos5 -- use Kerberos 5
# pam -- use PAM
# rimap -- use a remote IMAP server
# shadow -- use the local shadow password file
# sasldb -- use the local sasldb database file
# ldap -- use LDAP (configuration is in /etc/saslauthd.conf)
# Only one option may be used at a time. See the saslauthd man page
# for more information.
# Example: MECHANISMS="pam"
# Additional options for this mechanism. (default: none)
# See the saslauthd man page for information about mech-specific options.
# How many saslauthd processes should we run? (default: 5)
# A value of 0 will fork a new process for each connection.
# Other options (default: -c -m /var/run/saslauthd)
# Note: You MUST specify the -m option or saslauthd won't run!
# WARNING: DO NOT SPECIFY THE -d OPTION.
# The -d option will cause saslauthd to run in the foreground instead of as
# a daemon. This will PREVENT YOUR SYSTEM FROM BOOTING PROPERLY. If you wish
# to run saslauthd in debug mode, please run it by hand to be safe.
# See /usr/share/doc/sasl2-bin/README.Debian for Debian-specific information.
# See the saslauthd man page and the output of 'saslauthd -h' for general
# information about these options.
# Example for postfix users: "-c -m /var/spool/postfix/var/run/saslauthd"
OPTIONS=-c -m /var/spool/postfix/var/run/saslauthd -r
root@black:/# ls -lia /var/spool/postfix/var/run/saslauthd/
134910272 drwxr-xr-x 2 root root 6 2010-01-29 08:53 .
525972 drwxr-xr-x 3 root root 22 2010-01-27 21:51 ..
I don't fully fathom how Postfix chroot and the /var/run/saslauthd files function, which of these are missing, and how the owner-created /var/spool/postfix/var/run/saslauthd/"files" come to exist. I have already used "aptitude reinstall," for "libsasl2-2 sasl2-bin libsasl2-modules". I wouldn't mind starting from scratch with a clean install and perfect adherence to the complete tutorial, but I'm terrified of returning to the ecommerce disaster from which I have just recovered.
Any help will be truly appreciated.