Re: [exim] Debian as a 'Special Case' for Exim

On Fri, 2005-02-18 at 11:45 -0200, José de Paula Eufrásio Júnior wrote:
> As some people here, I run exim on 2 debian mailservers. Using the
> -heavy version of the daemon (that is not so "heavy" on dependencies
> since I use spamassassin and clamav). I use a single configuration file
> handmade, and the fact that you just need to drop the file in the place
> and reload exim to use it is plain right.
> On the other servers and stations, including laptops, I use the debconf
> version, local delivery, and all works fine.
> The botton line is that if somebody has to streamline the exim
> configuration, do it in a handmade file, no need to worry about the
> debconf stuff or the conf.d files...

I use the conf.d approach for huge installation. It allows me to split
config down to a single file per virtual domain for routers. Well,
unless they want ACLs too. Then they get a default to manage how ever
they want.

The biggest concern that everyone here is voicing is the Itty-bitty
files... I love 'em, and I break any-body's hands that take that away
from me.

The bigfile (atm) can be generated from those itty bitty config files by
using a script called "update-exim4.conf" it then does all the
substitution with values in /etc/exim4/update-exim4.conf.conf.

using "update-exim4.conf --keepcomments" keeps all the comments in the
file and the header comments for every file it uses stay there.

It is simply EASY to re-order routers without making a typo in the conf
itself. Just rename the file to a different prefix to re-order it
(change 380 --> 350).

I currently love the fact I can give my vdominas a self manageable
file(s), allowing me to have them manage their own stuff. Users, aliases
redirects etc... all there for the using. Since exim does lookups on
these files in my setup, they can be updated anytime the customer wants.

This is also good, mainly because it allows me as a System admin to
create a method for customer self management through an https service
for themselves. I also have splitup all configs for all >For-Pay<
services similar to what Marc and Andreas and other have done. Even
better I have move this config system to other linux distros and even a
coupla BSD machines (FreeBSD if you must know)

This whole seperate file per vdomain for Apache (with or without
SCGI/PHP/Perl/Python per vdomain too, this way), MTAs, IMAPD, POP3D with
and without TLS/SSL etc... I figure the pattern made good by the Debian
Teams and the "structured way" to configure every thing with a common
mechanism is a very awesome thing.

There is only one thing now, when is upstream going to understand that
it IS the exim.conf the people had debconf generate using variable
substitution. Geez, you'd guys think it wasn't supportable. It truly is
elegant and not complex. It is tweak-able, scalable and very very easy
to understand and manageable.

Just rise-up and see the forest inspite of those trees that seem to
block your view.
--
greg, greg@???

The technology that is
Stronger, better, faster: Linux