dovecot - Sep 2008 - problems with auth protocol

Hello there,

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?

Thanks you.

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 BASE64
> encoded string.  If the client wishes to cancel an authentication  
> exchange,
> it issues a line consisting of a single "*".
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20080927/50d07d2b/attachment-0002.bin>