From owner-freebsd-ports@freebsd.org  Wed Dec 13 18:10:01 2017
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 40BFCE81B00
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Wed, 13 Dec 2017 18:10:01 +0000 (UTC)
 (envelope-from dan@langille.org)
Received: from clavin2.langille.org (clavin2.langille.org [199.233.228.197])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "clavin.langille.org",
 Issuer "BSD Cabal Headquarters" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 1F6567B975
 for <freebsd-ports@freebsd.org>; Wed, 13 Dec 2017 18:10:00 +0000 (UTC)
 (envelope-from dan@langille.org)
Received: from (clavin2.int.langille.org (clavin2.int.unixathome.org
 [10.4.7.7]) (Authenticated sender: hidden) with ESMTPSA id B83761F8B8 ; 
 Wed, 13 Dec 2017 18:09:52 +0000 (UTC)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Subject: Re: Procmail Vulnerabilities check
From: Dan Langille <dan@langille.org>
In-Reply-To: <20171213172720.GA2016@esprimo.local>
Date: Wed, 13 Dec 2017 13:09:36 -0500
Cc: freebsd-ports@freebsd.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <49EE56FC-EDAA-43B1-AA01-A5445DD99155@langille.org>
References: <fb3d23c5-e32d-452a-a0c3-c3cb12340054@cloudzeeland.nl>
 <a66d1c33-e405-d9e8-d9c3-2738b5e66887@cloudzeeland.nl>
 <alpine.BSF.2.21.1712080956580.41281@wonkity.com>
 <230a4255-839b-0ff8-9730-c86425ab3d5d@cloudzeeland.nl>
 <20171213172720.GA2016@esprimo.local>
To: Christoph Brinkhaus <c.brinkhaus@t-online.de>
X-Mailer: Apple Mail (2.3445.5.20)
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.25
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: Wed, 13 Dec 2017 18:10:01 -0000

> On Dec 13, 2017, at 12:27 PM, Christoph Brinkhaus =
<c.brinkhaus@t-online.de> wrote:
>=20
> On Wed, Dec 13, 2017 at 11:35:55AM +0100, Jos Chrispijn wrote:
>> On 8-12-2017 17:58, Warren Block wrote:
>>> procmail is ancient, and has had known quality issues for much of =
the=20
>>> time.  Consider maildrop as a more powerful and more maintained=20
>>> replacement that is pretty easy to implement:
>> I know - but I can remember that procmail should be installed also =
when=20
>> using Postfix.
>> Might be wrong here...
>=20
> Dear Joe,
>=20
> I have replaced procmail by maildrop recently using it with Postfix.
> There has been just one single obstacle. I run fetchmail as suer
> fetchmail started with the entry in /etc/rc.conf. The mails have been
> delivered to Postfix which involked procmail to distribute the mail.
>=20
> With maildrop this did not work initially. Adding the user fetchmail
> to /etc/aliases with a proper alias address followed by the command
> newaliases fixed that.

I like such replacements.

However, if third party code is required, there is little we can do in =
the short term.

Case in point: security/logcheck.

I went upstream looking to see why Debian uses that.

I cannot recall exactly what it was, but it wasn't procmail, but another =
utility provide by procmail.

I stopped there.

--=20
Dan Langille - BSDCan / PGCon
dan@langille.org