From owner-freebsd-questions@FreeBSD.ORG Tue Oct 9 05:13:56 2007 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E52EA16A417 for ; Tue, 9 Oct 2007 05:13:56 +0000 (UTC) (envelope-from terry@sucked-in.com) Received: from mail.sucked-in.com (got.sucked-in.com [64.251.22.156]) by mx1.freebsd.org (Postfix) with ESMTP id C125113C45B for ; Tue, 9 Oct 2007 05:13:56 +0000 (UTC) (envelope-from terry@sucked-in.com) Received: from localhost (got.sucked-in.com [64.251.22.156]) by mail.sucked-in.com (Postfix) with ESMTP id 6DF751CC73; Tue, 9 Oct 2007 14:59:05 +1000 (EST) X-Virus-Scanned: amavisd-new at sucked-in.com Received: from mail.sucked-in.com ([64.251.22.156]) by localhost (mail.sucked-in.com [64.251.22.156]) (amavisd-new, port 10024) with ESMTP id PcNhRc4kvnBp; Tue, 9 Oct 2007 14:59:05 +1000 (EST) Received: from TerryPC (220-253-114-145.VIC.netspace.net.au [220.253.114.145]) by mail.sucked-in.com (Postfix) with ESMTP id B6FFA1CC39; Tue, 9 Oct 2007 14:59:03 +1000 (EST) From: "Terry Sposato" To: "'Tankko'" , References: <7fec743f0710081830n2e8448b9s96c76d7c15b5d0d9@mail.gmail.com> In-Reply-To: <7fec743f0710081830n2e8448b9s96c76d7c15b5d0d9@mail.gmail.com> Date: Tue, 9 Oct 2007 14:59:17 +1000 Message-ID: <000c01c80a31$27912cc0$76b38640$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcgKF9e7op5XDzQfSEmTkYiPDq2+HQAGRPZA Content-Language: en-au Cc: Subject: RE: courier-authlib problems. 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: Tue, 09 Oct 2007 05:13:57 -0000 Tankko, I am having these exact same problems with courier as well. I upgraded the system a couple of days ago and courier-imap-pop3d-ssl works fine with clients such as Outlook, but I get the same errors with Evolution as an e-mail client. It works fine using pop3d without ssl so it is definitely something screwed with the ssl part. Not exactly sure and haven't been able to track it down. -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Tankko Sent: Tuesday, 9 October 2007 11:31 AM To: questions@freebsd.org Subject: courier-authlib problems. I upgraded one of my servers to courier-authlib-base-0.60.0 from .59 and I am now getting the following errors in my mail log: Oct 8 18:21:47 myserver.net authdaemond: Shared object "libauthvchkpw.so" not found, required by "authdaemond" Oct 8 18:21:47 myserver.net authdaemond: Installing libauthpam Oct 8 18:21:47 myserver.net authdaemond: Installation complete: authpam Oct 8 18:21:47 myserver.net authdaemond: Installing libauthldap Oct 8 18:21:47 myserver.net authdaemond: Shared object "libauthldap.so" not found, required by "authdaemond" Oct 8 18:21:47 myserver.net authdaemond: Installing libauthmysql Oct 8 18:21:47 myserver.net authdaemond: Shared object "libauthmysql.so" not found, required by "authdaemond" Oct 8 18:21:47 myserver.net authdaemond: Installing libauthpgsql Oct 8 18:21:47 myserver.net authdaemond: Shared object "libauthpgsql.so" not found, required by "authdaemond" and Oct 8 18:11:33 myserver.net imapd-ssl: couriertls: connect: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number Oct 8 18:12:07 myserver.net imapd-ssl: couriertls: connect: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number Thunderbird (OSX) has doesn't seem to care, but the iphone is now unable to get email. I am using SSL to get mail via imap. I have a 2nd server that has not been upgraded to .60 yet, and it works fine. But...the upgraded server has: courier-authlib-base-0.60.0 = up-to-date with port and the non-upgraded server has: courier-authlib-0.59.3 < needs updating (port has 0.60.0) courier-authlib-base-0.59.3 < needs updating (port has 0.60.0) courier-authlib-vchkpw-0.59.3 < needs updating (port has 0.60.0) I am assuming the upgraded server had these three ports as well before the upgrade, but I can not be 100% sure. I always kept these 2 severs running the same versions of everything, so I assume they were. Anyone know how to fix this? Tankko _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"