Scenario: ^test@$primary_hostname "$h_from:" Ffs ^test@$primary_hostname "<z...@gdzies.pl>" Ffs
First rule in some cases will return "yielded unparseable address: empty address in address" which is fine and expected. But exim will stop rewritting in such case. It won't go to next rule (which I wanted to be a fallback rule). And that's unexpected. Docs ( http://www.exim.org/exim-html-current/doc/html/spec_html/ch-address_rewriting.html ) don't seem to mention anything about such case, so I assumed next rewrite rule to be applied. For now I have a workaround for such problem: ^test@$primary_hostname "${if !eq {${address:$h_from:}}{} {${address:$h_from:}}fail }" Ffs ^test@$primary_hostname "<z...@gdzies.pl>" Ffs When "fail" is returned then exim uses next rule. I wonder if that's (stopping when unparseable address occurs) a bug (and exim should try next rule) or a feature (if feature then would be nice to see it documented) ? jgh_ on #exim suggests that this is a feature. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
