search for: rfc4959

...s-cli --starttls --x509keyfile marc_mail.key --x509certfile marc_mail.crt -p sieve 172.17.1.4 ... m:OK "TLS negotiation successful." c:authenticate "EXTERNAL" "" m:"" c:"" m:OK "Logged in." However if I try the "imap" syntax (rfc4959) I get logged in at once ... m:OK "TLS negotiation successful." c:authenticate "EXTERNAL" "=" m:OK "Logged in." Note that this is an imap only extention, "=" is an invalid base64 encoding. Marc

...quot; policy. In fact, the problem seems to be a little bit deeper. In our setup user/password challenge is not needed at all. This is exactly what RFC 4959, "IMAP Extension for Simple Authentication and Security Layer (SASL) Initial Client Response", is about (http://tools.ietf.org/html/rfc4959 , see SASL EXTERNAL example). Are there any plans to implement SASL EXTERNAL mechanism in Dovecot? Thank you! Zohan

...certfile > marc_mail.crt -p sieve 172.17.1.4 > > ... > m:OK "TLS negotiation successful." > c:authenticate "EXTERNAL" "" > m:"" > c:"" > m:OK "Logged in." > > > However if I try the "imap" syntax (rfc4959) I get logged in at once > > ... > m:OK "TLS negotiation successful." > c:authenticate "EXTERNAL" "=" > m:OK "Logged in." > > Note that this is an imap only extention, "=" is an invalid base64 > encoding. Will get back on th...

....17.1.4 >> >> ... >> m:OK "TLS negotiation successful." >> c:authenticate "EXTERNAL" "" >> m:"" >> c:"" >> m:OK "Logged in." >> >> >> However if I try the "imap" syntax (rfc4959) I get logged in at once >> >> ... >> m:OK "TLS negotiation successful." >> c:authenticate "EXTERNAL" "=" >> m:OK "Logged in." >> >> Note that this is an imap only extention, "=" is an invalid base64 >&gt...