>>>>> On Wed, 6 Feb 2002, "Darren" == Darren Nickerson wrote:
Darren> How do I convince timsieved to use saslauthd? It seems to want to use Darren> sasldb. Darren> Feb 6 11:45:52 polaris timsieved[20740]: Could not open db Darren> Feb 6 11:45:52 polaris timsieved[20740]: Could not open db Darren> Feb 6 11:45:52 polaris timsieved[20740]: no secret in database I should have been more clear. I'm trying to use sieveshell to manage sieve scripts, but I'm unable to authenticate using saslauthd. Will sieveshell one day know about different auth methods? Installsieve used to, according to the manpage, though its current commandline shows no evidence of supporting it. In the end, I fudged the authentication by creating sasldb2 for now (allowing DIGEST-MD5 to succeed), which brought me to my next problem. The following looked like a login failure: [darren@polaris darren]$ sieveshell --user=darren localhost connecting to localhost Please enter your password: unable to connect to server: Authentication error at /usr/bin/sieveshell line 170, <STDIN> line 1. but was really the inability to create (or absence of) the sieve directory tree it seems to have been looking for. This must have been something I missed in the setup docs? Feb 6 22:13:52 polaris master[31465]: about to exec /usr/cyrus/bin/timsieved Feb 6 22:13:52 polaris service-sieve[31465]: executed Feb 6 22:13:52 polaris service-sieve[31465]: accepted connection Feb 6 22:13:54 polaris timsieved[31465]: mkdir /usr/sieve/d/darren: No such file or directory Feb 6 22:13:54 polaris timsieved[31465]: error in actions_setuser() Feb 6 22:13:54 polaris master[868]: process 31465 exited, status 75 -Darren -- Darren Nickerson Chief Technology Officer iWorkwell, Inc. 215.875.9550 (voice) 215.882.3266 (cell) 215.243.8335 (fax) HR Made Easy.(tm) The information contained in this email message is intended only for the personal and confidential use of the recipient(s) named above. This message may contain confidential and/or privileged material. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please contact the sender immediately, and delete the original message.
