Notes |
(0004613)
damjan (reporter)
2007-06-10 07:36
|
Do you use stable on unstable version?
Unstable version creates that file with sasl group and adds rw permissions to the socket:
-bash-3.00$ ls -l /var/opt/csw
total 2
drwxrws--- 2 root sasl 512 Jun 10 19:32 saslauthd
Add account which needs authentication via saslauthd to the sasl group and then it should work.
If you use stable version, then please beware of the current issues in SASL before you upgrade. Update is pending. |
|
(0004621)
rmf (reporter)
2007-06-11 15:49
|
It is the unstable version. But sendmail isn\'t in the saslauthd group, and I\'m not sure if simply adding smmsp to the saslauthd group would work without putting code changes into sendmail anyway. In any case, you need to KNOW that you have to do this, which is my only point. |
|
(0004641)
damjan (reporter)
2007-06-22 00:12
|
I see. It is actually written in the README.sasl, but it is not clear enough:
- CSWsasl creates a group \'sasl\'. Any process which is not running as root,
must belong to this group to perform authentiaction against SASLdb or via saslauthd.
I will clear it up in README.sasl for the next update. |
|
(0004642)
rmf (reporter)
2007-06-22 09:42
|
thanks. One of the reasons why it was perplexing was that sendmail, even in running as smmsp (ie, not root and not in group sasl), works fine. It\'s only when running the split configuration that amavisd wants where it breaks - one would naively think that you wouldn\'t have any permission problems once you get it working. |
|
(0010484)
yann (manager)
2013-07-09 15:57
|
The new package 2.1.25,REV=2013.07.09 which will soon land in all mirrors in the unstable repository contains the reference to the sasl group in the README.CSW file, so I am closing this bug.
|
|