From owner-freebsd-ports@FreeBSD.ORG Wed Oct 23 17:27:03 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 602C648D for ; Wed, 23 Oct 2013 17:27:03 +0000 (UTC) (envelope-from trashcan@odo.in-berlin.de) Received: from mx1.enfer-du-nord.net (mx1.enfer-du-nord.net [91.121.60.26]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E8D542F55 for ; Wed, 23 Oct 2013 17:27:02 +0000 (UTC) Received: from sulu.fritz.box (p5DDC3A2F.dip0.t-ipconnect.de [93.220.58.47]) by mx1.enfer-du-nord.net (Postfix) with ESMTPSA id 3d4dn11RwTzCwv for ; Wed, 23 Oct 2013 19:27:01 +0200 (CEST) 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: <201310231649.25418.Mark.Martinec+freebsd@ijs.si> Date: Wed, 23 Oct 2013 19:27:00 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <006005D4-8E88-4D5F-B614-DEA24072F7AC@odo.in-berlin.de> References: <201310231649.25418.Mark.Martinec+freebsd@ijs.si> To: "freebsd-ports@freebsd.org" X-Mailer: Apple Mail (2.1510) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2013 17:27:03 -0000 Hi Marc -- On 23.10.2013, at 16:49, Mark Martinec = wrote: >> amavis[12345]: (12345-02) (!)file utility failed: exit 1 >>=20 >> 1. Do others see those warning messages as well, running the = combination >> amavisd-new 2.8.0 and file 5.15? 2. Can one safely ignore those = messages? >=20 > If it occurs on a rare occasion, it is probably safe to ignore, > otherwise it would be worth investigating. It is happening on every single mail passing amavisd.=20 > Other option is to enable debug logging (e.g. '# amavisd debug'), > and grep for 'result line from file' in the log. Here is the log file's excerpt for a plain ASCII mail message with 1000 = 'x'=20 in the body, sent to an echo mailer: | (50329-01) Issued a new file name: p001 | (50329-01) Charging 1000 bytes to remaining quota 792500 (out of = 792500, (0%)) - by mime_decode | (50329-01) p001 1 Content-Type: text/plain, size: 1000 B, name:=20 | (50329-01) get_deadline mime_decode - deadline in 270.0 s, set to = 189.000 s | (50329-01) prolong_timer mime_decode: timer 189, was 189, deadline in = 270.0 s | (50329-01) get_deadline mime_decode-1 - deadline in 270.0 s, set to = 189.000 s | (50329-01) prolong_timer mime_decode-1: timer 189, was 189, deadline = in 270.0 s | (50329-01) inspect_dsn: parts: text/plain | (50329-01) inspect_dsn: not a bounce | (50329-01) get_deadline dsn_parse - deadline in 270.0 s, set to = 189.000 s | (50329-01) prolong_timer dsn_parse: timer 189, was 189, deadline in = 270.0 s | (50329-01) decode_parts: level=3D1, #parts=3D1 : p001 | (50329-01) running file(1) on 1 files, arglist size 24 | (50329-01) run_command: [3984] /usr/local/bin/file p001 &1 | (50329-01) result line from file(1): p001: ERROR: line 163: regex = error 17, (illegal byte sequence)\n | (50329-01) lookup_re("ERROR: line 163: regex error 17, (illegal byte = sequence)") matches key "(?^:^ERROR:)", result=3D"dat" | (50329-01) lookup [map_full_type_to_short_type] =3D> true, "ERROR: = line 163: regex error 17, (illegal byte sequence)" matches, = result=3D"dat", matching_key=3D"(?^:^ERROR:)" | (50329-01) File-type of p001: ERROR: line 163: regex error 17, = (illegal byte sequence); (dat) | (50329-01) (!)file utility failed: exit 1 Well, I have to admit: The interpretation of those lines are far beyond = my scope ... Questions: 1) Is the file utility to blame? 2) My setup? 3) What else might I do to investigate this issue? >> 3. May "$file =3D '/usr/bin/file';" in amavisd.conf function as a = valid >> workaround for the time being? (I have to admit that I didn't dare = testing >> that, yet) >=20 > Yes, that is certainy a viable option. After activating that option, and testing with "amavisd debug" as = outlined above, I'll get: | (71656-01) Issued a new file name: p001 | (71656-01) Charging 1000 bytes to remaining quota 792500 (out of = 792500, (0%)) - by mime_decode | (71656-01) p001 1 Content-Type: text/plain, size: 1000 B, name:=20 | (71656-01) get_deadline mime_decode - deadline in 270.0 s, set to = 189.000 s | (71656-01) prolong_timer mime_decode: timer 189, was 189, deadline in = 270.0 s | (71656-01) get_deadline mime_decode-1 - deadline in 270.0 s, set to = 189.000 s | (71656-01) prolong_timer mime_decode-1: timer 189, was 189, deadline = in 270.0 s | (71656-01) inspect_dsn: parts: text/plain | (71656-01) inspect_dsn: not a bounce | (71656-01) get_deadline dsn_parse - deadline in 270.0 s, set to = 189.000 s | (71656-01) prolong_timer dsn_parse: timer 189, was 189, deadline in = 270.0 s | (71656-01) decode_parts: level=3D1, #parts=3D1 : p001 | (71656-01) running file(1) on 1 files, arglist size 18 | (71656-01) run_command: [71668] /usr/bin/file p001 &1 | (71656-01) result line from file(1): p001: ASCII text\n JYFI and with kind regards, Michael=20