init.d script only seems to be seeing first auth_mech

Bug #72097 reported by Gargoyle
4
Affects Status Importance Assigned to Milestone
cyrus-sasl2 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: libsasl2

If I set the MECHANISMS in /etc/defaults/saslauthd to "pam rimap", when saslauthd is started by the init.d script, it loads only pam. However, If I just have 1 auth_mech, then that one seems to work OK.

I redirected the output of saslauthd to /var/log/sasl.log and added the -V option. Snippet 1 below shows a single auth_mech working. Snippet 2 shows the second one (rimap) seems to get forgotten.

I hope I haven't made a silly mistake and wasted any-ones time.

Paul
(aka. Gargoyle)

--- 8< ---- Snippit 1 ---- 8< ---
-- /etc/defaults/saslauthd --
# This needs to be uncommented before saslauthd will be run automatically
# START=yes

# You must specify the authentication mechanisms you wish to use.
# This defaults to "pam" for PAM support, but may also include
# "shadow" or "sasldb", like this:
# MECHANISMS="pam shadow"

START=yes
PWDIR="/var/spool/postfix/var/run/saslauthd"
PARAMS="-V -r -O localhost -m ${PWDIR}"
PIDFILE="${PWDIR}/saslauthd.pid"

MECHANISMS="rimap"

-- /var/log/sasl.log --
saslauthd[22466] :main : num_procs : 5
saslauthd[22466] :main : mech_option: localhost
saslauthd[22466] :main : run_path : /var/spool/postfix/var/run/saslauthd
saslauthd[22466] :main : auth_mech : rimap
saslauthd[22466] :ipc_init : using accept lock file: /var/spool/postfix/var/run/saslauthd/mux.accept

--- 8< ---- Snippit 2 ---- 8< ---
-- /etc/defaults/saslauthd --
# This needs to be uncommented before saslauthd will be run automatically
# START=yes

# You must specify the authentication mechanisms you wish to use.
# This defaults to "pam" for PAM support, but may also include
# "shadow" or "sasldb", like this:
# MECHANISMS="pam shadow"

START=yes
PWDIR="/var/spool/postfix/var/run/saslauthd"
PARAMS="-V -r -O localhost -m ${PWDIR}"
PIDFILE="${PWDIR}/saslauthd.pid"

MECHANISMS="pam rimap"

-- /var/log/sasl.log --
saslauthd[22578] :main : num_procs : 5
saslauthd[22578] :main : mech_option: localhost
saslauthd[22578] :main : run_path : /var/spool/postfix/var/run/saslauthd
saslauthd[22578] :main : auth_mech : pam
saslauthd[22578] :ipc_init : using accept lock file: /var/spool/postfix/var/run/saslauthd/mux.accept

Revision history for this message
Adam Niedling (krychek) wrote :

What version of Ubuntu are you using? Is this still an issue?

Changed in cyrus-sasl2:
status: New → Incomplete
Revision history for this message
Gargoyle (g-rgoyle) wrote :

Wow, I filed that bug almost two years ago this week!

I have actually discontinued hosting my own email server and switched all my clients over to google apps, but I'll see if I have some time this weekend to recreate with 8.04 or 8.10 using my old setup notes.

Revision history for this message
Martin Meredith (mez) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in cyrus-sasl2 (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.