"Michael Scheidell" <[email protected]> wrote on 22.2.2010 16:20:15:

>On 2/22/10 3:30 AM, miha vrhovnik @ domenca wrote:
>> Hi Mark,
>>
>> On messages with large attachments or attachments that contain a zip file 
>> with other zip files and in that inside zip files a large quantity of files 
>> I get the following error.
>> amavis[3816]: (03816-11) (!!)TROUBLE in check_mail: virus_scan FAILED: 
>> virus_scan: ALL VIRUS SCANNERS FAILED: ClamAV-clamd av-scanner FAILED: 
>> CODE(0x8a065f4) Exceeded allowed time at (eval 45) line 292. at (eval 45) 
>> line 491.
>>
>> the problem here is that after that happens amavis doesn't clean up the 
>> temporary directory. Which could result in filling up a disk space and as 
>> Murphy says it will happen in the middle of the night.
>>
>> Any chances to cook up a quick patch for that?
>>
>>    
>you can already tell clamav not to unzip past (x) number of levels, and 
as zip is uncommented in amavis config file in @decoders section and a large 
amount (1000)of partX files was in ./parts directory I believe decoding is 
already done by amavis.
>you can already give it a max archive size.
>the tmp dir cleanup can be done with a cronjob and find -mtime options.
How old directories I'm supposed to remove? 1h, half a day? I doubt that this 
would help much in a case I had. I had 2 legit! messages one just under 20M in 
size (this is the max server would allow) which had a zip file with 20 or so 
bmp files zipped in.. uncompressed size was around 120M + message itself 140M. 
The other was 8M in size with 5,5M zip file which contained 14 zip files with 
total above 1000 files mostly js, html, gif, css.. also around good 100M of 
decompressed files. Both of this messages burnt 50G of free space during the 
night!


-- 
No system, however painstakingly designed, can withstand the destructive force 
of an idiot who's found the power switch. 
-
Z lepimi pozdravi / Kind regards,

Miha Vrhovnik

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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/ 

Reply via email to