Date: Fri, 23 Jul 2004 11:21:40 -0700 (PDT) From: Alex Melkomukov <amelkomukov@flexpop.net> To: dave <dmehler26@woh.rr.com> Cc: freebsd-questions@freebsd.org Subject: Re: chrooting Postfix+SASL+TLS Message-ID: <Pine.BSI.4.10.10407231117270.8377-100000@pdx-s02.navi.net> In-Reply-To: <000401c470df$bc97a810$0200a8c0@satellite>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Dave, I have setup /var/spool/postfix/var/state/salsauthd for that per a how-to I read. The normal socket was located in /var/state/saslauthd, so I figured that was the correct location. I guess I can try /var/spool/postfix/var/run and see if that works. am On Fri, 23 Jul 2004, dave wrote: > Hi, > Yah, your problem is when saslauth and smtp are chrooted they do not > have there unix socket that they use to communicate. When saslauthd normally > starts i believe it makes a socket at /var/run/mux i'm not near my machine > to confirm this, but assuming your postfix chroot is /var/spool/postfix you > would do: > > # mkdir -p /var/spool/postfix/var/run/mux > > and when you start saslauth use the -m option and specify the path to the > chroot location. > HTH > Dave. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.4.10.10407231117270.8377-100000>