From owner-freebsd-questions@FreeBSD.ORG Thu Oct 9 06:55:17 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9288E106568F for ; Thu, 9 Oct 2008 06:55:17 +0000 (UTC) (envelope-from rock_on_the_web@comcen.com.au) Received: from angel.comcen.com.au (angel.comcen.com.au [203.23.236.69]) by mx1.freebsd.org (Postfix) with ESMTP id 54FA18FC27 for ; Thu, 9 Oct 2008 06:55:17 +0000 (UTC) (envelope-from rock_on_the_web@comcen.com.au) Received: from [192.168.0.185] (unknown [202.172.126.254]) by angel.comcen.com.au (Postfix) with ESMTP id 574465C2ED7D for ; Thu, 9 Oct 2008 17:51:29 +1100 (EST) From: Da Rock To: freebsd-questions@freebsd.org In-Reply-To: <1223533280.12779.23.camel@laptop1.herveybayaustralia.com.au> References: <1223533280.12779.23.camel@laptop1.herveybayaustralia.com.au> Content-Type: text/plain Date: Thu, 09 Oct 2008 16:52:29 +1000 Message-Id: <1223535149.12779.32.camel@laptop1.herveybayaustralia.com.au> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) Content-Transfer-Encoding: 7bit X-comcen-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: 574465C2ED7D.4D703 X-comcen-MailScanner: Found to be clean X-comcen-MailScanner-SpamCheck: not spam, SpamAssassin (score=0.1, required 3, RDNS_NONE 0.10) X-comcen-MailScanner-From: rock_on_the_web@comcen.com.au X-Spam-Status: No Subject: [SOLVED] Re: !@%%## maildrop and postfix - temporary authentication failure X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Oct 2008 06:55:17 -0000 On Thu, 2008-10-09 at 16:21 +1000, Da Rock wrote: > I'm really about to throw this damn server through a closed window (or > better yet a brick wall). I've searched high and low on google for a > straight answer, and any references in mailing lists give an answer of > read the INSTALL file (as if thats supposed to solve everything). > > I have virtual users for email in postfix, and I want to use maildrop to > deliver to the virtual mailboxes. Problem is, when it does use maildrop > it shows an error in the logs as the subject line says. > > I've tried everything, checked everything. That supposed magic solution > in the INSTALL file says only ONE thing needs to be set to get it to > work. Maildrop is owned by root and group is mail. The socket is rwx > globally (all this is set by the port install). The executing user for > pipe in postfix is vmail. > > I've installed the port with authlib and gdbm (even manually adjusted > the makefile to ensure --enable-userdb). Nada. > > The generally consensus is that it should work out of the box- so what > the hell am I doing wrong? Where should I be looking? Specifically: what > is not authenticating? I can manually test maildrop ok. So wtf? > > You'll have to excuse my language here- I'm not sure how much hair I > have left after working on this for several days... Ok, I know I'm answering my own question here- but this should definitely be fixed. In the INSTALL file, someone should change the statement where it says "When using the standalone maildrop build with courier-authlib, one of the following configurations must be used:"\ to: "When using the standalone maildrop build with courier-authlib, ALL of the following configurations must be used:" Just after I sent the email I thought I'd check the only thing I hadn't changed, the setuid bit. There are several reasons why I hadn't had the guts to do this before- but in my mood I was feeling reckless. 1. The statement in the INSTALL file said only one configuration needed to be changed. 2. I installed from ports- I would have thought (like most would, and history has served to provide empirical data) that the install process would have set this. 3. None of the information I read when searching emphasised this when all other options are already set- and certainly none based on freebsd. Anyone else with this issue popping up THIS is the answer- set ALL the configuration options in the INSTALL file.