** Changed in: sendmail (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/99459
Title:
[feisty] sendmail unable to automatically determine domain name
** Changed in: sendmail (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/99459
Title:
[feisty] sendmail unable to automatically determine domain name
--
** Bug watch added: Debian Bug tracker #375787
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375787
** Also affects: sendmail (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375787
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Forgot to mention that I already had explicit
define(`confDOMAIN_NAME',...
in my sendmail.mc, as well as
FEATURE(use_cw_file)dnl
and
GENERICS_DOMAIN_FILE(...
which pretty obviously make the dialup.m4 useless anyway.
--
[feisty] sendmail unable to automatically determine domain name
https://bugs.l
This hit me yesterday as well.
Since the network connection in the machine in question is static, I simply
removed the lines
include(`/etc/mail/m4/dialup.m4')dnl
include(`/etc/mail/m4/provider.m4')dnl
from sendmail.mc. As far as I can tell, none of the current config tools will
put them back,
This bug is from the upstream distribution. I hit it today on a Debian
lenny system.
See DBTS #375787
--
[feisty] sendmail unable to automatically determine domain name
https://bugs.launchpad.net/bugs/99459
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
This bug also seems to be upstream and unfixed in the Debian Etch
Sendmail package as bug 375787 . I have added the following report there
as follows:
My /etc/mail/m4/dialup.m4 contained:
define(`confDOMAIN_NAME', `;; connection timed out; no servers could be
reached')dnl
This seems to end up wi
Status changed to Confirmed as we all see the same issue. 3 months
untriaged for such a critical bug..
** Changed in: sendmail (Ubuntu)
Status: New => Confirmed
--
[feisty] sendmail unable to automatically determine domain name
https://bugs.launchpad.net/bugs/99459
You received this bug n
Be warned, your solution of moving dialup.m4 is only a temporary fix,
the problem will recurr in my experience.
My ultimate solution is to use postfix instead of sendmail. As this bug
is completely intolerable - it loses mail forever!!
--
[feisty] sendmail unable to automatically determine domai
In order to bypass the problem I did this after having edited dialup.m4
manually:
# cd /etc/mail/m4
# mv dialup.m4 dialup-good.m4
# ln -s dialup-good.m4 dialup.m4
I don't know why, but the function update_host() in
/usr/share/sendmail/dynamic, which is responsible for creating
dialup.m4, refrains
The same issue affects edgy i386. I have three of them as the
cpqd.com.br domain MXs. It seems that when /etc/network/if-up.d/sendmail
is called it cannot resolve the reverse of the host's IP address and
that strange string ends up being inserted in /etc/mail/m4/dialup.m4.
The problem occurs whene
I re-installed this feisty amd64 box with feisty i386. I've experienced
this sendmail issue once again. It's indeed the /etc/network/if-
up.d/sendmail script that produces that.
--
[feisty] sendmail unable to automatically determine domain name
https://bugs.launchpad.net/bugs/99459
You received t
[ for AMD64, I plan to go back to 32bit ASAP as so many things are
broken in AMD64. That was my first try with a 64bit linux, not ready for
my taste (I've been running Debian for 10 years, always the so called
unstable, both servers and desktops, I was happy). Well, maybe this
issue is not 64bit r
I'm not on AMD64, although I will be in a couple of weeks.
I have looked further into this and I've found that this problem is caused by
/usr/share/sendmail/dynamic this is sourced by /etc/network/if-up.d/sendmail
and then the /usr/share/sendmail/dynamic update_host() function is run by the
/e
hmm, are you on AMD64 ?
I have 3 boxes running Feisty, 2 are running Feisty i386, 1 is Feisty amd64. I
have this issue only on the later.
I also have an issue (on that amd64) with the NetworkManager applet. It
always says the link (eth0) is disabled, while it's not and I've noticed
during an upgr
I have reproduced this bug. It exists in Feisty even if you install it
from scratch (ie not upgrade). I'm not sure what the root cause is, but
I can tell you that if you manually edit sendmail.cf to remove line 99
("Dj;; connection timed out; no servers could be reached") and then
restart it doing
It occured a second time last week after I did an update using the
update manager. I had to manually edit dialup.m4 once again.
The bug is in sendmail-8.13.8/debian/local/dynamic.in in the find_host()
function called by update_host().
I guess $(host $SM_ip) simply fails.
This is a serious flaw as
Seems like it comes from a bad /etc/mail/m4/dialup.m4
[EMAIL PROTECTED]:/etc/mail # grep -v ^# /etc/mail/m4/dialup.m4
LOCAL_CONFIG
dnl include(`/etc/mail/dialup.m4')dnl
Cw1.2.3.4
define(`confDOMAIN_NAME', `;; connection timed out; no servers could be
reached')dnl
Cw;; connection timed out; no ser
18 matches
Mail list logo
