On Sep 27, 2008, at 12:17 AM, Giorgenes Gelatti wrote:
I have a client connecting to dovecot and comunicating like this:
* OK Dovecot ready.
* AUTHENTICATE MYAUTH
+ base64 challange
base64_response {NNN}
* NO Invalid base64 data in continued response
The problem is that dovecot seems to reject the response because of
the {NNN} in the end of the string.
If I remove the {NNN} it authenticates just fine.
Any idea of whether it's standard or not?
What is the {NNN}? I've never seen that before and it's definitely against RFC 3501:
The client response consists of a single line consisting of a BASE64encoded string. If the client wishes to cancel an authentication exchange,it issues a line consisting of a single "*".
PGP.sig
Description: This is a digitally signed message part
