Re: [Exim] Exim & MySQL

> > If I do: hosts = ${lookup mysql ..... }
> > and the query returns multiple hosts, I'd have this after expansion:
> > hosts = 127.0.0.1\n
> > 192.168.1.1\n
> > 192.168.1.2
>
> Aha! I see. What you are asking for is that newline be treated as a list
> item separator in addition to colon. I will put this on the WishList to
> think about.

That'll work =) It'd cut down on the confusion of using the ${sg{}{}{}}.

What happens if I do:
hosts = ${lookup mysql .... }

and the lookup returns say 10,000 rows (also assuming \n is a seperator like
: is). How would exim handle this? I'm sure on systems with loads of
memory it wouldn't be a problem.


Just off the top of my head, is there an easy way (or possible) to convert
an @@lsearch* into an sql db?

If I could have a lookup that uses another lookup, IMO, I don't think that'd
be a problem (unless reading all rows is).