Package: courier-mta
Version: 1.0.16-2
Severity: grave
Justification: renders package unusable


On current debian bullseye, courier-mta is not startable, looks like
some kind of
problem in init scripts (but could be executables/environment), as per
system info
and console log below.

Even with all courier packages purged,  /etc/courier  /???/lib/courier
directories
completely removed, and start from scratch, installation of courier-base
is OK but
installing courier-mta consistently fails.



This is reproducible on a buster system upgraded to bullseye (i386 and
sysvinit-core
and no usrmerge) e.g.:-

====================================================================================
Preconfiguring packages ...
Selecting previously unselected package courier-mta.
(Reading database ... 42620 files and directories currently installed.)
Preparing to unpack .../courier-mta_1.0.14-2_i386.deb ...
Adding 'diversion of /usr/bin/addcr to /usr/bin/addcr.ucspi-tcp by
courier-mta'
Adding 'diversion of /usr/share/man/man1/addcr.1.gz to
/usr/share/man/man1/addcr.ucspi-tcp.1.gz by courier-mta'
Unpacking courier-mta (1.0.14-2) ...
Setting up courier-mta (1.0.14-2) ...
update-alternatives: using /usr/bin/lockmail.courier to provide
/usr/bin/lockmail (lockmail) in auto mode
update-alternatives: using /usr/bin/preline.courier to provide
/usr/bin/preline (preline) in auto mode
/etc/courier/esmtpd.pem.pem already exists.
dpkg: error processing package courier-mta (--configure):
 installed courier-mta package post-installation script subprocess
returned error exit status 1
Processing triggers for man-db (2.9.4-2) ...
Errors were encountered while processing:
 courier-mta
E: Sub-process /usr/bin/dpkg returned an error code (1)
====================================================================================



ALSO (though not quite the same) on a current debian amd64 bullseye
chroot (not upgraded)
systemd-based host system as well.   In that circumstance you get various
"Running in chroot, ignoring request." messages for start (which
otherwise passes even
if mta may not be started), but similar error shows up upon trying to
remove/purge
courier-mta instead, with error:-

====================================================================================
Removing courier-mta (1.0.14-2) ...
Running in chroot, ignoring request.
Stopping Courier MSA server: esmtpd-msa.
invoke-rc.d: initscript courier-msa, action "stop" failed.
dpkg: error processing package courier-mta (--remove):
 installed courier-mta package pre-removal script subprocess returned
error exit status 1
dpkg: too many errors, stopping
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Running in chroot, ignoring request.
Running in chroot, ignoring request.
Running in chroot, ignoring request.
Running in chroot, ignoring request.
Running in chroot, ignoring request.
Errors were encountered while processing:
 courier-mta
Processing was halted because there were too many errors.
====================================================================================



System info below is from trying the sid/second version (just the
courier packages) but exactly the same failure happens either way.
This clearly needs looking at for bullseye release.

**NB** Have discovered that, at least for the case of new-installing
courier-mta 1.0.16-2, adding "exit 0" on the end of
/etc/init.d/courier-msa   *seems* to be sufficient to allow dpkg
configure to work, and courier-mta then seems to start okay.

I have considered the non-systemd and non-usrmerge (mkdir path)
bugs I could find for courier-mta but these don't seem to apply
to this circumstance.


This clearly makes the package unusable on bullseye and needs looking
at for release.  Lots of courier-mta users will be "upgrade" case, I
strongly suspect, so working for upgrade cases in older configs is
especially important!

--Simon




-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-14-686-pae (SMP w/2 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages courier-mta depends on:
ii  courier-authlib        0.71.1-1
ii  courier-base           1.0.16-2
ii  debconf [debconf-2.0]  1.5.74
ii  libc6                  2.31-9
ii  libcourier-unicode4    2.1.2-2
ii  libgcc-s1              10.2.1-6
ii  libgdbm6               1.19-2
ii  libidn11               1.33-3
ii  libnet-cidr-perl       0.20-1
ii  libperl5.32            5.32.1-2
ii  libstdc++6             10.2.1-6
ii  perl                   5.32.1-2
ii  sysvinit-utils         2.96-6
ii  wget                   1.21-1

courier-mta recommends no packages.

Versions of packages courier-mta suggests:
pn  courier-doc          <none>
pn  courier-filter-perl  <none>
pn  couriergrey          <none>
pn  mail-reader          <none>

-- Configuration Files:
/etc/courier/aliases/system [Errno 13] Permission denied:
'/etc/courier/aliases/system'
/etc/courier/esmtpauthclient [Errno 13] Permission denied:
'/etc/courier/esmtpauthclient'
/etc/courier/esmtpd.cnf [Errno 13] Permission denied:
'/etc/courier/esmtpd.cnf'

-- debconf information:
  courier-mta/dsnfrom: mailer-dae...@muddle.enyc.org.uk
  courier-mta/defaultdomain: muddle.enyc.org.uk

Reply via email to