Benny Pedersen escreveu:
> On Mon, June 16, 2008 13:02, Leonardo Rodrigues Magalhães wrote:
>
>
>> anyway, it would be interesting if this 0.1 value is raised to
>> something more helpful .....
>>
>
> how ?
>
My idea is that amavisd.conf-sample, shipped with 2.6.0, that does
NOT define @virus_name_to_spam_score_maps, makes SaneSecurity extra
definitions almost useless.
As not defined on amavisd.conf, amavisd use it's own internal
default definition that gives 0.1 for SaneSecurity detected messages. As
0.1 probably wont change the 'spam-or-not' situation of almost all
messages, so i think 0.1 is PRETTY low and VERY much conversative value.
So i really think that raising this 0.1 to something higher (2 or
even 3) could be an interesting change.
I also think that this feature of virus_name_to_spam_score_maps,
altough pretty well detailed on RELEASE_NOTES, could be disabled by
default. It's an interesting feature, but lots of people probably doesnt
read the whole RELEASE_NOTES and, thus, can let AV-detected messages
pass through because of the feature being enabled and with that low
score, 0.1.
That's my idea about it .... :)
--
Atenciosamente / Sincerily,
Leonardo Rodrigues
Solutti Tecnologia
http://www.solutti.com.br
Minha armadilha de SPAM, NÃO mandem email
[EMAIL PROTECTED]
My SPAMTRAP, do not email it
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
