------- 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 #11 from [EMAIL PROTECTED]  2007-02-07 16:29 -------
On Wed, 7 Feb 2007, [EMAIL PROTECTED] wrote:

> ------- Comment #10 from [EMAIL PROTECTED]  2007-02-07 15:45 -------
> On Wednesday 07 February 2007 16:31, [EMAIL PROTECTED] 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" <[EMAIL PROTECTED]>[EMAIL PROTECTED]

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. 

-- 
Configure bugmail: http://www.exim.org/bugzilla/userprefs.cgi?tab=email

-- 
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details 
at http://www.exim.org/ ##

Reply via email to