- Previous message: mouss: "Re: auto.reply"
- Maybe in reply to: Vlada Macek: "Stucked mail from amavis"
- Next in thread: Tim Weippert: "Re: Stucked mail from amavis"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
|
|
|
From: mouss (no email)
Date: Tue Jan 03 2006 - 17:02:40 EST
Vlada Macek a écrit :
> Today I experienced a queue stucked mail. Amavis was unable to unpack a
> gzipped attachment:
>
> -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
> 366C29C0A5 71028 Tue Jan 3 16:27:13 E at MAIL1
> (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing,
> id=17863-06, decoding2-get-file-types FAILED: 'file' utility
> (/usr/bin/file) failed, status=255 (65280 ) at /usr/sbin/amavisd-new
> line 3853. (in reply to end of DATA command))
> E at MAIL2
>
> Corresponding log lines are:
>
> Jan 3 16:27:28 amavis[29925]: (29925-01) Decoding of part-00003 (gzip
> compressed data, from Unix, max compression) failed, leaving it
> unpacked: Error running decompressor /bin/gzip -d on part-00003, exit
> status 1 at /usr/sbin/amavisd-new line 4208.
> Jan 3 16:27:28 amavis[29925]: (29925-01) 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.
> Jan 3 16:27:28 amavis[29925]: (29925-01) PRESERVING EVIDENCE in
> /var/lib/amavis/amavis-20060103T162727-29925
> Jan 3 16:27:28 postfix/lmtp[31198]: 366C29C0A5: to=<E at MAIL2>,
> relay=127.0.0.1[127.0.0.1], delay=15, status=deferred (host
> 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=29925-01,
> decoding2-get-file-types FAILED: 'file' utility (/usr/bin/file) failed,
> status=255 (65280 ) at /usr/sbin/amavisd-new line 3853. (in reply to end
> of DATA command))
>
> Logcheck is of course mailing me similar new lines everytime Postfix try
> to redeliver the message, which is often. :-)
>
> Looking at the part-00003 I found it's an incomplete gzip file. That's
> why gzip exits with return code 1.
>
> What is the best way of handling such messages? I was looking up for how
> to command Postfix to bounce an arbitrary queued message to the sender
> immediately with some nice DSN, but I haven't found it.
if you fail to check it, either reject it or quarantine it. reject if
you are in smtp level (proxy_filter) and quarantine otherwise.
It would be great if you can provide the file that caused this, so as to
find out what is the causing the issue (and give Mark enough data to fix
amavisd if it proves necessary).
|
|
|