On Fri, 2012-09-21 at 17:58 +0100, Jon Dowland wrote: > On Thu, Sep 20, 2012 at 07:10:18PM +0200, Martin Steigerwald wrote: > > I think its better to configure exim4 for single configuration file by > > whatever means is described in the wiki page Camaleón linked to, likely an > > > > dpkg-reconfigure exim4something > > We differ in our opinion. > > In my opinion, for anything but the simplest of deployments, the > Debian packaging introduces more complexity than it hides from you. > If you have to modify an exim configuration file by hand, and need > to know exim syntax, then you might as well do away with the Debian > framework. It just adds another layer that you need to understand, > with its own foibles and problems. > > I've been running exim on Debian for a long time and this was the best > piece of advice I was ever given on the matter. > I find the split configuration more convenient. For one thing, if one of the pieces gets updated your customizations will be unaffected. I'm not sure that's true with the monolithic configuration.
Second, it is unclear to me what the OP was trying to do. If the goal is to remove a header field from messages then you need to find the appropriate router in /etc/exim4/conf.d/router and add a header_delete directive. If you want to do it for all routers you can probably create a router that appears before the others, e.g. name the file 050_local_delete, and have the router delete the header and pass the message on (I don't recall the exact commands, but I think they exist). Another possible issue is that you may have trouble figuring out which router is active. If that is the case, your issue may be understanding the prebuilt config that comes with debian, rather than whether it is split or not. The package has a very useful README.Debian intended as a jumping off point for the documentation, e.g. /usr/share/doc/exim4-config/README.Debian.gz. Third, I'm a bit puzzled by Jon's remarks quoted above. Martin recommends using a single, aka monolothic configuration file. Jon says "I disagree" but then suggests doing away with the debian framework. Anyway, you can choose any of 3 approaches to configuration: 1. Use the split config in conjunction with the package management tools (debconf) to configure exim. 2. Like 1, but use the monolithic config file. It's not clear to if changes you make in debconf, or that the package might make on upgrade, will get integrated in to the monolithic file in this case. 3. Don't use the Debian config stuff, and the exim4-config package, at all and just write your own configuration file. Presumably you'd borrow from an existing one. If your needs are relatively simple and fit well into one of the types of setups the Debian configuration file is meant to support, that favors 1. As they get more complex, the balance may shift down the list, and is also just a matter of personal preference. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1348350518.21959.18.ca...@corn.betterworld.us
