>RedHat have a great .spec file for sasl1+2 combined in their rawhide >development snapshot. You might want to check it out, I'm using it now. > I guess this could be called a feature request :)
Would it be possible for you nice SASL folks to make releases containing both sasl1 and sasl2 libs. A standard way of installing both libs from one tarball will save a lot of trouble for different packagers and others. SASL1 will probably be used by other programes the next 1 - 2 years so I think we'll se a lot of two-sasllibs question as sasl2 moves into higher use. What do you think? Tarjei > >How do I convince timsieved to use saslauthd? It seems to want to use sasldb. > > Feb 6 11:45:52 polaris timsieved[20740]: Could not open db > Feb 6 11:45:52 polaris timsieved[20740]: Could not open db > Feb 6 11:45:52 polaris timsieved[20740]: no secret in database > >I've put various things in the sasl2 plugin dir: > > [root@polaris sasl2]# pwd > /usr/lib/sasl2 > [root@polaris sasl2]# cat timsieved.conf > pwcheck_method:saslauthd > [root@polaris sasl2]# cat Sieve.conf > pwcheck_method:saslauthd > [root@polaris sasl2]# > >but they're not getting picked up. I would have thought my Cyrus.conf would >have been enough anyway . . . ? > >Thanks for any info. > >-Darren >
