Sat, 25 May 2013 02:19:41 +0000 http://bugs.horde.org/ticket/1378 change in whitelist sieve behavior? The description for Ingo's whitelist is... "The whitelist is a list of (legitimate) email addresses that you always wish to see in your INBOX. Each address should be entered on a separate line." In it's current condition, when generating rule using the sieve backend, it generates rules that look like.. if address :all :comparator "i;ascii-casemap" :is ["From", "Sender", "Resent-From"] ["user@example.com"] { keep; } whitelist is the first rule be default, all "keep" does is mean "keep it in the inbox". Subsequent rules can still act upon these messages should they match the critera set forth in those rules. To accurately produce the behavior described in the help text, shouldn't there be a "stop" in the rule? if address :all :comparator "i;ascii-casemap" :is ["From", "Sender", "Resent-From"] ["user@example.com"] { keep; stop; } Or... line ~300 in lib/Script/sieve.php.. $action = array(); $action[] = &new Sieve_Action_Keep(); $action[] = &new Sieve_Action_Stop(); Tue, 15 Feb 2005 00:07:26 +0000 http://bugs.horde.org/ticket/1378#t5504 Makes sense to me. Changed in CVS and 1.0.2. Sun, 06 Mar 2005 13:29:27 +0000 http://bugs.horde.org/ticket/1378#t6080