Tickets :: [#5834] Kill Level being set to 0 (Zero) when it should be NULL

6.0.0-beta1

7/27/25

Summary	Kill Level being set to 0 (Zero) when it should be NULL
Queue	Sam
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	2. Medium
Owners	jan (at) horde (dot) org
Requester	horde (at) mightytux (dot) com
Created	10/25/2007 (6485 days ago)
Due
Updated	09/02/2009 (5807 days ago)
Assigned	10/25/2007 (6485 days ago)
Resolved	12/04/2007 (6445 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

09/02/2009 05:09:30 PM	me (at) junc (dot) org	Comment #6	Reply to this comment
Fixed in CVS. Great, thanks! I have tested this on two webmail servers and it appears to do the trick. NULL in sql policy means that amavisd uses amavisd.conf values not just disabled hope to clear out this mistake

12/04/2007 09:13:45 PM	horde (at) mightytux (dot) com	Comment #5	Reply to this comment
Fixed in CVS. Great, thanks! I have tested this on two webmail servers and it appears to do the trick.

12/04/2007 04:33:25 PM	Jan Schneider	Comment #4 State ⇒ Resolved Assigned to Jan Schneider	Reply to this comment
Fixed in CVS.

10/25/2007 11:29:58 PM	horde (at) mightytux (dot) com	Comment #3	Reply to this comment
Which driver do you use? I'm using amavisd_sql

10/25/2007 11:24:01 PM	Jan Schneider	Comment #2 Priority ⇒ 2. Medium State ⇒ Feedback	Reply to this comment
Which driver do you use?

10/25/2007 08:23:48 PM	horde (at) mightytux (dot) com	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Kill Level being set to 0 (Zero) when it should be NULL Queue ⇒ Sam State ⇒ Unconfirmed	Reply to this comment
Using Sam with the amavis_sql backend. When a user changes their Spam Options without specifying a value for Kill Level, the kill level is set to 0. This causes any email with a spam score of zero or higher to be quarantined. Instead, if a user does not specify a value for Kill Level, it should be set to NULL so it is disabled.