On Tue, 20 Mar 2001, Yann Golanski wrote:
>However, I think that it should all be kept in one file. I would not
>want to have a file for routers, one for ACLs, one for rewrites and a
>main one that would include them all. Athough it has the potential for a
>Lord of the Exim poem...
A include statement could actually be useful, though. Today you can
either generate the config-file or use -D options (or even have a special
name for each file, using CONFIG_FILE_USE_NO), but neither are really
perfect.
I often have specific configurations for spesific hosts, but wish to more
easily dist new exim.conf files. These host spesific files would most
often be static, but the general exim file changes quite often.
But it really isn't a big problem, since you could just generate them
using a script.
(I don't like to use -D since I like my init.d-scripts to be the same all
over.. Hmm, now that I think of it, a much better solution would be to
have the init.d-script read the host-spesific file and set the -D values).
So, it isn't really necessary..
>... I really need to stop lisening to the voices in my head.
