Re: [AMaViS-user] Quarantine mails on error (AM.PDP)

2009-03-16 Thread David Schweikert
On Mon, Mar 16, 2009 at 18:40:49 +0100, Mark Martinec wrote: I agree it is too long. I'll make the following change: Perfect. Thanks! Each temporary failure should leave behind preserved temporary directory, along with a mail message (email.txt), available for later examination. The

[AMaViS-user] Quarantine mails on error (AM.PDP)

2009-03-13 Thread David Schweikert
Hi, We are using amavisd-new + amavisd-milter and, once in a while, a mail comes in that can't be scanned in the given $child_timeout time. The mail gets temporarily rejected like this (amavisd-new 2.6.2): 4.5.0 Error in processing, id=04844, virus_scan FAILED: virus_scan: ALL VIRUS SCANNERS

[AMaViS-user] TimeElapsedReceiving

2008-01-15 Thread David Schweikert
Hi Mark, I am using Amavisd-new only for virus scanning and have the following timings in amavisd-agent: TimeElapsedReceiving 10992 s 0.397 s/msg (InMsgs) TimeElapsedSending 44 s 0.002 s/msg (InMsgs) TimeElapsedTotal 17688 s

Re: [AMaViS-user] TimeElapsedReceiving

2008-01-15 Thread David Schweikert
On Tue, Jan 15, 2008 at 14:51:09 +0100, Mark Martinec wrote: TimeElapsedReceiving is the elapsed time (wall clock) between the reception of a MAIL FROM smtp command from a MTA (this is where a new smtp transaction starts) and the time when content checking begins (when check_mail() is called),

Re: [AMaViS-user] TimeElapsedReceiving

2008-01-15 Thread David Schweikert
Hi Mark, On Tue, Jan 15, 2008 at 15:46:41 +0100, Mark Martinec wrote: We keep three log files for amavisd at different syslog priorities: user.notice /var/log/amavisd.log user.info /var/log/amavisd-info.log user.debug/var/log/amavisd-debug.log The compact amavisd.log is kept

Re: [AMaViS-user] Letting big mails through

2008-01-10 Thread David Schweikert
On Wed, Jan 09, 2008 at 20:45:12 +0100, Mark Martinec wrote: Is there a way to configure Amavisd-new so that big mails (for example bigger as 10 MB) do not get virus-scanned? If not, is it possible to implement it with a custom hook? Not configurable, but can be done through a custom

[AMaViS-user] Letting big mails through

2008-01-09 Thread David Schweikert
Hi, Is there a way to configure Amavisd-new so that big mails (for example bigger as 10 MB) do not get virus-scanned? If not, is it possible to implement it with a custom hook? Cheers David - Check out the new

[AMaViS-user] Sophos SAVI and amavisd-new's UNDECIPHERABLE

2007-11-15 Thread David Schweikert
Hi, I was wondering, if it would be possible to mark the mail as 'UNDECIPHERABLE' if SAVI returns one of the error codes already defined here: if (! grep {$result == $_} (514,527,530,538,549) ) { $status = 2; $output = ERROR $query: $msg; } else { # don't panic on non-fatal

Re: [AMaViS-user] Postfix + Amavisd-new + Amavisd-milter

2007-07-30 Thread David Schweikert
On Sat, Jul 28, 2007 at 01:04:54 +0200, Mark Martinec wrote: Since the problem is in Socket::SOMAXCONN, this is where it should be fixed, probably not in Net::Server. It is unlikely the Perl core module will be fixed, at least not for the current version. But certainly, if you'd be willing to

Re: [AMaViS-user] Postfix + Amavisd-new + Amavisd-milter

2007-07-27 Thread David Schweikert
The mailing-list doesn't seem to like attachments so here is the patch for amavisd-milter inline: --- amavisd-milter/mlfi.c.orig 2007-07-27 14:02:47.068396000 +0200 +++ amavisd-milter/mlfi.c 2007-07-27 14:02:53.058402000 +0200 @@ -929,6 +929,18 @@ return SMFIS_TEMPFAIL; } +

[AMaViS-user] Postfix + Amavisd-new + Amavisd-milter

2007-07-27 Thread David Schweikert
Hi, I am using Postfix and am experimenting with the inline rejection of virus mails using amavisd-new combined with amavisd-milter. The reason for using the milter interface instead of smtpd_proxy_filter is that if you do inline rejection with smtpd_proxy_filter, you need to have as many

Re: [AMaViS-user] Postfix + Amavisd-new + Amavisd-milter

2007-07-27 Thread David Schweikert
On Fri, Jul 27, 2007 at 17:52:58 +0200, Mark Martinec wrote: The problem is that even though I properly limited the number of amavisd connections in amavisd-milter, amavisd does have a listen backlog (queuing of connecting clients) of maximum 5 clients. That is, if I have