Re: [AMaViS-user] Connection refused (no pid problem)

2007-01-02 Thread Ralf Hildebrandt
* sasa [EMAIL PROTECTED]: Hi, I have a problema with amavisd-new (my version is amavisd-new-2.3.1-1.1), in log file I have: .. (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: Connection refused) I have tried: #rm /var/amavis/amavisd.pid ..but the problem isn't

Re: [AMaViS-user] Connection refused (no pid problem)

2007-01-02 Thread sasa
Ralf Hildebrandt wrote: Have you restarted amavisd-new? ..yes. -- Salvatore. - 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

Re: [AMaViS-user] Connection refused (no pid problem)

2007-01-02 Thread Ralf Hildebrandt
* sasa [EMAIL PROTECTED]: Ralf Hildebrandt wrote: Have you restarted amavisd-new? ..yes. And is it running now? please show your postconf -n output. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450

Re: [AMaViS-user] locker entries

2007-01-02 Thread Gary V
Pavel wrote: Hello, when I've tried to raise the limit of amavisd-new processes to some insane value (128 I think) I've encountered this problem: Jan 1 19:37:55 antivir5 amavis[1170]: (!!)TROUBLE in child_init_hook: BDB no dbS: Lock table is out of available locker entries, . at (eval

Re: [AMaViS-user] maRBL on Debian

2007-01-02 Thread Vincent Li
On Tue, 2 Jan 2007, Gary V wrote: I installed maRBL 1.1 on a Debian system and it appears to be working. Oddly however the log output looks like: marbl: p0f query: %s port=%s %s %s marbl: p0f collect: max_wait=%.3f, %.35s... = %s marbl: Action for %s (%s = %s): %s As opposed to a Fedora

Re: [AMaViS-user] maRBL on Debian

2007-01-02 Thread Gary V
Gary wrote: I installed maRBL 1.1 on a Debian system and it appears to be working. Oddly however the log output looks like: marbl: p0f query: %s port=%s %s %s marbl: p0f collect: max_wait=%.3f, %.35s... = %s marbl: Action for %s (%s = %s): %s As opposed to a Fedora system: marbl: p0f

Re: [AMaViS-user] p0f/p0f-analyzer init.d script?

2007-01-02 Thread Shaun T. Erickson
On 1/1/07, Patrick Ben Koetter [EMAIL PROTECTED] wrote: I run a sloppy modified version from a p0f-init-skript that Dag Wieers created. You can download it here: http://postfix.state-of-mind.de/patrick.koetter/p0f Feel free to improve it. ;) Thanks! -- -ste

Re: [AMaViS-user] More detailed scanning time

2007-01-02 Thread Bob Pierce
On Fri, 2006-12-29 at 17:34 -0600, Noel Jones wrote: Is there any way to track how long each portion of the scan takes for a message? It would be handy to know for each message how long the virus scan took, how long the rbl checks take, how long FuzzyOCR takes... etc. Log level 2 (in

Re: [AMaViS-user] More detailed scanning time

2007-01-02 Thread Gary V
Bob wrote: On Fri, 2006-12-29 at 17:34 -0600, Noel Jones wrote: Is there any way to track how long each portion of the scan takes for a message? It would be handy to know for each message how long the virus scan took, how long the rbl checks take, how long FuzzyOCR takes... etc. Log level

Re: [AMaViS-user] More detailed scanning time

2007-01-02 Thread Noel Jones
At 03:10 PM 1/2/2007, Bob Pierce wrote: On Fri, 2006-12-29 at 17:34 -0600, Noel Jones wrote: Is there any way to track how long each portion of the scan takes for a message? It would be handy to know for each message how long the virus scan took, how long the rbl checks take, how long

Re: [AMaViS-user] maRBL on Debian

2007-01-02 Thread Gary V
Brian wrote: On 1/2/07, Gary V [EMAIL PROTECTED] wrote: I installed maRBL 1.1 on a Debian system and it appears to be working. Oddly however the log output looks like: marbl: p0f query: %s port=%s %s %s marbl: p0f collect: max_wait=%.3f, %.35s... = %s marbl: Action for %s (%s = %s): %s

Re: [AMaViS-user] More detailed scanning time

2007-01-02 Thread Bob Pierce
On Tue, 2007-01-02 at 14:24 -0700, Gary V wrote: Which makes me wonder, is there a performance benefit to running clamd instead of having spamassassin call clamscan? There is a hugh difference. Get clamd running. Actually, it's amavisd-new that calls virus scanners, not spamassassin.

Re: [AMaViS-user] maRBL on Debian

2007-01-02 Thread Gary V
Vincent wrote: Try to change line 87 and line 89 to: 87 $hostport =~ /^(?: inet: )? ([^:]*) : ([^:]*) /six 88 or die Bad p0f method syntax: $hostport; 89 my($host,$port) = ($1, $2); my($sock); and see if it make any difference. If it is not maRBL problem, then

Re: [AMaViS-user] maRBL on Debian

2007-01-02 Thread Brian Wong
snip Thanks Michael and Brian. Do you get these also when it tries to perform RBL checks? fatal: alarm time out at /usr/local/share/perl/5.8.4/Net/RBLClient.pm line 85. I think that is just Net::RBLClient complaining that a particular RBL didnt respond in time and is skipping it. Im not

[AMaViS-user] amavis processing pauses

2007-01-02 Thread Alan
Hey all, new to the list here. Our setup here at work is an amavis setup to filter mail for many domains and emails (typical isp-like environment). What happens ocassionally is that incoming mail will spike and then the mail queue starts to grow. Amavis processing becomes more sporatic, it

Re: [AMaViS-user] amavis processing pauses

2007-01-02 Thread Gary V
Alan wrote: Hey all, new to the list here. Our setup here at work is an amavis setup to filter mail for many domains and emails (typical isp-like environment). What happens ocassionally is that incoming mail will spike and then the mail queue starts to grow. Amavis processing becomes

[AMaViS-user] Ham email being blocked by amavisd-new?

2007-01-02 Thread Nathan Zabaldo
Is the following message coming from amavisd-new? This happens often when they are sending an email to someone within the same domain. How do I turn off spam scanning on outgoing mail in Amavisd-new so that only incoming email is scanned for spam? Or how else would I solve this problem? I have

Re: [AMaViS-user] maRBL on Debian

2007-01-02 Thread Henrik Krohns
On Tue, Jan 02, 2007 at 04:03:18PM -0700, Gary V wrote: I am going to let it go for a while by itself but will probably add (a somewhat permissive) policyd-weight back into the mix (ahead of selective greylisting). It would be very simple to add greylist command support to policyd-weight.