From owner-freebsd-ports@FreeBSD.ORG Mon Mar 3 16:39:25 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2F58F3D0 for ; Mon, 3 Mar 2014 16:39:25 +0000 (UTC) Received: from mx2.enfer-du-nord.net (mx2.enfer-du-nord.net [IPv6:2001:41d0:b:2cb:1:1:0:1]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E6C91CB0 for ; Mon, 3 Mar 2014 16:39:24 +0000 (UTC) Received: from sulu.fritz.box (p3EE2F37F.dip0.t-ipconnect.de [62.226.243.127]) by mx2.enfer-du-nord.net (Postfix) with ESMTPSA id 3fd6Wb239PzNL4 for ; Mon, 3 Mar 2014 17:39:23 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: amavis[12345]: (12345-02) (!)file utility failed: exit 1 From: Michael Grimm In-Reply-To: Date: Mon, 3 Mar 2014 17:39:21 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201310232003.39787.Mark.Martinec+freebsd@ijs.si> <029DD189-E4F7-441D-95A4-08E73327DBDB@odo.in-berlin.de> To: "freebsd-ports@freebsd.org" X-Mailer: Apple Mail (2.1510) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Mar 2014 16:39:25 -0000 Hi -- I'd like to come back on an issue reported last October (see thread = ending in = http://lists.freebsd.org/pipermail/freebsd-ports/2013-October/087175.html)= . amavisd-new requires sysutils/file which throws an error like ... | test> /usr/local/bin/file ascii.txt | ascii.txt: ERROR: line 163: regex error 17, (illegal byte sequence) ... whereas the system file utility acts as expected: | test> /usr/bin/file ascii.txt | ascii.txt: ASCII text I did notice it for the first time with file-5.15. Today I did upgrade = to file-5.17, and I do still see that error. According the message obove (see link) that bug should have been fixed = already, correct or am I mistaken? Thanks and with kind regards, Michael =20=