[Tickets #1378] NEW: change in whitelist sieve behavior?

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=1378
-----------------------------------------------------------------------
 Ticket             | 1378
 Created By         | liamr at umich.edu
 Summary            | change in whitelist sieve behavior?
 Queue              | Ingo
 Version            | 1.0.1
 State              | Unconfirmed
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


liamr at umich.edu (2005-02-14 16:07) wrote:

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 at 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 at example.com"]  { 
        keep;
        stop;
    } 

Or... line ~300 in lib/Script/sieve.php..

                $action = array();
                $action[] = &new Sieve_Action_Keep();
                $action[] = &new Sieve_Action_Stop();