Devuan bug report logs - #630
exim 4.94.5 installation configures IPv6 by default on IPv4 only machines

version graph

Package: exim4; Maintainer for exim4 is (unknown); Source for exim4 is src:exim4.

Reported by: sawbona@xsmail.com

Date: Sat, 13 Nov 2021 20:42:02 UTC

Severity: grave

Tags: debian

Found in version 4.92-5

Forwarded to https://bugs.debian.org/610918

Full log


🔗 View this message in rfc822 format

X-Loop: owner@bugs.devuan.org
Subject: bug#630: exim 4.94.5 installation configures IPv6 by default on IPv4 only machines
Reply-To: sawbona@xsmail.com, 630@bugs.devuan.org
Resent-From: sawbona@xsmail.com
Resent-To: devuan-bugs@lists.dyne.org
Resent-CC: devuan-dev@lists.dyne.org
X-Loop: owner@bugs.devuan.org
Resent-Date: Sat, 13 Nov 2021 20:42:02 +0000
Resent-Message-ID: <handler.630.B.163683600327298@bugs.devuan.org>
Resent-Sender: owner@bugs.devuan.org
X-Devuan-PR-Message: report 630
X-Devuan-PR-Package: exim4
X-Devuan-PR-Keywords: 
Received: via spool by submit@bugs.devuan.org id=B.163683600327298
          (code B); Sat, 13 Nov 2021 20:42:02 +0000
Received: (at submit) by bugs.devuan.org; 13 Nov 2021 20:40:03 +0000
Delivered-To: devuanbugs@dyne.org
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Sat, 13 Nov 2021 20:40:02 +0000 (UTC)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id 91833F60CC2
	for <submit@bugs.devuan.org>; Sat, 13 Nov 2021 21:30:38 +0100 (CET)
Authentication-Results: vm6.ganeti.dyne.org;
	dkim=pass (2048-bit key; unprotected) header.d=xsmail.com header.i=@xsmail.com header.b="PrkaS8Cq";
	dkim=pass (2048-bit key; unprotected) header.d=messagingengine.com header.i=@messagingengine.com header.b="fSCrnRrd";
	dkim-atps=neutral
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44])
	by mailout.west.internal (Postfix) with ESMTP id 8D37E3200E18
	for <submit@bugs.devuan.org>; Sat, 13 Nov 2021 15:30:36 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163])
  by compute4.internal (MEProxy); Sat, 13 Nov 2021 15:30:36 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xsmail.com; h=
	from:to:date:mime-version:subject:message-id:content-type
	:content-transfer-encoding:content-description; s=fm1; bh=v2tHai
	+YJx4GOkOx2OoQ1+BvQKff1giQMJfyKc0y7EE=; b=PrkaS8Cq/TcPhqD4lsEmtb
	ecoHQGTMRJAlutazO+Ht6DkQYGpz23jxlOfLXBGilLez+aEq1aP1AGlqaygVKE9r
	p58NDVLrks/snboaXGRGGpsoV9tOLbEl5HmmNBJ9NGS5KeCGYqSV7jLBrWTi5VuJ
	LSuSs8JKyZGMw0Qoi0twv+7oOnpIkGP6es8wBpWabvT8Yo8iVNBO6emd0aYyxQ2u
	ApGb1oljbzrrOmMR1YLtTLBIoOeIA5ypm7PT7tr2CZvxHhuMl+GRgx2hXD93sWHq
	qCBNV4yrRR3YzdKjEBar8XlQcmsJKuEEGjRWtQZqj3IB1xH4rCcsDiGi/1nLEg2w
	==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=content-description
	:content-transfer-encoding:content-type:date:from:message-id
	:mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender
	:x-me-sender:x-sasl-enc; s=fm1; bh=v2tHai+YJx4GOkOx2OoQ1+BvQKff1
	giQMJfyKc0y7EE=; b=fSCrnRrdWi2EtGPxQXehs12Keioxbyxz5HRokLgjzcsZh
	vcYE66sxRYs+jJGdqqtihxQK38ER/rWk6JAyrKJ5K8jbTkEsa1Wp9RKpc7gozlpN
	bCzbWBPBrqnJ0ouQg9bZtxYWTjm1w22j3Rl8dDxFiEIcIJNsuLwMzRSZXcDtQ/oo
	FCm6/d5eRRPQ+8gm6zde1wjm7fqzQvsJ57UhAEevnsjDDeTxhYfH+BQUKdQu1Y1O
	+9M+fhqCrBAnq+b73FSstIyA4iWhXAAtxxrkqtZkyUdMCzBgzppdZT1inkF3PUqn
	FzB+45bKcPTvnti4SDwoINiJPiUWwy3TUSqn5QTdQ==
