[EMAIL PROTECTED] wrote:
Hello and thanks for your reply...
check the permissions for /var/imap/db. I had a problem with that once. What's in /var/imap/db?
centralcore# ls -la /var/imap/ total 20 drwxr-xr-x 10 cyrus cyrus 512 Jan 17 22:23 . drwxr-xr-x 21 root wheel 512 Jan 17 22:23 .. drwxr-xr-x 2 cyrus cyrus 512 Jan 17 22:23 db drwxr-xr-x 2 cyrus cyrus 512 Jan 17 22:23 log drwxr-xr-x 2 cyrus cyrus 512 Jan 17 22:23 msg drwxr-xr-x 2 cyrus cyrus 512 Jan 17 22:23 proc drwxr-xr-x 28 cyrus cyrus 512 Jan 17 22:23 quota drwxr-xr-x 28 cyrus cyrus 512 Jan 17 22:23 sieve drwxr-xr-x 2 cyrus cyrus 512 Jan 17 22:23 socket drwxr-xr-x 28 cyrus cyrus 512 Jan 17 22:23 user
Also, I just tried again, using skiplist. I am getting errors now when I try and add a user to the sasldb backend:
centralcore# /usr/local/sbin/saslpasswd2 -c imapadmin
Jan 17 22:27:34 centralcore saslpasswd2: setpass succeeded for imapadmin Jan 17 22:27:34 centralcore saslpasswd2: error deleting entry from sasldb: DB_NOTFOUND: No matching key/data pair found Jan 17 22:27:34 centralcore last message repeated 2 times
This has nothing to do with skiplist, SASL and the Cyrus databases are two entirely separate things.
The errors you see are normal. saslpasswd2 is trying to delete some legacy secrets, which won't exist on a new system. The fact that setpass succeeds is all you need to see.
-- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
