Dear Maintainer,
*** Reporter, please consider answering these questions, where
appropriate ***
* What led up to the situation?
Upgrading from bookworm to trixie.
* What exactly did you do (or not do) that was effective (or
ineffective)?
In bookworm, I had two configuration files : /etc/default/saslauthd and
/etc/default/saslauthd-postfix. The second file used a Unix socket in
the postfix chroot, as recommended in
https://wiki.debian.org/PostfixAndSASL
This worked in bookworm, where saslauthd was launch using the script
/etc/init.d/saslauthd,
which takes care to list all configuration files starting with the
prefix saslauthd
within directory /etc/default.
I kept this configuration when upgrading to trixie.
* What was the outcome of this action?
The second configuration (saslauthd-postfix) is not started anymore.
If I run "systemctl status saslauthd", I see 5 saslauthd processes that
correspond to the configuration in /etc/default/saslauthd. The 5 other
processes
I used to see and that did correspond to the /etc/default/saslauthd-
postfix
instance are not started anymore.
* What outcome did you expect instead?
I expected 10 processes to be run, 5 with one general configuration,
and
5 with a configuration running in postfix chroot.
The /etc/init.d/saslauthd seems to still be shiped in the package (it
just
seem to not use a "START=yes" test anymore as it did in bookworm). It
seems
however that it is not used at all, and that only the
/usr/lib/systemd/system/saslauthd.service
file is used, and this file references only a single configuration file
/etc/default/saslauthd,
hence ignoring the second configuration file.
*** End of the template - remove these template lines ***