Devuan bug report logs -
#586
exim 4.94.2 update default configuration option breaks MTA
Reply or subscribe to this bug.
Toggle useless messages
Report forwarded
to devuan-bugs@lists.dyne.org, devuan-dev@lists.dyne.org
:
bug#586
; Package exim4
.
(Fri, 25 Jun 2021 16:03:01 GMT) (full text, mbox, link).
Acknowledgement sent
to sawbona@xsmail.com
:
New bug report received and forwarded. Copy sent to devuan-dev@lists.dyne.org
.
Your message specified a Severity: in the pseudo-header, but
the severity value high was not recognised.
The default severity normal is being used instead.
The recognised values are: critical, grave, normal, minor, wishlist.
(Fri, 25 Jun 2021 16:03:05 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):
Package: exim4
Version: 4.94
Severity: high
Half way through the update to exim 4.94.2, the installer pops up a
warning in the terminal informing that the configuration file being
installed was different to the one in place and prompts to choose
what to do:
1. keep the installed configuration (default)
2. install the new configuration
3. check and compare the differences in order to choose.
In most default Devuan Beowulf installations the installer will be
referring to the [c]/etc/exim4/exim4.conf.template[/c] which is used
by the default non-split configuration scheme used by most anyone
running a Devuan Beowulf desktop box.
Most users will choose the (recommended) default option.
In doing so they will unknowingly break their exim4 installation.
The result is a non-working MTA, with system mail being held.
ie: not delivered to /var/mail/user folder while at the same time
/var/log/exim4/paniclog slowly grows in size.
With all versions of exim previous to version 4.94.2 now rendered
obsolete, exim 4.94.2 will break any and all configurations set up
with previous versions of the package.
This happens whether it uses the default configuration ie: the
non-split configuration scheme which uses the
/etc/exim4/exim4.conf.template file or the split configuration scheme
used in more complex installations and which you can eventually opt
for when installing Devuan or by running dpkg-reconfigure
exim4-config later on.
exim 4.94.2 is absolutely incompatible with any configuration files
used/generated with versions previous to version 4.94.2.
Which, at least for *this* very significant update, makes the
(default) option to keep an existing configuration a serious problem.
Doing so will keep back the exim-config 4.94.2 package and make a
mess.
Please don't ask how I know this.
Thanks in advance,
Carlos Izzo Videla
Information forwarded
to devuan-bugs@lists.dyne.org, devuan-dev@lists.dyne.org
:
bug#586
; Package exim4
.
(Sat, 03 Jul 2021 14:03:02 GMT) (full text, mbox, link).
Message #8 received at 586@bugs.devuan.org (full text, mbox, reply):
Control: tags -1 debian
Carlos,
Thanks for this.
On Fri, Jun 25, 2021 at 12:45:28PM -0300, sawbona@xsmail.com wrote:
> Package: exim4
> Version: 4.94
> Severity: high
However, all of Devuan's exim4 packages are used directly from Debian with out
recompilation. Please could you report this to Debian's BTS?
Thanks
Mark
Added tag(s) debian.
Request was from Mark Hindley <mark@hindley.org.uk>
to 586-submit@bugs.devuan.org
.
(Sat, 03 Jul 2021 14:03:04 GMT) (full text, mbox, link).
Information forwarded
to devuan-bugs@lists.dyne.org, devuan-dev@lists.dyne.org
:
bug#586
; Package exim4
.
(Sat, 03 Jul 2021 16:03:01 GMT) (full text, mbox, link).
Acknowledgement sent
to Mark Hindley <mark@hindley.org.uk>
:
Extra info received and forwarded to list. Copy sent to devuan-dev@lists.dyne.org
.
(Sat, 03 Jul 2021 16:03:03 GMT) (full text, mbox, link).
Message #15 received at 586@bugs.devuan.org (full text, mbox, reply):
Control: forwarded -1 https://bugs.debian.org/990344
Carlos,
On Sat, Jul 03, 2021 at 11:23:22AM -0300, sawbona@xsmail.com wrote:
> > ... Devuan's exim4 packages are used directly from Debian ...
> Yes, Dev1 admin golinux later informed me of that, so I submitted a
> bug report.
>
> You can see how *that* went here:
>
> [url]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990344[/url]
Thanks. Sorry you didn't get a better result.
Mark
Information forwarded
to devuan-bugs@lists.dyne.org, devuan-dev@lists.dyne.org
:
bug#586
; Package exim4
.
(Sun, 04 Jul 2021 11:33:01 GMT) (full text, mbox, link).
Acknowledgement sent
to Hendrik Boom <hendrik@topoi.pooq.com>
:
Extra info received and forwarded to list. Copy sent to devuan-dev@lists.dyne.org
.
(Sun, 04 Jul 2021 11:33:04 GMT) (full text, mbox, link).
Message #22 received at 586@bugs.devuan.org (full text, mbox, reply):
On Sat, Jul 03, 2021 at 04:50:54PM +0100, Mark Hindley wrote:
> Control: forwarded -1 https://bugs.debian.org/990344
>
> Carlos,
>
> On Sat, Jul 03, 2021 at 11:23:22AM -0300, sawbona@xsmail.com wrote:
> > > ... Devuan's exim4 packages are used directly from Debian ...
> > Yes, Dev1 admin golinux later informed me of that, so I submitted a
> > bug report.
> >
> > You can see how *that* went here:
> >
> > [url]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990344[/url]
>
> Thanks. Sorry you didn't get a better result.
Is the exim upgrade capable of translating the old configuration files to
correspnding new configuration files?
If not, I'd have to study the matter before allowing *any* such upgrade.
I guess to the extent of pinning exim.
-- hendrik
>
> Mark
> _______________________________________________
> devuan-dev internal mailing list
> devuan-dev@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/devuan-dev
Send a report that this bug log contains spam.