From owner-freebsd-questions@FreeBSD.ORG Fri Jul 23 18:16:08 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E98D16A4CE for ; Fri, 23 Jul 2004 18:16:08 +0000 (GMT) Received: from ms-smtp-02-eri0.ohiordc.rr.com (ms-smtp-02-smtplb.ohiordc.rr.com [65.24.5.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8605643D53 for ; Fri, 23 Jul 2004 18:16:07 +0000 (GMT) (envelope-from dmehler26@woh.rr.com) Received: from satellite (dhcp065-031-041-029.woh.rr.com [65.31.41.29]) i6NIG2lo002438; Fri, 23 Jul 2004 14:16:03 -0400 (EDT) Message-ID: <000401c470df$bc97a810$0200a8c0@satellite> From: "dave" To: "Alex Melkomukov" , References: Date: Fri, 23 Jul 2004 14:06:10 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: chrooting Postfix+SASL+TLS X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jul 2004 18:16:08 -0000 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.