On 13/07/16 21:45, Arkadiusz Miśkiewicz wrote:
> Scenario:
>
> ^test@$primary_hostname "$h_from:" Ffs
> ^test@$primary_hostname "<zupa@???>" 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 "<zupa@???>" 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)
Exim has applied your first rule, which gave an empty result. How
will any subsequent rule match the now-empty address?
> or a feature (if feature then would be nice to see it documented) ?
--
Jeremy
