WHOA! Where the heck has THAT! message been? I have to say, it was a bit
surreal to have posted this question on the 6th, and then to have seen several
threads about it emerge in the past week, all asking a similar question ;-)
Received: from lists2.andrew.cmu.edu (LISTS2.ANDREW.CMU.EDU [128.2.10.216])
by mail.iworkwell.com (Postfix) with ESMTP id D7297B4624
for <[EMAIL PROTECTED]>; Wed, 13 Feb 2002 14:47:59 -0500 (EST)
Received: (from postman@localhost)
by lists2.andrew.cmu.edu (8.12.0.Beta16/8.12.0.Beta16) id g16KQrHt001232
for info-cyrus-list; Wed, 6 Feb 2002 15:26:53 -0500 (EST)
*phew* 7 days sitting on lists2.andrew.cmu.edu. Poor little e-mail . . . I hope
you were occasionally feeding it!
Is this a moderation/approval workflow issue?
-Darren
>>>>> On Wed, 6 Feb 2002, "Darren" == Darren Nickerson wrote:
Darren> Folks,
Darren> RedHat have a great .spec file for sasl1+2 combined in their rawhide
Darren> development snapshot. You might want to check it out, I'm using it
now.
Darren> How do I convince timsieved to use saslauthd? It seems to want to
Darren> use 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
Darren> I've put various things in the sasl2 plugin dir:
Darren> [root@polaris sasl2]# pwd
Darren> /usr/lib/sasl2
Darren> [root@polaris sasl2]# cat timsieved.conf
Darren> pwcheck_method:saslauthd
Darren> [root@polaris sasl2]# cat Sieve.conf
Darren> pwcheck_method:saslauthd
Darren> [root@polaris sasl2]#
Darren> but they're not getting picked up. I would have thought my
Cyrus.conf would
Darren> have been enough anyway . . . ?
Darren> Thanks for any info.
Darren> -Darren
