Re: [sieve] extracting address behavior changes beetwen 2.2.13 and 2.2.16

5 May 2015


      W dniu 05.05.2015 o 13:46, Stephan Bosch pisze:
...
Marcin Mirosław schreef op 5-5-2015 om 11:48:
...
Hi all!
After upgrading dovecot from 2.2.13 to 2.2.16 I noticed that my sieve
filters doesn't catch some emails. I used sieve-test with tracing (it's
great tool!) and I can see as below:
part of sieve filter:
[...]
elsif address :is "From" "backup@areda.pl" {
[...]
dovecot-2.2.13:
36: address test
36:   starting :is' match with i;ascii-casemap' comparator:
36:   extracting From' headers from message    36:   parsing address header value =?UTF-8?B?QmFjdWxhQEFUTQ==?=
<backup@areda.pl>'
36:   extracting all' part from address backup@areda.pl'
36:   matching value backup@areda.pl'    36:     with key backup@areda.pl' => 1
36:   finishing match with result: matched
36: jump if result is false
36:   not jumping
dovecot-2.2.16:
36: address test
36:   starting :is' match with i;ascii-casemap' comparator:
36:   extracting From' headers from message    36:   parsing address header value Bacula@ATM <backup@areda.pl>'
36:   extracting all' part from address Bacula@ATM'
36:   matching value Bacula@ATM'    36:     with key backup@areda.pl' => 0
36:   finishing match with result: not matched
36: jump if result is false
36:   jumping to line 43
So in newer dovecot sieve uses comment not exact email address. Did I
wrongly wrote my sieve script?
Fixed:
http://hg.rename-it.nl/dovecot-2.2-pigeonhole/rev/a3d26f12c2cd
Thank you!
Marcin