Re: exim4: avoiding "retry time not reached for any host"
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
And even then you allways have the option to keep the old file. Nothig
gets blindly overwritten.
And that goes only for major version updates. Minor security updates
go with no problem at all.
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.
2006/10/2, Vincent Lefevre <firstname.lastname@example.org>:
On 2006-10-02 14:56:52 +0200, Predrag Gavrilovic wrote:
> You should put them in /etc/exim4/exim4.conf.template, under the
> section that begins with "begin retry".
But this file gets overwritten after an exim upgrade. So, until
bug 32877 (conffile merging) is fixed, this solution isn't very
I think something to put in /etc/default/exim4 would be better,
Vincent Lefèvre <email@example.com> - 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)
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org