Package: mailutils-imap4d Version: 1:3.20-2 Severity: normal Tags: patch Dear Maintainer,
randomly during
$> systemctl restart mailutils-imap4d.service
IMAP4 daemon does fail to (re-)start with
$> journalctl -eu mailutils-imap4d
systemd[1]: mailutils-imap4d.service: Scheduled restart job, restart counter
is at 5.
systemd[1]: mailutils-imap4d.service: Start request repeated too quickly.
systemd[1]: mailutils-imap4d.service: Failed with result 'start-limit-hit'.
systemd[1]: Failed to start mailutils-imap4d.service - GNU IMAP4 daemon.
It seems that the daemon does too often fail to come up. I'm not sure
what the origin of the issue, but as work-around it works to set in
* /usr/lib/systemd/system/mailutils-imap4d.service
StartLimitBurst=0
I provide a patch as reply to this report.
Greets, Dirk.
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.16.9+deb14-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mailutils-imap4d depends on:
ii libc6 2.41-12
ii libcom-err2 1.47.2-3+b3
ii libcrypt1 1:4.4.38-1
ii libgnutls30t64 3.8.10-2
ii libgsasl18 2.2.2-4
ii libgssapi-krb5-2 1.21.3-5
ii libk5crypto3 1.21.3-5
ii libkrb5-3 1.21.3-5
ii libldap2 2.6.10+dfsg-1
ii libmailutils9t64 1:3.20-2
ii libpam0g 1.7.0-5
ii libunistring5 1.3-2
ii libwrap0 7.6.q-36
ii mailutils-common 1:3.20-2
ii netbase 6.5
mailutils-imap4d recommends no packages.
Versions of packages mailutils-imap4d suggests:
pn mailutils-mda <none>
0001-debian-mailutils-imap4d.service-Prevent-failed-start.patch
Description: application/mbox