X-ME-Sender: <xms:bCCQYd8Nj176SjWW1pZ4qSgNVVpeLww5coMr33O45_MzYvIWzvCcrQ>
    <xme:bCCQYRte6TxZeMegavWVSRQXAgyQn70pwQP4Qrj22ryaJ5IDslaLCbmMZop9WtB9V
    y7f3JEkuwGg_VvhsA>
X-ME-Received: <xmr:bCCQYbCrLbz5CqQGdH6-jVdGOG0qHNIiPCHoisUxMXTSUbBOPj89GddHBhxWT30o>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrvdehgddufeekucetufdoteggodetrfdotf
    fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
    uceurghilhhouhhtmecufedttdenucenucfjughrpefhvfffggfukffotgfgsehtufertd
    fftddvnecuhfhrohhmpehsrgifsghonhgrseigshhmrghilhdrtghomhenucggtffrrght
    thgvrhhnpeffgeejhefgkedtvdeggfdvuddvteelgeelgeejheefgfelveetieefvdetke
    egkeenucffohhmrghinhepuggvsghirghnrdhorhhgpdgvgihimhdrohhrghenucevlhhu
    shhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehsrgifsghonhgrse
    igshhmrghilhdrtghomh
X-ME-Proxy: <xmx:bCCQYRem1VJYT85f2eNaaYhL2OzDn_lDNqVJTpvZpk70fxFlbRnlVQ>
    <xmx:bCCQYSMmqIP8Vlodvtx8eFtjGGhvb9oCXxWvCAOjsj5XC_chjgwmxw>
    <xmx:bCCQYTlLBiS8e5oqwtHLA9Dyd1T0KRSHn1S51rMrIcksrfqSSGldBg>
    <xmx:bCCQYVYZM5oNmFzIJ093WNWD0F71695Dpdvm-1tY9McThCqM6UmFjw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for
 <submit@bugs.devuan.org>; Sat, 13 Nov 2021 15:30:35 -0500 (EST)
From: sawbona@xsmail.com
To: submit@bugs.devuan.org
Date: Sat, 13 Nov 2021 17:31:42 -0300
MIME-Version: 1.0
Message-ID: <619020AE.19336.680229@sawbona.xsmail.com>
Priority: normal
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,
	RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_PASS autolearn=disabled
	version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org
Package: exim4
Version: 4.92-5
Severity: grave

I've previously reported this bug to Debian:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999612

Unfortunately, a *single* reference to Devuan slipped by my editing.
As a result, the bug report was instantly/swiftly closed by the chap 
in charge with the reply being:

"Well, you are running an unsupported setup."

I really don't have time to set up a Debian installation to prove it 
is *also* a bug for Debian and probably every Debian based 
distribution. 

I had also previously exchanged opinions with respect to this problem 
on the exim-users list but without any success.

https://lists.exim.org/lurker/thread/20211113.163548.7007ca8c.en.html

So ...
Exim will not fix it because they actually don't think it is a bug.

Debian won't fix it because the person reporting the bug is running 
Exim under an unsupported configuration.

The truth of the matter is this:

Exim, as it comes straight from the official Debian repository, will 
install itself to use IPv6 *by default* in a system where the 
settings *explicitly* disable the IPv6 protocol.  

ie:

1.
The kernel command line includes the bit needed to disable ipv6 at
boot:

[code]
ipv6.disable=1
[/code]

2.
The /etc/hosts file has no machine readable IPv6 lines:

[code]
groucho@devuan:~$ cat /etc/hosts
#
127.0.0.1         localhost  devuan
#
# remmed to disable ip6
#::1                 localhost       ip6-localhost ip6-loopback
#fe00::0          ip6-localnet
#fe00::0          ip6-mcastprefix
#fe02::1          ip6-allnodes
#fe02::1          ip6-allrouters
groucho@devuan:~$
[/code]

3.
The /etc/ssh/ssh_config file includes the line needed to disable
ipv6:

[code]
groucho@devuan:~$ cat /etc/ssh/ssh_config
--- snip ---
AddressFamily inet     # instead of 'any' or 'inet6'
--- snip ---
groucho@devuan:~$
[/code]

In doing so, when Exim starts it generates a paniclog message:

[code]
IPv6 socket creation failed: Address family not supported by protocol
[/code]

Also, in a machine such as mine, running a VBox VM with a DNS (both 
configured explicitly disabling IPv6) it will also generate a 30s 
delay at boot while Exim makes an AAAA query to the DNS which (quite 
obviously) it won't answer.  

If this is not a bug ...

I'd appreciate any comments you'd care to make.

Thanks in advance.

Best,

A.

Send a report that this bug log contains spam.


Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.

Devuan Bugs Owner <owner@bugs.devuan.org>.
Last modified: Sun Nov 24 01:57:06 2024;