Autor: Chuck Moore Data: A: Nico Erfurth CC: Chuck.Moore, exim-users Assumpte: Re: [Exim] failed to expand "${lookup{$local_part}lsearch{SYSTEM_ALIASES_FILE}}":
failed to open
On Fri, 9 Jul 2004, Nico Erfurth wrote:
> Chuck@??? wrote:
>
> > I, too, experienced a failure when testing exim-4.34 after having used 4.10 and 4.20
> > for many months. The error message I saw was regarding existance of the "aliases"
> > file.
> >
> > [Exim] failed to expand
> > "${lookup{$local_part}lsearch{SYSTEM_ALIASES_FILE}}"
> >
> > Since I had not had this problem before, I decided to compare my configure file as
> > used for 4.20 (which, thankfully, I had saved in advance!) with the 4.34 file after I had
> > made my modifications.
>
> The exim "installer" should take care of replacing the macro while
> installation. Clearly it will fail when you just COPIED the configure
> file from the source tree.
>
> Nico
> Well, I want to say that it didn't. I copied the config file from the 4.34
package (tar.gz which I obtained from exim.org). I printed it and I
printed my configure.4.20workedforme and I compared them side by side
making notes of any pertinent configuration info that I thought needed to
be put into the new one. Maybe where I missed the boat was in some other
file, but I don't know where that would have been.
Anyway, what I did was to replace the line as below. Recompiled and it
worked.
# data = ${lookup{$local_part}lsearch{SYSTEM_ALIASES_FILE}}
data = ${lookup{$local_part}lsearch{/etc/aliases}}
I did read the note and the NB in the new configure file. My aliases file
is (as you can see) in the default location.
I mean no disrespect, but it clearly is not just I; otherwise, I wouldn't
have found it three places in a google search of the error message text.
Be all that as it may, I am NUTS about Exim -- I've bought both books, and
we are doing stuff that people don't even think someone should want to do.
Thanks to Philip Hazel and to all of exim.org who have contributed to this
project.
