Luca noted, "
But it won't do you any good if all your secrets are in sasldb. What happens if you remove completely /usr/lib/sasl/smtpd.conf? (sasldb should be the default then)."
When I remove it, SASLDB keeps working. So, does this mean that the PAM setting never worked at all, and choosing a method which was somehow
that would surprise me, since pam is the method I'm using now (on 8.2, though) and it works fine. At home I'm using sasl v2 with saslauthd (it's not possible in sasl v2 to use pam directly, and that's a good thing depending on your pam method: an unprivileged user cannot access /etc/shadow, for example, while saslauthd can).
valid but not enabled caused the fallthrough to sasldb? I'm just very puzzled by it not working when I specify sasldb.
I'm puzzled too. I never used sasldb with sasl v1 (did some cursory tests with v2 while preparing packages for it), but "sasldb" is mentioned in the documentation.
and Luca also noted:
"This is wrong: the sasldb for v1 and v2 have a different layout, so they should be two separate and distinct files. This has nothing to do with your problem though."
Sorry,I caught that and did the conversion, so the v2 sasldb now lives in /var/lib/sasl2/sasl.db
Yes, but as I said that's not your problem. There are currently *no* packages in mandrake 9.1 using sasl v2 (apart from cyrus-imapd in contribs), but things are going to change in 9.2 (sasl v1 has been obsoleted more than a year ago).
BTW, may I ask you how you did the conversion? (since the dbconverter-2 as packaged is broken --my fault, but I sent a fix that's been ignored--, maybe you just used the one generated while rebuilding the rpm?).
Martin asked, "What about to use sasldb as authentication method?" One of the things I've done while looking on the web is to note that sasl's default sasldb location is /etc/sasldb, not /var/lib/sasl/sasl.db. So, I put in a symlink to the v1 version.
Wait a minute, that's it!!
The database location is a configure option (--with-dbpath), and in the 9.0 spec file it was set to /var/lib/sasl/sasl.db. In the 9.1 package, during the merge of the v1 and v2 sources (something that I wouldn't have done) the maintaner forgot to add this configure option, so the library checks the default location.
One more brokenness to add to the list (gdbm/berkeley, dbconverter-2, sasl.db location).
Bye
-- Luca Olivetti
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
