Re: different sasl_mech_lists for imap and http?

2018-10-11 Thread Pim Zandbergen
Right, I tried that, but used the wrong prefix ("dav" instead of  "http"). So I would probably need to define imaps_sasl_mech_list and https_sasl_mech_list too. Can I save one line by mixing prefixed  and non-prefixed options as a default? Like sasl_mech_list: login plain cram-md5 digest-md

Re: different sasl_mech_lists for imap and http?

2018-10-11 Thread Ken Murchison
Yes.  Each option in imapd.conf can be prefixed with a service name from cyrus.conf. So if your services are named 'imap' and 'http', use: imap_sasl_mech_list http_sasl_mech_list Definitely don't rely on Digest for http.  Most implementations are either broken or incompatible.  I should hav

different sasl_mech_lists for imap and http?

2018-10-11 Thread Pim Zandbergen
Is there a simple way to configure a different sasl_mech_list for imap and http? I was allowing login, plain, cram-md5 and digest-md5 using sasldb, when I noticed digest-md5 is not working at all for http. But it works fine for imap. I started noticing this when it turned out iOS CalDAV/CardD