Re: [Evolution] AUTH and BASE64


They will not be Base64 encoded spaces in the EHLO response, that will all
be plain text, therefor the esmtp_get_authtypes code is NOT broken

the actual AUTH tokens will be base64 encoded (possibly - according to the
RFC some may not support the base64 encoding)

Now...what *is* broken is the initial HELO vs EHLO code, we currently send
HELO if we do not detect the support of ESMTP, when, in fact, we should
probably send EHLO *first* no matter what, then, if that is rejected, send
HELO rather than trying to auto-detect


On Fri, 09 Jun 2000, Trever Adams wrote:
Date: Fri, 09 Jun 2000 13:02:28 -0400
To: evolution <evolution helixcode com>
From: Trever Adams <trever_Adams bigfoot com>
Subject: [Evolution] AUTH and BASE64

esmtp_get_authtypes is totally broken.  It assumes spaces around AUTH
that won't
be there.  It assumes spaces, according to the RFC, will be normal ASCII
spaces.  They are BASE64 (or '=').  In a few minutes I will describe the
exchange for the AUTH=LOGING type.

For the finest in family and value oriented products:
For owner friendly domain names:

Spruce: A release a day keeps the termites away

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]