On Fri, Aug 21, 2009 at 5:09 PM, J.P. Trosclair <[email protected]
> wrote:

>
> Oscar m Cruz wrote:
>
>> F003D25C001     2057 Fri Aug 21 16:10:58  [email protected]
>> (host 127.0.0.1[127.0.0.1] said: 451-4.5.0 Error in processing,
>> id=08510-11,
>> virus_scan FAILED: virus_scan: ALL VIRUS SCANNERS FAILED: ClamAV-clamd
>> av-scanner FAILED: CODE(0x816e564) Too many retries to talk to
>> 127.0.0.1:3310 (Can't connect to INET socket 127.0.0.1:3310: Connection
>> refused) at (eval 69) line 310. at (eval 69) line 511.; Avira AntiVir
>> av-scanner FAILED: /usr/sbin/antivir unexpected exit 200, output="error
>> (not
>> enough memory available):  451-4.5.0  451-4.5.0 AntiVir / Linux Version
>> 2.1.10-15 451-4.5.0 Copyright (c) 2007 by Avira GmbH. 451-4.5.0 All rights
>> reserved. 451 4.5.0 " at (eval 69) line 511.; ClamAV-clamscan av-scanner
>> FAILED: /usr/bin/clamscan run_command (open pipe): Can't fork at
>> /usr/lib/perl5/5.8.8/i586-linux-thread-multi/IO/File.pm line 192. at
>> /usr/sbin/amavisd line 2565. at (eval 69) line 511. (in reply to end of
>> DATA
>> command))
>>                                          [email protected]
>>
>>
>
> Notice the out of memory error above:
>        error (not enough memory available)
>
> I've seen this happen on our server before when people send us emails with
> large attachments. Check your mailq (postqueue -p) output, look at the size
> column. You may have a message in there that's so large is crashing amavisd
> while it attempts to scan it. If this indeed the problem you may want to
> extract or delete it (postsuper & postcat) from the mail spool and look at
> setting a lower message_size_limit in your main.cf file.
>
>
> Thanks for your fast answer


   from now on i'm gonna block all messages with large attachments get more
memory
   'cause i running a cron backups and this is get me slowly tooo


    Regards

Reply via email to