Re: [exim-dev] [Bug 458] Expansion condition: forall and/or …

Page principale
Supprimer ce message
Répondre à ce message
Auteur: Philip Hazel
Date:  
À: bug458
CC: exim-dev
Sujet: Re: [exim-dev] [Bug 458] Expansion condition: forall and/or forany
On Wed, 7 Feb 2007, holmgren@??? wrote:

> ------- Comment #10 from holmgren@??? 2007-02-07 15:45 -------
> 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:
No, I didn't misunderstand. This is what you wrote:

Hmmm, would it hurt too much if ${address: ...} always called
parse_extract_address()? Obviously it causes a little bit of overhead
when it wasn't needed.

As far as match_address goes, I don't see why one would ever want to
supply a full RFC2822 address.

> I concur. address_list was that Kjetil T. Homme suggested. But isn't
> "addresslist" better, considering the "historical mis-design"?


I don't think I really mind, though "addresslist" is already an Exim
technical term, so might be misunderstood. I had considered something
like "regularize_address_list", but that's too long, and
"fix_address_list" is vague.

-- 
Philip Hazel            University of Cambridge Computing Service
Get the Exim 4 book:    http://www.uit.co.uk/exim-book