On Thu, 3 Jan 2002, Ken Murchison wrote:
> > # ls -l /usr/local/lib/sasl/*plain*
> > lrwxrwxrwx 1 root system 18 Oct 23 12:57 libplain.a ->
>libplain.so.1.0.14
> > -rwxr-xr-x 1 root system 679 Oct 23 12:57 libplain.la
> > lrwxrwxrwx 1 root system 18 Oct 23 12:57 libplain.so.1 ->
>libplain.so.1.0.14
> > -rwxr-xr-x 1 root system 12900 Oct 23 12:57 libplain.so.1.0.14
>
> Do you have any other mechs installed in the directory? If so, then
> timsieved isn't seeing any of them. Try running:
>
> imtest -m login <servername>
>
> and see if any of your mechanisms are listed.
$ imtest -m login localhost
C: C01 CAPABILITY
S: * OK yoda IMAP4 v2.0.16 server ready
S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS ID
NO_ATOMIC_RENAME UNSELECT MULTIAPPEND SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES
IDLE X-NETSCAPE
S: C01 OK Completed
Password:
C: L01 LOGIN cyrus {5}
+ go ahead
C: <omitted>
L01 OK User logged in
Authenticated.
Hm. :-/
> If you have the tls_* options set in imapd.conf, trying running:
>
> imtest -t "" -m plain <servername>
>
> and see if imapd picks up the PLAIN mechanism.
I don't have ans tls_* options right now.
> I'd also check auth.log to see if there are any SASL errors.
Jan 4 15:26:49 yoda imapd[235334]: login: localhost[127.0.0.1] cyrus plaintext
working just fine.
Only that I cannot authenticate to timsieved. :-(
Trying authenticate "plain" "myuser" only yields
NO ("SASL" "no mechanism available") "Authentication error"
I have checked again on SASL, PLAIN is definitely compiled in.
*sigh*
