Re: amavis[12345]: (12345-02) (!)file utility failed: exit 1

2014-03-04 Thread Scot Hetzel
On Tue, Mar 4, 2014 at 12:19 PM, Michael Grimm wrote: > Hi -- > > On 04.03.2014, at 14:04, Scot Hetzel wrote: >> On Mon, Mar 3, 2014 at 10:39 AM, Michael Grimm >> wrote: > >>> amavisd-new requires sysutils/file which throws an error > > [...] > >> I checked the Magdir/windows file and the bug i

Re: amavis[12345]: (12345-02) (!)file utility failed: exit 1

2014-03-04 Thread Michael Grimm
Hi -- On 04.03.2014, at 14:04, Scot Hetzel wrote: > On Mon, Mar 3, 2014 at 10:39 AM, Michael Grimm > wrote: >> amavisd-new requires sysutils/file which throws an error [...] > I checked the Magdir/windows file and the bug is still there. You > will need to apply the patch that is in PR 1832

Re: amavis[12345]: (12345-02) (!)file utility failed: exit 1

2014-03-04 Thread Scot Hetzel
On Mon, Mar 3, 2014 at 10:39 AM, Michael Grimm wrote: > 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 ... > > |

Re: amavis[12345]: (12345-02) (!)file utility failed: exit 1

2014-03-03 Thread Michael Grimm
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: r

Re: amavis[12345]: (12345-02) (!)file utility failed: exit 1

2013-10-23 Thread Scot Hetzel
On Wed, Oct 23, 2013 at 1:25 PM, Michael Grimm wrote: > Hi -- > > On 23.10.2013, at 20:03, Mark Martinec wrote: > >> The text "ERROR: line 163: regex error 17, (illegal byte sequence)" >> comes from the file utility, unmodified. >> >>> 1) Is the file utility to blame? >> >> Yes. >> >>> 2) My setu

Re: amavis[12345]: (12345-02) (!)file utility failed: exit 1

2013-10-23 Thread Michael Grimm
Hi -- On 23.10.2013, at 20:03, Mark Martinec wrote: > The text "ERROR: line 163: regex error 17, (illegal byte sequence)" > comes from the file utility, unmodified. > >> 1) Is the file utility to blame? > > Yes. > >> 2) My setup? > > Possibly (e.g. broken magic database). > > Looks like a k

Re: amavis[12345]: (12345-02) (!)file utility failed: exit 1

2013-10-23 Thread Mark Martinec
Michael, > | (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) (!)file utility failed: exit 1 The text "ERROR: line 163: regex error 17, (illegal byte sequence)"

Re: amavis[12345]: (12345-02) (!)file utility failed: exit 1

2013-10-23 Thread Mark Martinec
Michael, > | (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) (!)file utility failed: exit 1 The text "ERROR: line 163: regex error 17, (illegal byte sequence)"

Re: amavis[12345]: (12345-02) (!)file utility failed: exit 1

2013-10-23 Thread Michael Grimm
Hi Marc -- On 23.10.2013, at 16:49, Mark Martinec wrote: >> amavis[12345]: (12345-02) (!)file utility failed: exit 1 >> >> 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 messag

Re: amavis[12345]: (12345-02) (!)file utility failed: exit 1

2013-10-23 Thread Mark Martinec
Michael, > amavis[12345]: (12345-02) (!)file utility failed: exit 1 > This is FreeBSD (9.2-STABLE, r256062), amavisd-new 2.8.0, and file 5.15. > Mailserver including amavisd is running in a service jail. > > After a recent port upgrade of file to 5.15, I do get warnings like

amavis[12345]: (12345-02) (!)file utility failed: exit 1

2013-10-23 Thread Michael Grimm
Hi -- This is FreeBSD (9.2-STABLE, r256062), amavisd-new 2.8.0, and file 5.15. Mailserver including amavisd is running in a service jail. After a recent port upgrade of file to 5.15, I do get warnings like shown in the subject line. In order to debug that issue I did replace the file 5.15 by t