Antoine,
I'm trying to configure a custom spam_kill_level for a specific domain
using an SQL policy but amavis doesn't want to apply it. I've already
define a custom spam_tag2_level using the same method and it works fine.
(example: tag2=1000, kill=1010)
I've tested with the GTUBE sample message. The message is put into
quarantine and here is what I can see into the headers:
X-Spam-Score: 999.001
X-Spam-Status: Yes, score=999.001 tag=2 tag2=1000 kill=6.9
tests=[ALL_TRUSTED=-1, DNS_FROM_RFC_DSN=0.001, GTUBE=1000] autolearn=no
*tag2=1000* corresponds to my custom value
*kill=6.9* corresponds to the default value but should be (from my point
of view) equal to 1010
Does the *spam_kill_level* field differs from the others ?
spam_kill_level is no different than spam_tag2_level in this regards,
should work the way you expected. A log at a higher log level
may tell what is happening. Perhaps you have spam_kill_level
in multiple matching records and the more specific one does
not have a higher priority field that the less specific.
Mark
