[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: exim4: avoiding "retry time not reached for any host"

On 2006-10-02 22:55:42 +0200, Predrag Gavrilovic wrote:
> I don't understand you.
> bug 32877 is about not being able to merge old and new configuration
> files, and I don't think it would be smart thing to do across major
> version upgrades.

I'm using testing, so that exim config files are often modified
(almost each time there is an upgrade).

> And even then you allways have the option to keep the old file. Nothig
> gets blindly overwritten.

Without manual intervention (which I want to avoid), there are two

  1. Keep the old config files, but that's a bad idea IMHO, because
     they are improved/fixed by exim upgrades, and I'm not sure that
     old config files still work in the same way with new binaries.

  2. Use the new config files provided by new exim versions, but any
     change is overwritten.

That's why config file merging would be useful, at least when the user
has done minor changes (such as the change of a time value).

> My exim4.conf.template survived at least one security update
> unchanged, as it should.
> exim4.conf.template is THE place where you confiure Exim4 on debian.

There's also /etc/default/exim4, where I could change the queue
interval and the Maildir location. And this config file is not
modified by upgrades.

Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Reply to: