On 2015-12-13, Ian Zimmerman <itz@???> wrote: > On 2015-12-12 21:34 -0600, Robert Steinmetz wrote:
>
>> How would one implement your suggestion in an Ubuntu/Debian server?
>>
>> The git hub link I provided in my original post also seems a valid approach, but
>> Again, I'm not sure how to implement it in a Debian/Ubuntu environment.
>>
>> Please be gentle.
>
> Maybe, as a first step, you could move from the Debian configuration
> infrastructure for exim to a hand edited configuration file. The exim4
> package is already prepared for that; all you have to do is to create
> the configuration file as /etc/exim4/exim4.conf. You can start with the
> example configuration /usr/share/doc/exim4-base/examples/example.conf.gz
> and make changes as necessary.
>
> While it _is_ possible to achieve your goal within the Debian
> infrastructure, it involves creating or modifying files in an entire
> tree of configurations [1], which many find not "intuitive" and/or
> unfamiliar.
>
> I am reasonably sure that Ubuntu is exactly the same as Debian with
> respect to Exim.
it's not that hard to work within the debian confug tree you just
need to read the debian specific documentation first.
the only real difficulty is that syntax error messages will not give
the address of the error but instead point to the generated file.
The reason behind this config splitting is so that debian can offer
seamless ingeration with other mail processing packages like
spamassassin and clamav using connector packages that drop additional
config files into the config tree to activate the integration.
One big advantage of split config is that when exim is upgraded by
debian your changes will persist while the stock config files are
updated. saving you from crawling through a 2000 line config file.
duplicating all the edits.
