imapd not using saslauthd - IMAP
This is a discussion on imapd not using saslauthd - IMAP ; First, Postfix is working fine for its authentication using saslauthd.
Now, the problem is that imapd doesn't seem to use at all saslauthd, and
always try to access sasldb2 for its authentication despite the fact
that imap.conf contains: sasl_pwcheck_method: saslauthd
...
-
imapd not using saslauthd
First, Postfix is working fine for its authentication using saslauthd.
Now, the problem is that imapd doesn't seem to use at all saslauthd, and
always try to access sasldb2 for its authentication despite the fact
that imap.conf contains: sasl_pwcheck_method: saslauthd
and no message in the log saying that communication with saslauthd is
not possible.
Any idea?
Thanks
--
Stephane D'Alu
-
Re: imapd not using saslauthd
in comp.mail.imap i read:
>Now, the problem is that imapd doesn't seem to use at all saslauthd, and
>always try to access sasldb2 for its authentication despite the fact
>that imap.conf contains: sasl_pwcheck_method: saslauthd
>and no message in the log saying that communication with saslauthd is
>not possible.
UW IMAP does not use the Cyrus SASL libraries. If you use some other imapd
-- which seems likely, as UW wouldn't look in sasldb2 either -- you'll have
to be more explicit.
--
a signature
-
Re: imapd not using saslauthd
those who know me have no need of my name wrote:
> in comp.mail.imap i read:
>
>
>>Now, the problem is that imapd doesn't seem to use at all saslauthd, and
>>always try to access sasldb2 for its authentication despite the fact
>>that imap.conf contains: sasl_pwcheck_method: saslauthd
>>and no message in the log saying that communication with saslauthd is
>>not possible.
>
>
> UW IMAP does not use the Cyrus SASL libraries. If you use some other imapd
> -- which seems likely, as UW wouldn't look in sasldb2 either -- you'll have
> to be more explicit.
>
Was using Cyrus IMAP and SASL. Found the problem. I was using ldap to
store the password using a SHA hash. As the password was not in clear
text it was not possible to use CRAM-MD5 or Digest-MD5, which was
requested by mozilla (as I checked the 'use secure autentication'), so
it seems that IMAP was using the 'next'/'fallback' method which involved
looking in sasldb2.
--
Stephane
Similar Threads
-
By Application Development in forum IMAP
Replies: 1
Last Post: 10-24-2007, 03:12 AM
-
By Application Development in forum IMAP
Replies: 1
Last Post: 01-27-2005, 08:57 PM
-
By Application Development in forum IMAP
Replies: 2
Last Post: 07-21-2004, 01:49 PM
-
By Application Development in forum IMAP
Replies: 0
Last Post: 02-02-2004, 07:08 AM
-
By Application Development in forum IMAP
Replies: 2
Last Post: 11-26-2003, 10:58 AM