On Fri, 21 Nov 1997, Alpha Geek wrote:
> In sender_address_relay, I was using an sql lookup to determine valid
> domains. However, I'd unfortunately chosen some syntax there (using an
> @ sign) which conflicts with an address lookup in exim. Of course, the
> address lookup in exim checks to see if there is an @ sign in the text
> of the lookup itself.
Oh dear. Yet another case of insufficient foresight.
> I believe this is a bug. Address lookups should key off of the lookup
> type FIRST and foremost (a la nis:, dbm:, etc) and NOT from the raw text
> of what's specified after one of these special lookups. Heck, somebody
> may want to have a filename with an @ sign in it for one of these
> things.
Can you let me know the strings in question, please? The problem is that
address lookups can contain either unadorned domains, or complete
addresses (i.e. localpart@domain). The quickest way to distinguish is
just to look for the @, but in the light of your problem, perhaps I
should make exim spend more effort on parsing the item to ensure that
what precedes an @ is a syntactically valid local part.
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
--
*** Exim information can be found at
http://www.exim.org/ ***
