From owner-freebsd-stable@FreeBSD.ORG  Wed Jan 17 04:39:59 2007
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id D2B1916A40F
	for <freebsd-stable@freebsd.org>; Wed, 17 Jan 2007 04:39:59 +0000 (UTC)
	(envelope-from pkg@hunter-gatherer.org)
Received: from [212.112.40.199] (212-112-40-199.lidnet.net [212.112.40.199])
	by mx1.freebsd.org (Postfix) with SMTP id 1597513C45D
	for <freebsd-stable@freebsd.org>; Wed, 17 Jan 2007 04:39:58 +0000 (UTC)
	(envelope-from pkg@hunter-gatherer.org)
Received: (qmail 40121 invoked by uid 1000); 17 Jan 2007 04:13:16 -0000
Date: Wed, 17 Jan 2007 05:13:16 +0100
From: Par Leijonhufvud <par@hunter-gatherer.org>
To: freebsd-stable@freebsd.org
Message-ID: <20070117041316.GA23307@ojibwe.hunter-gatherer.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Subject: Fetchmail problem
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jan 2007 04:39:59 -0000

I have a FreeBSD box (running ancient 4.8) that used to collect email
fine with fetchmail. Then after te latest portupgrade of fetchmail it
stopped working. When trying to run it manual I see the error shown
below.

Anyone with suggestions as to (a) just what is going wrong, and (b) how
to fix it? Another machine running 5.3 have no problems.

/Par

==========================================
 % fetchmail -v -v -p pop3 -u <USERNAME> tuschin.blackcatnetworks.co.uk
fetchmail: removing stale lockfile
Enter password for <USERNAME>@tuschin.blackcatnetworks.co.uk: 
fetchmail: 6.3.6 querying tuschin.blackcatnetworks.co.uk (protocol POP3) at Wed Jan 17 05:09:02 2007: poll started
Trying to connect to 2001:1b40:0:20::34/110...connection failed.
fetchmail: connection to tuschin.blackcatnetworks.co.uk:pop3 [2001:1b40:0:20::34/110] failed: No route to host.
Trying to connect to 193.201.200.34/110...connected.
fetchmail: POP3< +OK Hello there.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Here's what I can do:
fetchmail: POP3< STLS
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< LOGIN-DELAY 10
fetchmail: POP3< PIPELINING
fetchmail: POP3< UIDL
fetchmail: POP3< IMPLEMENTATION Courier Mail Server
fetchmail: POP3< .
fetchmail: POP3> STLS
fetchmail: POP3< +OK Begin SSL/TLS negotiation now.
fetchmail: Issuer Organization: Equifax Secure Inc.
fetchmail: Issuer CommonName: Equifax Secure Global eBusiness CA-1
fetchmail: Server CommonName: tuschin.blackcatnetworks.co.uk
fetchmail: tuschin.blackcatnetworks.co.uk key fingerprint: 82:24:50:19:D3:9D:36:12:EC:49:99:7C:E1:C3:A9:F2
fetchmail: Server certificate verification error: unable to get local issuer certificate
fetchmail: Server certificate verification error: certificate not trusted
fetchmail: Server certificate verification error: unable to verify the first certificate
Segmentation fault (core dumped)
absaroka 114 ~ % 
==========================================