From owner-freebsd-ports  Fri Apr 28 10:49:52 2000
Delivered-To: freebsd-ports@freebsd.org
Received: from viper.lovett.com (hub.lovett.com [216.60.121.161])
	by hub.freebsd.org (Postfix) with ESMTP id A9D0737B822
	for <ports@freebsd.org>; Fri, 28 Apr 2000 10:49:50 -0700 (PDT)
	(envelope-from ade@lovett.com)
Received: from ade by viper.lovett.com with local (Exim 3.13 #1)
	id 12lEte-000H6J-00
	for ports@FreeBSD.org; Fri, 28 Apr 2000 12:49:46 -0500
Date: Fri, 28 Apr 2000 12:49:46 -0500
From: Ade Lovett <ade@FreeBSD.org>
To: ports@FreeBSD.org
Subject: comms/hylafax
Message-ID: <20000428124946.G53118@lovett.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Ports people,

comms/hylafax has been marked FORBIDDEN with security holes for
quite some time now.  There are also a few ports PRs open relating
to it.  Since neither the authors, nor anyone on the ports list
appears to be concerned about it enough to fix it, I am proposing
that one week from today (5th May 2000)

	comms/hylafax
and	comms/tkhylafax

be removed from the tree and all associated PRs be closed.

Any objections? (preferably with patches to fix the problems...)

-aDe

-- 
Ade Lovett, Austin, TX.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message