[bug-mailutils] Re: gsasl support for version 0.6

[Simon Josefsson]

Thanks for the error message.  Given how imapd/auth_gsasl.c look:

  if (gsasl_cram_md5_pwd && access (gsasl_cram_md5_pwd, R_OK) == 0)
    {
      gsasl_server_callback_retrieve_set (ctx, cb_retrieve);
    }

I'd say you didn't specify a CRAM-MD5 password file, or it was not
readable.  Do you have a $(sysconfdir)/cram-md5.pwd?  Typically
/etc/cram-md5.pwd or /usr/local/etc/cram-md5.pwd.

The IMAP server should be able to implement a callback for PLAIN that
uses PAM or /etc/passwd directly, for password authentication, though,
but this appear to be missing right now.  It is impossible to use PAM
or /etc/passwd for CRAM-MD5/DIGEST-MD5 though, and for those systems
you must create a user/password database and store it in
$(sysconfdir)/cram-md5.pwd.

I only read the source very briefly, sorry if I missed something.

Regards,
Simon

Fredrick O Jackson <address@hidden> writes:

> I use Kmail, and I've tried most of the settings in the options dialog, 
> including LOGIN, PLAIN, CRAM-MD5, and DIGEST-MD5. I have discovered that 
> using one of these produces syslog errors "GSASL error: Authentication failed 
> because the password was not provided."
> Thanks
> Fred
>
>
> _____________________________________
> On Sunday 13 February 2005 05:43 pm, Sergey Poznyakoff wrote:
>> Fredrick O Jackson <address@hidden> wrote:
>> > * CAPABILITY IMAP4rev1 NAMESPACE IDLE X-VERSION AUTH=GSSAPI
>> > AUTH=ANONYMOUS AUTH=EXTERNAL AUTH=PLAIN AUTH=LOGIN AUTH=SECURID
>> > AUTH=CRAM-MD5
>>
>> Great. That means that your imap4d does supports sasl. What
>> authentication method is your client program using?
>>
>> Regards,
>> Sergey