From owner-freebsd-ports@FreeBSD.ORG Mon Jan 17 01:05:09 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B1E216A4CE for ; Mon, 17 Jan 2005 01:05:09 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CD4A43D45 for ; Mon, 17 Jan 2005 01:05:08 +0000 (GMT) (envelope-from clint@0lsen.net) Received: from 0lsen.net ([24.20.127.157]) by comcast.net (sccrmhc13) with ESMTP id <20050117010507016006n441e>; Mon, 17 Jan 2005 01:05:07 +0000 Received: by 0lsen.net (Postfix, from userid 1001) id C10A217A05; Sun, 16 Jan 2005 17:05:06 -0800 (PST) Date: Sun, 16 Jan 2005 17:05:06 -0800 From: Clint Olsen To: Koop Mast Message-ID: <20050117010506.GB1359@0lsen.net> References: <20050116182553.GA19411@0lsen.net> <20050116193511.1df9b3d5.lehmann@ans-netz.de> <1105916643.655.13.camel@heater.rainbow-runner.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1105916643.655.13.camel@heater.rainbow-runner.nl> User-Agent: Mutt/1.4.2.1i Organization: NULlsen Network X-Disclaimer: Mutt Bites! cc: ports@freebsd.org Subject: Re: Courier-imap upgrade broke me going to 4.0 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 01:05:09 -0000 On Jan 17, Koop Mast wrote: > This problem got me too last week. I use userdb for my imap users. After > the upgrade none of my users could login on the imap. I fixed it then by > readding them. And I just found out that the userdb stuff doesn't live in > /usr/local/etc anymore, but in /usr/local/etc/authlib. This is part of the problem, but the documentation for getting CRAM-MD5 authentication working is just plain lacking. I'm thinking I need to rewrite this section and send it to the author. CRAM will not work unless you pretty much import all the fields from the password file for a given user, and the Courier docs don't mention this anywhere. Why does CRAM authentication care about a users home directory location or shell for that matter? I also noticed the port does not install pw2userdb from the distribution, which is very handy for automating the password file into userdb. -Clint