On Sat, 30 Aug 2008, Graham Leggett wrote:
Unfortunately the alternate usecase support in SASL is virtually non existent, so you're stuck using strace to tease out the real error that is preventing SASL from working. If you are truly stuck, use strace (or your local equivalent) to run testsaslauthd, and pick backwards through the error messages.
Graham, I'll do this over the weekend.
Typical reasons it doesn't work include trying to connect to a socket using the wrong path, or using the correct path, but without the permissions being set correctly to access the socket. Also be careful of assuming the permissions on the socket are correct - double check the permissions of all the parent directories of the socket as well.
What I've not found are the proper permissions. Would 770 be appropriate? Thanks, Rich
