On Tue, Oct 19, 2004 at 07:21:32AM -0400, Wakko Warner said:
> Please keep me in CC.
OK.
> > > used nor the spec. IIRC it does cache this!
> >
> > It appears to, but only for the first address lookup. In other words,
> > I have a list of domains that contain no real users - they all undergo
> > alias expansion and are remailed elsewhere to real email addresses (that
> > may then be forwarded again for all I know, but I'm just doing this hop).
> > When I try an address, say foo@???, it gets looked up in SQL, and
> > then later, when a routing decision is made based on +virtual_domains,
> > it uses the cached lookup. After alias expansion to bar@??? occurs
> > in that redirect router, however, and it is routing the second address,
> > exim has to make a new query - the results of the old aren't cached
> > any more. Now I have to decide which kind of lookup is less overhead :)
> > Since the connection is cached, I am betting multiple single key lookups
> > is better than two big ones here.
>
> Which version of exim are you using? I think it also depends on how you use
> the domainlist. a few releases ago, IIRC, Nico fixed the caching in the
> lookups. I haven't tested it at work to see exactly how it works. Just as
> long as it worked. I used MySQL instead of flat files to ease in mail
> server administration.
4.34, I believe. It would be good if it was fixed later, as it would
allow better caching on multi-recipient messages of the SQL lookup, but
it's not a huge performance hit for now.
Thanks again for all your help.
--
--------------------------------------------------------------------------
| Stephen Gran | Hummingbirds never remember the words |
| steve@??? | to songs. |
| http://www.lobefin.net/~steve | |
--------------------------------------------------------------------------
