View Single Post
Old 4th April 2012, 01:37
Mitzy Mitzy is offline
Join Date: Mar 2012
Posts: 41
Thanks: 20
Thanked 0 Times in 0 Posts

Originally Posted by falko View Post
Looks to me as if the -r switch is missing. What do you have in /etc/default/saslauthd?
Here is the contents of that file.

# 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!
# 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/run/saslauthd"
I don't know if this is related but every time I try apt-get upgrade I get the following error, is it related?

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  libsasl2-2 libsasl2-dev libsasl2-modules libsasl2-modules-sql
4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/454 kB of archives.
After this operation, 180 kB disk space will be freed.
Do you want to continue [Y/n]? y
Reading changelogs... Done
Get:1 Changelog for libsasl2-2 ( [50.6 kB]
cyrus-sasl2 (2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu2) oneiric; urgency=low

  * Build for multiarch.  LP: #826601.

 -- Steve Langasek <>  Mon, 15 Aug 2011 15:30:56 -0700

cyrus-sasl2 (2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1) oneiric; urgency=low

  * Fix FTBFS with newer versions of Heimdal. LP: #825872

 -- Jelmer Vernooij <>  Sat, 13 Aug 2011 18:00:52 +0200

cyrus-sasl2 (2.1.24~rc1.dfsg1+cvs2011-05-23-4) unstable; urgency=low

  * Fix yet another upstream segfault breakage in GSSAPI from CVS
    (Closes: #629589)

 -- OndÅej Surý <>  Wed, 08 Jun 2011 08:37:13 +0200

cyrus-sasl2 (2.1.24~rc1.dfsg1+cvs2011-05-23-3) unstable; urgency=low

Last edited by Mitzy; 4th April 2012 at 01:40.
Reply With Quote
Sponsored Links