[editors note: removed a lot of the quoting of previous discussion] On 2006-07-30, Gary V <[EMAIL PROTECTED]> wrote: > Micah wrote: > >>>>>> Jul 2 11:31:07 buffy amavisd-new[2975]: (02975-29) Decoding of >>>>>> part-00001 >>>>>> (bzip compressed data, version: 7, compression block size 200k) failed, >>>>>> leaving it unpacked: Error running decompressor /usr/bin/bzip2 -d on >>>>>> part-00001, exit status 2 at /usr/sbin/amavisd-new line 4208. >>>>> >>>>>> and >>>>> >>>>>> Jul 2 11:31:07 buffy amavisd-new[2975]: (02975-29) TROUBLE in >>>>>> check_mail: >>>>>> decoding2-get-file-types FAILED: 'file' utility (/usr/bin/file) failed, >>>>>> status=255 (65280 ) at /usr/sbin/amavisd-new line 3853. >>>>> > Are you using a version of file(1) that is at least from 'stable' > (I have 4.12-1). Are these errors crashing amavisd-new?
I've got file(1) from 'stable': file: Installed: 4.12-1 The errors are not crashing amavisd-new, it keeps running. > What other errors are there (if any) that are related to this message? > Are we seeing the complete picture? Is the evidence preserved where > it may be tested on another system? There appear to be three messages associated with each of these. The first is the Decoding of part-0000x gzip failed, error running decompressor. The second is the TROUBLE in check_mail, decoding2-get-file-types FAILED: 'file' utility failed status=255. (these are quoted above), and then the third is: Jul 30 06:35:21 buffy amavisd-new[29274]: (29274-26) PRESERVING EVIDENCE in /var/lib/amavis/tmp/amavis-20060730T062903-29274 I had a look at this one, it exists, and this one actually looks like a genuine email, with a gnumeric attachment, the email body has a bunch of portugese characters in it. I looked at another one, this one happened to also be a legitimate email, didn't have UTF text, but had a jpg attachment. The directory contains an email.txt and a parts directory. How can I take that to another system and test it? > I could be wrong but I'm thinking if these do not crash amavisd-new > then this is mostly an annoyance that may likely be solved by upgrading > amavisd-new. These may provide food for thought: > > http://www200.pair.com/mecham/spam/debian-amavisd-new_2.4.1.html > http://www200.pair.com/mecham/spam/upgrade242.html I see, its a bit of a process to upgrade, and would mean that I'd have to disable virus protection while I sort out the configuration changes. > > This post has a suggestion also, but I question whether Sarge in > particular has an issue with this, and while the workaround mentioned > would probably work, whether it is the best way to fix the situation. > > http://archives.neohapsis.com/archives/postfix/2006-01/0090.html I've actually got that change in place already, its the first thing I tried when I tried to fix this problem. > I wonder if installing file(1) from testing may offer any relief. There is a file(1) from backports (4.17-0bpo1), I'm going to install it and see how it goes. Micah ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
