Bug#375787: I've analysed this some more...

2007-10-20 Thread David Fries
On Thu, Oct 18, 2007 at 07:01:59PM -0700, Richard A Nelson wrote: > On Thu, 18 Oct 2007, Kees-Jan Dijkzeul wrote: > > This whole mess was concocted by me and a few others back when we were > forced to live on PPP/dialup or DHCP dsl/cable - and it worked just fine > for us, but at least I always ra

Bug#375787: I've analysed this some more...

2007-10-19 Thread Kees-Jan Dijkzeul
Richard A Nelson wrote: [...] >> /etc/network/if-up.d/sendmail 192.168.11.2 '' eth0 >> >> seems to solve the issue for me (dialup.m4 gets rewritten correctly, and >> isn't messed up again by subsequent ifup/ifdowns > > Exactly - you told it what your new address was, and that the domain > (provider

Bug#375787: I've analysed this some more...

2007-10-18 Thread Richard A Nelson
On Thu, 18 Oct 2007, Kees-Jan Dijkzeul wrote: The problem first occurred when I booted the box without the network cable plugged in. The network interface got configured with a remembered ip adress, but obviously, DNS is not available. Hence, the /etc/network/if-up.d/sendmail script failed (?) t

Bug#375787: I've analysed this some more...

2007-10-18 Thread Kees-Jan Dijkzeul
I've just recently had the same problem (sendmail 8.13.8-3 / Debian Etch) The problem first occurred when I booted the box without the network cable plugged in. The network interface got configured with a remembered ip adress, but obviously, DNS is not available. Hence, the /etc/network/if-up.d/se