From owner-freebsd-ports@freebsd.org  Mon Feb  8 06:30:50 2016
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5580AAA1302
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Mon,  8 Feb 2016 06:30:50 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::50:5])
 by mx1.freebsd.org (Postfix) with ESMTP id 472EF1394
 for <freebsd-ports@freebsd.org>; Mon,  8 Feb 2016 06:30:50 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 43C7EAA1301; Mon,  8 Feb 2016 06:30:50 +0000 (UTC)
Delivered-To: ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 436BEAA12FF
 for <ports@mailman.ysv.freebsd.org>; Mon,  8 Feb 2016 06:30:50 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 056CC1393
 for <ports@freebsd.org>; Mon,  8 Feb 2016 06:30:50 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.86 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1aSfLS-000Jvo-Ba; Mon, 08 Feb 2016 07:30:46 +0100
Date: Mon, 8 Feb 2016 07:30:46 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: qjail1 <qjail1@a1poweruser.com>
Cc: ports@freebsd.org
Subject: Re: port maintainer address
Message-ID: <20160208063046.GV46096@home.opsec.eu>
References: <56B56114.1000401@a1poweruser.com>
 <20160206063406.GP46096@home.opsec.eu>
 <56B80099.3070606@a1poweruser.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <56B80099.3070606@a1poweruser.com>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 06:30:50 -0000

Hi!

> I ask WHY is the 
> Freebsd ports system using a very old methodology that was designed over 
> 20 years ago, before the birth of spam.

There was spam, even more than 20 years ago.

> The majority of customer 
> websites and programming development websites all have protected their 
> user email addresses, WHY NOT FREEBSD?

Maybe because it's not a big problem in general ? It's annoying etc,
but not a big problem ?

> It's way past the time that this problem gets the attention it deserves.

If you have code and ideas on how to handle this, put in a problem
report in bugs.freebsd.org. If some activist can be found to fight
this cause, it will probably be solved.

-- 
pi@opsec.eu            +49 171 3101372                         4 years to go !