Bug#379881: cyrus-imapd-2.2: several oddities about imapd.conf parameters

Sven Mueller debian at incase.de
Mon Jul 31 11:11:27 UTC 2006


Ross Boylan wrote on 28/07/2006 20:37:
> On Fri, 2006-07-28 at 14:14 +0200, Sven Mueller wrote:
>>I just checked, here is a list of hard-wired service names (they are
>>identical to the executable name AFAICT except those specifically noted):
> 
> What is the significance of a hardcoded name?  That even if you name the
> service by something else in cyrus.conf the hardcoded name will still
> work?  That if you don't use the hardcoded name in cyrus.conf things
> will fail?

They will always use the hardcoded name as the service name, no matter
what you used in cyrus.conf. They will not, however stop to work if
their hardcoded name doesn't match the service name you chose in
cyrus.conf. They will also not try both names to match configuration
options, just the hardcoded one, which is used only to check for service
specific configuration options.

>>arbitron
>>chk_cyrus
>>ctl_cyrusdb
>>ctl_deliver
>>ctl_mboxlist
>>cvt_cyrusdb
>>cyr_expire
>>deliver (executable: cyrdeliver)
>>dump (executable: cyrdump)
>>fetchnews
>>idled
>>ipurge
>>mbexamine
>>mbpath
>>ptdump
>>ptexpire
>>quota
>>reconstruct (executable: cyrreconstruct)
>>squatter
>>syncnews
>>tls_prune

[...]
>>>>My reference to the sasl options may have been unclear.  I meant, if you
>>>>set lmtp_allowplaintext and sasl_mech_list how do they interact,
>>>>perticularly if they contradict each other? 
>>
>>You mean like when you only list "login" in the sasl_mech_list, but set
>>allowplaintext to "no"? In that case noone will be able to authenticate
>>on non-encrypted (i.e. non-TLS/non-SSL) sessions. I know this from
>>experience rather than from reading the source. The exception is
> 
> I was also thinking of the case in which one said allowplaintext: yes
> but PLAIN was not listed in sasl_mech.

Well, if you have neither PLAIN nor LOGIN (which are both considered
plaintext authentications IIRC) in your sasl_mech_list, it doesn't
matter what you have in allowplaintext.

Plaintext mechanisms are only tried if they are listed in sasl_mech_list
and either
1) The connection is encrypted or
2) allowplaintext is set to "yes"

> Too bad upstream hasn't been able to dedicate a bit more effort to the
> docs.

Sad but true.

Regards,
Sven
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 188 bytes
Desc: OpenPGP digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-imapd-debian-devel/attachments/20060731/dcba4a13/signature.pgp


More information about the Pkg-Cyrus-imapd-Debian-devel mailing list