On Wed, 2007-06-27 at 07:50 -0600, Ben Schumacher wrote:
> This somewhat
> conflicts with dovecot's authentication system, which expects to have
> all the necessary authentication information internally and is not
> design (not willing?) to trust a checkpassword-style authentication
> mechanism to
On 6/25/07, John Peacock <[EMAIL PROTECTED]> wrote:
Ben Schumacher wrote:
> I would like to see this, too. After digging through the code some, it
> seems that the major sticking point is that dovecot would prefer to do
> the CRAM-MD5 internally and therefore expects to have access to the
> passw
Ben Schumacher wrote:
> I would like to see this, too. After digging through the code some, it
> seems that the major sticking point is that dovecot would prefer to do
> the CRAM-MD5 internally and therefore expects to have access to the
> password in plaintext and doesn't pass the timestamp on
Ben Schumacher wrote:
I would like to see this, too. After digging through the code some, it
seems that the major sticking point is that dovecot would prefer to do
the CRAM-MD5 internally and therefore expects to have access to the
password in plaintext and doesn't pass the timestamp on to
checkp
On 3/29/07, Max A. <[EMAIL PROTECTED]> wrote:
> Still a bit more fixes. My coding TODO list is again empty.
Whether it is possible to add APOP and CRAM-MD5 in the
checkpassword-module? Original qmail-popup is able APOP, and smtp-auth
patch (http://www.fehcom.de/qmail/smtpauth.html) can use CRAM-M
