unable to open Berkeley db /etc/sasldb: No such file or directory
hello i have a suse linux 7.3 with qpopper and sendmail (i installed imapd but then disabled when it overlapped with qpopper on pop services) all of a sudden im getting the following error message and at the same time (i think due to this) one email account is not working... any ideas??
Hi!
i have a suse linux 7.3 with qpopper and sendmail (i installed imapd but then disabled when it overlapped with qpopper on pop services)
all of a sudden im getting the following error message and at the same time (i think due to this) one email account is not working...
I have no solution, but I have nearly the same problem:
I am also using SuSE 7.3 with sendmail and I use the
cyrus-(imapd)-pop3d (but I never installed qpopper).
pop3d[7981]: unable to open Berkeley db /etc/sasldb: No such file or directory
The only thing I configured is this inetd.conf-entry which should be
right:
pop3 stream tcp nowait cyrus /usr/cyrus/bin/pop3d pop3d
Bye.
* da_bug@gmx.net (da_bug@gmx.net) [020510 13:32]:
I have no solution, but I have nearly the same problem: I am also using SuSE 7.3 with sendmail and I use the cyrus-(imapd)-pop3d (but I never installed qpopper).
pop3d[7981]: unable to open Berkeley db /etc/sasldb: No such file or directory
The only thing I configured is this inetd.conf-entry which should be right: pop3 stream tcp nowait cyrus /usr/cyrus/bin/pop3d pop3d
Why doesn't /etc/sasldb exist? You did create the imap users with saslpasswd, right? -- -ckm
Hi, CM> Why doesn't /etc/sasldb exist? You did create the imap users with CM> saslpasswd, right? no, I want to use the existing passwd/shadow-entrys for authentification (I have been told this works). After reading in the cyrus-howto and checking the imapd.conf I found out that it used pam for authentification. the howto says:
If you don't want your password check to be the default sasldb, you must specify which one of PAM, kerberos_v4, passwd, shadow you wish to use. If PAM is the authentication you desire for example, you would type: sasl_passwd_check: pam
So I changed it to
sasl_passwd_check: shadow
I'm not sure if this works because I couldn't test it yet.
I think this imapd.conf-entry also controls the pop3-part of the
cyrus-imapd (?) but I'm not sure...
Bye.
participants (3)
-
Christopher Mahmood -
da_bug＠gmx.net -
Omppu