Re: [AMaViS-user] AWL, ALL_TRUSTED, From: = To: spam

2009-01-22 Thread Need Coffee
On Thu, Jan 22, 2009 at 5:07 PM, Jo Rhett wrote: > Are you using sendmail with amavisd-milter? If so there were some bugs > which caused the network path to be broken that have been fixed in the last > year. Things appeared to work, but in reality they didn't :-( Interesting... no, it's postfix

Re: [AMaViS-user] AWL, ALL_TRUSTED, From: = To: spam

2009-01-22 Thread Jo Rhett
Are you using sendmail with amavisd-milter? If so there were some bugs which caused the network path to be broken that have been fixed in the last year. Things appeared to work, but in reality they didn't :-( On Jan 22, 2009, at 7:36 AM, Need Coffee wrote: > There were a few threads on the

Re: [AMaViS-user] (!)DENIED ACCESS from IP 0.0.0.0, policy bank ''

2009-01-22 Thread Michael Scheidell
> Hi! > > When we get an high amount of emails through our amavisd-new server we get > the following error in our logs: > > (!)DENIED ACCESS from IP 0.0.0.0, policy bank '' Check the max_servers vs process limits in your MTA. I think the recommended value is about 1 more max_server (to allow fo

[AMaViS-user] (!)DENIED ACCESS from IP 0.0.0.0, policy bank ''

2009-01-22 Thread Jens Larsson
Hi! When we get an high amount of emails through our amavisd-new server we get the following error in our logs: (!)DENIED ACCESS from IP 0.0.0.0, policy bank '' It seems that amavisd-new doesn't get the connecting client ip-address and therefore rejects the request. Of course 0.0.0.0 isnt in o

Re: [AMaViS-user] Why does that message not have a score?

2009-01-22 Thread Michael Scheidell
> Dear list, > > every now and then, really seldom but still it happens that a message > slips through and doesn't get a score. The X-Spam* Headers are there, > but look like a NULL check: > > > In the logs I can see this amavis line: > Jan 22 05:34:12 ourhost amavis[30464]: (30464-11) Passed CLE

Re: [AMaViS-user] long list of mynetworks

2009-01-22 Thread Rocco Scappatura
> > >> originating recip. is local > > >> 0 0can't happen (open relay) > > >> 0 1inbound > > >> 1 0outbound > > >> 1 1internal-to-internal > > >>

Re: [AMaViS-user] SAs vbounce and autolearn

2009-01-22 Thread Michael Scheidell
99 too high??? :-[ (amavisd as a 'bounce_killer_score' that is 100 in the amavisd.conf-dist). does something similar. Justin Mason wrote: > have you changed the score of the vbounce rules from 0.1? this is why > you shouldn't ;) > > --j. > > On Thu, Jan 22, 2009 at 16:51, Michael Scheidell

[AMaViS-user] SAs vbounce and autolearn

2009-01-22 Thread Michael Scheidell
Just found out why, all of a sudden, users who never got blocked, now are getting blocked. Christmas, these brilliant people set up 'I am out of the office' messages, which spamassassin 'vbounce' sees as a 'bounce'. (seriously, is a OOO backscatter?) if you don't set tflags noautolearn on your

[AMaViS-user] AWL, ALL_TRUSTED, From: = To: spam

2009-01-22 Thread Need Coffee
Hi. There were a few threads on the SA mailinglist about it, but I have been unable to find anything useful... and all the SA chatter was complaining about not setting up trust correctly which in my case is dependent on amavisd and is correct. Like a lot of places we are getting spam like this:

[AMaViS-user] [newbie] - ClamAV doesn't seem to be doing anything...

2009-01-22 Thread Bernard T. Higonnet
System FreeBSD 7.0-RELEASE Amavisd-new amavisd-new-2.6.1 (20080629), Unicode aware ClamAV clamd daemon 0.94.2 freshclam daemon 0.94.2 3 machines are involved 192.168.3.102 postfix 192.168.3.103 clamd/freshclam 192.168.3.108 amavisd-new From am

Re: [AMaViS-user] long list of mynetworks

2009-01-22 Thread Rocco Scappatura
Mark, > >> originating recip. is local > >> 0 0can't happen (open relay) > >> 0 1inbound > >> 1 0outbound > >> 1 1internal-to-internal > >> > >>

[AMaViS-user] Why does that message not have a score?

2009-01-22 Thread Michael Monnerie
Dear list, every now and then, really seldom but still it happens that a message slips through and doesn't get a score. The X-Spam* Headers are there, but look like a NULL check: Received: from localhost (localhost [127.0.0.1]) by ourhost (Postfix) with ESMTP id 623A5424 for ;