On Fri, 13 Jun 2003 23:37:16 +0200, Luca Berra wrote:
> 
> Jun 13 23:32:12 Moskow postfix/postfix-script: starting the Postfix mail system
> Jun 13 23:32:12 Moskow postfix/master[4203]: daemon started -- version 2.0.12
> Jun 13 23:32:12 Moskow postfix:  succeeded
> Jun 13 23:32:15 Moskow postfix/smtpd[12935]: fatal: no SASL authentication mechanisms
> Jun 13 23:32:16 Moskow postfix/master[4203]: warning: process /usr/lib/postfix/smtpd 
> pid 12935 exit status 1
> Jun 13 23:32:16 Moskow postfix/master[4203]: warning: /usr/lib/postfix/smtpd: bad 
> command startup -- throttling
> 
> 
> [EMAIL PROTECTED] ~ # cat /usr/lib/sasl2/smtpd.conf
> pwcheck_method: saslauthd
> 
> [EMAIL PROTECTED] ~ # grep sasl /etc/postfix/main.cf
> smtpd_sasl_auth_enable = yes
> smtpd_sasl_security_options = noanonymous
> smtpd_recipient_restrictions = permit_mynetworks,
> reject_non_fqdn_recipient, permit_sasl_authenticated, check_relay_domains
> 
> and i am too tired to do more

I dicked around with this one for a while too.  Postfix's smtpd daemon
runs chrooted by default, which means it does not have access to the
"default" saslauthd socket in /var/lib/sasl2.  I simply moved the socket
into the smtpd's "chroot jail" and symlinked the "jailed" socket to the
regular space:
# ls -l /var/lib/
total 13
...
lrwxrwxrwx    1 root     root           31 May 30 09:27 sasl2 -> 
../spool/postfix/var/lib/sasl2//

All works fine now.

I guess, really, saslauthd should be able to listen on multiple sockets.

b.



Reply via email to