From owner-freebsd-questions@FreeBSD.ORG Sun Feb 8 06:33:26 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5443216A4CE for ; Sun, 8 Feb 2004 06:33:26 -0800 (PST) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FE9143D1D for ; Sun, 8 Feb 2004 06:33:26 -0800 (PST) (envelope-from jshamlet@comcast.net) Received: from localhost.invalid (pcp04637401pcs.gambrl01.md.comcast.net[68.49.84.210]) by comcast.net (sccrmhc13) with ESMTP id <2004020814332501600f6kt0e>; Sun, 8 Feb 2004 14:33:25 +0000 From: "J. Seth Henry" To: freebsd-questions@freebsd.org Date: Sun, 8 Feb 2004 09:33:24 -0500 User-Agent: KMail/1.6 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200402080933.24082.jshamlet@comcast.net> Subject: Have two critical kmail 1.6 bugs been patched in the ports tree? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2004 14:33:26 -0000 Guys, I was checking out the kde website, and noticed that there are (or were) two critical bugs in the 3.2.0 release of kmail. (http://dot.kde.org/1075969434/) Have these been fixed in the ports tree, or do I need to attempt to apply a patch? (I would be affected by the pop3 filter bug.) I installed kmail after a cvsup upgrade Saturday at 12:30PM EST. Thanks, Seth Henry