------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://www.exim.org/bugzilla/show_bug.cgi?id=458
------- Comment #12 from holmgren@??? 2007-02-07 21:31 -------
On Wednesday 07 February 2007 17:29, Philip Hazel wrote:
> On Wed, 7 Feb 2007, holmgren@??? wrote:
> > On Wednesday 07 February 2007 16:31, ph10@??? wrote:
> > > As far as I can see, it *does* always call parse_extract_address().
> >
> > It does? Where? When testing, I get:
> > > ${if match_address {"Magnus Holmgren"
> > > <holmgren@???>}{*@lysator.liu.se}{yes}{no}}
>
> Did I misunderstand? I though you were talking about ${address:
You didn't RWIM. :-) Of course ${address:...} calls
parse_extract_address() - that's all it's there for.
> As far as match_address goes, I don't see why one would ever want to
> supply a full RFC2822 address.
${if match_address {$h_From:}{+something}} instead of ${if match_address
{${address:$h_From:}}{+something}}. Less typing :-) and a slight compensation
for having to apply ${address_list:} to $h_To: etc. when there is no
foranyaddress/foralladdresses. Unless address_list does extract the
effective addresses instead of merely converting the commas and doubling the
nonseparating colons. But in that case I find the name "addresses"
appropriate, for it does exactly the same thing as ${address:}, but in
plural.
--
Configure bugmail:
http://www.exim.org/bugzilla/userprefs.cgi?tab=email
