------- 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=459 ------- Comment #3 from [EMAIL PROTECTED] 2007-02-01 10:14 ------- On Thu, 1 Feb 2007, [EMAIL PROTECTED] wrote: > ------- Comment #2 from [EMAIL PROTECTED] 2007-02-01 10:06 ------- > On Thursday 01 February 2007 10:34, [EMAIL PROTECTED] wrote: > > What should this key contain for a hosts condition? > > :-P > > Why, the hostname of course. So, if somebody says hosts = 192.168.1.1 which works quite happily now, you want Exim to try to look up a hostname before processing that list? Is that right? That is highly incompatible because it is resource-wasteful and there is the defer problem. > You'd have to use e.g. net-mysql to make the IP > address be the key, in a manner similar to single-key lookups. The string expansion happens *before* the list is scanned, and therefore *before* Exim knows what kind of items there are in the list. > But the big problem is that the query string is in many cases expanded before > it's passed to match_isinlist() or match_address_list(). That would have to > change. Massively incompatible change. I know this is an awkward area, but it has "grown up" that way, and to disturb it now would, I believe, cause hassle because it would almost certainly affect existing installations. Therefore, I think any change of this magnitude must be an "Exim 5" issue. Philip -- 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/ ##
