Since I haven't seen a response to this yet, I'll
take a shot. Make sure you compiled imspd with the
appropriate options (my assumption would be that you
should use the same as imapd). You might try to
explicitly disable-sasl (not sure if imspd supports
that flag).
You also might try and touch /etc/sasldb just to
see what it does when there actually is a file there.
You haven't given us much else to work with.
We would need to know what authentication mechanism
you were expecting to use and what compile time
options you used with imapd vs imspd to really say
anything concrete.
Since I don't use imspd I can't say much more.
Is there a configuration file? Check to ensure
you are using the right authentication mechanism.
-- Michael --
----- Original Message -----
From: "P Christie" <[EMAIL PROTECTED]>
To: "info-cyrus" <[EMAIL PROTECTED]>
Sent: Tuesday, June 05, 2001 2:34 AM
Subject: cyrus-imspd-v1.6a3
> I have installed the cyrus-imspd 1.6 on a Solaris machine which is
> already running cyrus imap 1.6.24. On testing with imtest the following
> happens and I am not sure what to try next.
>
> bash$ /usr/local/bin/imtest -p 406 -m login localhost
> C: C01 CAPABILITY
> S: * OK Cyrus IMSP version 1.6a3 ready
> S: * CAPABILITY AUTH=PLAIN AUTH=KERBEROS_V4 LITERAL+
> S: C01 OK capability completed
> Password:
> + go
> L01 NO generic failure
> Authenticated.
> Security strength factor: 0
> . logout
> * BYE Logging user out
> . OK Logging user out
> Connection closed.
> bash$
>
> The /var/adm/messages has the following
>
> Jun 5 10:31:23 anaheim.bath.ac.uk imsp[12688]:
> unable to open Berkeley db /etc/sasldb: No such file or directory
>
> Any ideas?
> -------------------
> P Christie
> [EMAIL PROTECTED]
>
>
