Bug#823132: courier-imap and courier-imap-ssl doesn't start at boot

Found the bug. I added .service files, but forgot to use dh_systemd dh addon, so the services were not enabled at the install time. This will be fixed in next upload. Cheers, -- Ondřej Surý Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server Vše pro chleba (https://vseprochleba.

Bug#823132: courier-imap and courier-imap-ssl doesn't start at boot

Hello Ondřej, I filed the bug on the machine where it appeared. The outputs were: $ systemctl status courier-imap-ssl ● courier-imap-ssl.service - Courier IMAP Daemon (SSL) Loaded: loaded (/lib/systemd/system/courier-imap-ssl.service; disabled; vendor preset: enabled) Active: inactive (de

Bug#823132: courier-imap and courier-imap-ssl doesn't start at boot

Hi Robert, your init seems to be systemd (unless you filled a bug at different machine), and courier packages now have service files for all courier daemons. Could you check what: systemctl status courier-imap and systemctl status courier-imap-ssl says? (Also journalctl --unit=courier-imap a

Bug#823132: courier-imap and courier-imap-ssl doesn't start at boot

Package: courier-imap Version: 4.16.2+0.75.0-20 Severity: important Dear Maintainer, after the update of the courier-imap and courier-imap-ssl packages (and related) from 1.141 to 1.142, the server doesn't start anymore during boot. When starting courier-autdaemon and courier-imap(-ssl) manually