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

2006-10-06 Thread Vincent Lefevre
On 2006-10-04 23:12:46 +0200, Predrag Gavrilovic wrote: > If you chose to keep old config file, new version gets saved with > *.dpkg-new extension. You can inspect if it has some new > features-settings worthy of replacing old config, and manualy merge > your specific changes. But I said I didn't

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

2006-10-04 Thread Predrag Gavrilovic
If you chose to keep old config file, new version gets saved with *.dpkg-new extension. You can inspect if it has some new features-settings worthy of replacing old config, and manualy merge your specific changes. 2006/10/3, Vincent Lefevre <[EMAIL PROTECTED]>: On 2006-10-02 22:55:42 +0200, Pred

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

2006-10-03 Thread Vincent Lefevre
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 oft

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

2006-10-02 Thread charles norwood
On Mon, 2006-10-02 at 22:55 +0200, Predrag Gavrilovic wrote: ---snip--- > 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. > > And even then you allways have the option to keep the old fil

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

2006-10-02 Thread Predrag Gavrilovic
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. And even then you allways have the option to keep the old file. Nothig gets blindly overwritten. And that goes only f

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

2006-10-02 Thread Vincent Lefevre
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 nice.

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

2006-10-02 Thread Predrag Gavrilovic
You should put them in /etc/exim4/exim4.conf.template, under the section that begins with "begin retry". Excuse me if I am teachig you things that you allready know, but just for the record, after that you should run update-exim4.conf, because, under Debian that's how you generate "real" exim4 c

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

2006-10-01 Thread Vincent Lefevre
On 2006-10-01 23:42:47 +0200, Predrag Gavrilovic wrote: > Part of the Exim configuration file are Retry rules wich govern how > often Exim (guess what) retries failed deliveries. You shoul'd adjust > that to your needs > > http://exim.org/exim-html-4.62/doc/html/spec_html/ch32.html Where do I wri

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

2006-10-01 Thread Predrag Gavrilovic
Part of the Exim configuration file are Retry rules wich govern how often Exim (guess what) retries failed deliveries. You shoul'd adjust that to your needs http://exim.org/exim-html-4.62/doc/html/spec_html/ch32.html 2006/9/28, Vincent Lefevre <[EMAIL PROTECTED]>: Hi, In /etc/default/exim4, I'

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

2006-09-28 Thread Vincent Lefevre
Hi, In /etc/default/exim4, I've set: QUEUEINTERVAL='5m' to run the queue every 5 minutes, as I often get temporary errors (in particular with the network where my machine is currently). But this is not sufficient, I still get things like that in my logs: 2006-09-28 10:28:35 Start queue run: pid