I can see why you describe it as "well hidden". Thanks for the enlightenment. I'll endeavor to get all of these points adequately included in the documentation. Thanks! https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3114 https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3115 :wes On 30 Oct 2008, at 15:28, Andreas Winkelmann wrote: > Because plugin_name is NULL in most cases, the interesting part > here is > config_getoverflowstring()@lib/libconfig.c: > > const char *config_getoverflowstring(const char *key, const char *def) > { > char buf[256]; > char *ret = NULL; > > /* First lookup <ident>_key, to see if we have a service-specific > * override */ > > if(config_ident) { > if(snprintf(buf,sizeof(buf),"%s_%s",config_ident,key) == -1) > fatal("key too long in config_getoverflowstring", > EC_TEMPFAIL); > > ret = hash_lookup(buf, &confighash); > } > > /* No service-specific override, check the actual key */ > if(!ret) > ret = hash_lookup(key, &confighash); > > /* Return what we got or the default */ > return ret ? ret : def; > } > > config_ident is filled from master with the first column from > cyrus.conf of > the assoiciated Service. So in the case of pop3 Cyrus-IMAP tries > first to > lookup the Option with "pop3_sasl_..." > >> The sasl_<someoption> seems to be pretty well described in the man >> page for imapd.conf. The method with the plugin_name >> (sasl_<plugin_name>_<someoption>) wasn't in the documentation that I >> could find. > > A few examples for plugin_name "SQL", "ldapdb", "DIGEST-MD5", > "GSSAPI", "SRP", > NULL. The environment of the related option from Cyrus-SASL > specifies the > plugin_name. All ldapdb_ Options have "ldapdb", "sql_*" "SQL" and > so on... ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
