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

* Your Email Address
* Spam protection	Enter the letters below: .__ ._.. . __.. . \| \ \| \|__\|(__ \|\ \| \|__/_\|_\| \|.__)\| \\|
Comment	> 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(); > >
Attachment
Watch this ticket