Package: sasl2-bin Version: 2.1.28+dfsg1-9 Severity: normal 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 *** -- System Information: Debian Release: 13.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.12.38+deb13-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=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 sasl2-bin depends on: ii db-util 5.3.4 ii debconf [debconf-2.0] 1.5.91 ii init-system-helpers 1.68 ii libc6 2.41-11 ii libcrypt1 1:4.4.38-1 ii libdb5.3t64 5.3.28+dfsg2-9 ii libkrb5-3 1.21.3-5 ii libldap2 2.6.10+dfsg-1 ii libpam0g 1.7.0-5 ii libsasl2-2 2.1.28+dfsg1-9 ii libssl3t64 3.5.1-1 sasl2-bin recommends no packages. sasl2-bin suggests no packages. -- Configuration Files: /etc/default/saslauthd changed: DESC="SASL Authentication Daemon" NAME="saslauthd" MECHANISMS="pam" MECH_OPTIONS="" THREADS=5 OPTIONS="-c -m /run/saslauthd" -- debconf information excluded
