Easy bug: undocumented option "sasl_saslauthd_path" to imapd

Andreas Winkelmann ml at awinkelmann.de
Wed Dec 10 04:52:54 EST 2008


> imapd.conf will accept an option:
>
>    sasl_saslauthd_path: /var/spool/postfix/var/run/saslauthd/mux
>
> instructing it to connect to the saslauthd socket in a non-standard
> location (usually /var/run).  This is very useful if e.g. you're
> running Postfix in a chroot.
>
> A recursive grep for ``sasl_saslauthd_path'' in the source yields no
> occurances of this option anywhere!  It should at least be in the
> imapd.conf or imapd manpages, correct?

This (saslauthd_path) is a Cyrus-SASL Option, not a Cyrus-IMAP option.

If the Cyrus-SASL Library wants to resolv an Option it asks the
Application first if it wants to override the Option. In Cyrus-Imap this
feature is used and you can specify Cyrus-SASL Options in the
Configuration File of Cyrus-IMAP. To separate these Options from the real
Cyrus-IMAP Options they have to be prefixed with "sasl_".

So in Cyrus-IMAP all given sasl_* Options are forwarded to Cyrus-SASL.
There is no other relation for these Options in Cyrus-IMAP.

I see no sense in adding documentation for each Cyrus-SASL Option to
Cyrus-IMAP's Documentation. There are a lot more than mentioned in the
imapd.conf Man-Page.

But maybe it would be nice to have a better desciption of this handling in
the man-Page.

--
Andreas



More information about the Info-cyrus mailing list