Your message dated Thu, 3 Jul 2008 06:42:32 +0000 (UTC)
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#482375: triggered by /etc/network/if-up.d/sendmail
has caused the Debian Bug report #482375,
regarding On some systems sendmailconfig doesn't recognise local host name
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
482375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482375
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: sendmail
Version: 8.13.8
Severity: normal
I have sendmail installed on several servers of different customers.
When I run sendmailconfig on _some_ servers I get message:
WARNING: local host name (;; connection timed out; no servers could be
reached) is not qualified; see cf/README: WHO AM I?
As we can see there in brackets is an error message instead of true
local host name. This message is returned from dns lookup procedure. But
dns lookup has no problem (responses are pretty fast):
hostname -f
server.example.com
host server.example.com
server.example.com has address 10.22.19.126
host 10.22.19.126
126.19.22.10.in-addr.arpa domain name pointer server.example.com
host -t mx example.com
example.com mail is handled by 10 server.example.com.
cat /etc/mailname
server.example.com
That error message appears on some lines in sendmail.cf too:
Dj;; connection timed out; no servers could be reached
Cw;; connection timed out; no servers could be reached
CG;; connection timed out; no servers could be reached
Which results in situation when other mail servers refuses e-mail from
this server for that nonsense name. I must repair it myself "by hands",
but Debian has "helpful" feature - after reboot is sendmail.cf
autogenerated again with those error messages inside.
I repeat: This problem occurs on some systems only. I can't find rule
causing this abnormality.
Thank you
Viktor Matys
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---
On Wed, 2 Jul 2008, Thomas Liske wrote:
Update_host() uses the find_host() to do the reverse lookup.
If $(host IP) returns ";; connection timed out; no servers could be
reached" this value is taken as you hostname and your sendmail is broken
if you have dialup.m4 included to your sendmail.mc.
Indeed, you're spot on.
This was exactly the fix added to 8.14.1-11, and later work was done
to further clean up the dynamic handling... It is still limited by the
information it can gather from if-up|down/dhcp/ppp/etc.
This fix will give some additional delay if the nameserver(s) in
/etc/resolv.conf are not reachable (i.e. localhost => bind is being
started some times later during bootup).
Also quite true :(
"Here, thar be dragons"
What started as a kluge for me and a few others to manage `proper servers`
whilst stuck behind DHCP/PPP links has wrought a plethora of problems (and
quite a few more rants) the years... (probably second to sendmailconfig
- which I inherited and am still loathe to touch; the rest of the blood
be upon my hands); sendmail.conf is right up there as well - but at
least it is getting better (comments) with age, unfortunately is so far
afield from the other distributions.
It's kinda hard to believe that my 1st upload of this package was
over 10 years ago... 8.8.8-10 on Sun, 8 Mar 1998 12:00:00 -0500
and I picked it up to force myself to re-acquaint myself with unix
and the still fairly new (to me) open-source movement :)
It has been a mostly fun ride, and one that I'd do again - even knowing
the issues... and I'm still not sorry for adding so many ad-hoc pieces
as people requested them ;)
Anyway, as this issue is solved in testing/unstable (hopefully soon to
be stable - lenny), I'm going to close this - with regrets that I don't
yet have a stable chroot to maintain backports on :(
--
Rick Nelson
<Knghtbrd> it's 6am. I have been up 24 hours
<Knghtbrd> Wake me up and risk life and limb.
* Knghtbrd &; sleep
<Tv> Okay everyone, we wait 10 minutes and then start flooding Knghtbrd
with ^G's. Someone, hack root and cat /dev/urandom >/dev/dsp.
--- End Message ---
