From owner-freebsd-ports@FreeBSD.ORG Mon Oct 1 14:33:54 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC1E816A419 for ; Mon, 1 Oct 2007 14:33:54 +0000 (UTC) (envelope-from Lee@Dilkie.com) Received: from spock.dilkie.com (spock.dilkie.com [206.51.1.40]) by mx1.freebsd.org (Postfix) with ESMTP id 2B45013C458 for ; Mon, 1 Oct 2007 14:33:53 +0000 (UTC) (envelope-from Lee@Dilkie.com) Received: from [10.39.164.100] ([216.191.234.70]) (authenticated bits=0) by spock.dilkie.com (8.14.1/8.14.1) with ESMTP id l91EGu8E022386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 Oct 2007 10:16:57 -0400 (EDT) (envelope-from Lee@Dilkie.com) Message-ID: <47010153.9070303@Dilkie.com> Date: Mon, 01 Oct 2007 10:16:51 -0400 From: Lee Dilkie User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Matt Dawson References: <200710011331.06491.matt@chronos.org.uk> In-Reply-To: <200710011331.06491.matt@chronos.org.uk> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.63 on 206.51.1.40 Cc: freebsd-ports@freebsd.org Subject: Re: imap-uw-2006j_2,1, cclient-2006g_1,1 PAM problems? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2007 14:33:54 -0000 I had to roll back as well. Best I could tell was that the credentials presented to pam were the userid and userid (instead of password), at least that's what the logs looked like to me. -lee Matt Dawson wrote: > Is anyone else having problems with PAM authentication on these ports? I've > had to roll back to the 2004g_1,1 versions of both. > > Information is a bit thin; all I can tell you is that they both seem to > compile correctly and TLS works fine. Only when the client comes to > authenticate is there a problem. With a known good auth pair, the server > returns BAD LOGIN. The server also no longer supports LOGIN, only accepting > clear text. Rolling back cures this immediately with no change > in /etc/pam.d/pop3. > > Any suggestions? >