In all cyrus-sasl ebuilds I read: RDEPEND="authdaemond? ( || ( >=net-mail/courier-imap-3.0.7 >=mail-mta/courier-0.46 ) ) That's incorrect as there is no need of courier to use the authdaemond feature. Anyway, it's needed only in the default configuration, even if one could use dovecot instead. I am using cyrus-sasl authdaemond with any problem at all without courier-imap (I use the kerberos5 authentication mechanism). If pam is activated, it should default to pam. If kerberos is activated, it should default to kerberos5. Otherwise it shoud default to shadow. But why this dependency?
(In reply to comment #0) > But why this dependency? Perhaps because noone (including upstream - see doc/sysadmin.html) has tested this against anything else? If you have a patch to use dovecot, feel free to attach it. (And no, pam/kerberos/shadow has absolutely nothing to do with this and is not an 'alternative' to the courier dependency at all).
From doc/sysadmin.html: "contacts Courier-IMAP's authdaemond daemon to check passwords. This daemon is simliar in functionality to saslauthd, and is shipped separately with the Courier mail server. Note: this feature is not compiled in the library by default To enable authdaemond support, pass --with-authdaemond to the configuration script, [...] you can specify --with-authdaemond=PATH to the configure script so that authdaemond_path points to a default, static, location." So what we do is perfectly correct, the authdaemond USE flag enables --with-autdaemond=/path/to/courier/authdaemond/socket, and since that is needed, it also then DEPENDs upon the correct courier packages to get Courier's authdaemond. This has nothing to do at all with dovecot or other SASL implementation, this is simply an optional feature of cyrus-sasl, where it can use another backend from which to get its authentication data: courier's authdaemond. Best regards, CHTEKK.
