[AMaViS-user] ANNOUNCE: amavisd-new-2.6.4 released

2009-06-25 Thread Mark Martinec
Version 2.6.4 of amavisd-new has been released, it is available at: http://www.ijs.si/software/amavisd/amavisd-new-2.6.4.tar.gz release notes: http://www.ijs.si/software/amavisd/release-notes.txt The 2.6.4 is mainly a maintenance release over 2.6.3, but also brings a couple of new features

[AMaViS-user] Lookup lists priorities

2009-06-25 Thread Mikael Bak
Hi list, I am new here. I am not entirely new to amavisd-new, but I have a feeling I have a lot to learn. I am looking for that piece of documentation that describes exactly how amavisd-new does the lookups, what priorities an SQL-based lookup has compared to a statical list defined in amavisd.co

Re: [AMaViS-user] score_sender problem

2009-06-25 Thread Mark Martinec
Xavier, > I've some problem with soft whielisting : > Latest version installed: 2.6.1-r1 > A piece of my /etc/amavisd.conf: > > @score_sender_maps = ({ > '.' => [ > 'myaddr...@mydomain' => -15.0, > ], > }); > > in the log i get: > > lookup (score_sender), 1 matches for "myaddr...@mydomain'",

[AMaViS-user] score_sender problem

2009-06-25 Thread Xavier LANGLOIS
Hi there, I've some problem with soft whielisting : Latest version installed: 2.6.1-r1 A piece of my /etc/amavisd.conf: @score_sender_maps = ({ '.' => [ 'myaddr...@mydomain' => -15.0, ], }); in the log i get: lookup (score_sender), 1 matches for "myaddr...@mydomain'", results: "."=>["

Re: [AMaViS-user] SaneSecurity Signature Test #2 Failure

2009-06-25 Thread Michael Orlitzky
Noel Jones wrote: > Hrm, I thought the .ftm included with sanesecurity included most of the > common headers not in the "official" ftm, but it looks as if they mostly > address headers added by mailscanner. > > So create your own local.ftm file containing that header so clam knows > it's a mail

Re: [AMaViS-user] Exceeded storage quota problems

2009-06-25 Thread Jorgen Lundman
Hello, Patch applied without trouble and we will try the testing again. Thank you, Jorgen Lundman Mark Martinec wrote: > You are quite right, the do_uncompress should have propagated > the exception. It is a bug. > > Please try the patch below (agains 2.5.3), it fixes similar cases > in oth