Bug#1096206: sasl2-bin : saslauthd.service should take PIDFile path from /etc/default/saslauthd

[Pirate Praveen]

Control: severity -1 important

On Mon, 17 Feb 2025 16:51:23 +0100 Guillaume Hilt <deb...@shadowprojects.org> wrote:

Package: sasl2-bin
Version: 2.1.28+dfsg1-8+b1

* saslauthd.service has a fixed path in its file :
PIDFile=/var/run/saslauthd/saslauthd.pid


OPTIONS="-c -m /var/spool/postfix/run/saslauthd -r"

* With different paths for the file, saslauthd won't be able to start :

* But, in /etc/default/saslauthd, if you have postfix running chroot, the pid path will differ : saslauthd.service: Can't open PID file /run/saslauthd/saslauthd.pid (yet?) after start: No such file or directory saslauthd.service should take PIDFile from /etc/default/saslauthd and /etc/default/saslauthd should clearly explain what need to be done if you set a different path for the pid file. Reported from https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/2098601 per request.

Without this change, it breaks upgrade to trixie - saslauthd service no longer start after the upgrade to trixie. I noticed it when I upgraded one server to trixie and while searching for the error I found other people have noticed it too.

https://forum.virtualmin.com/t/saslauthd-fails-to-start-on-debian-13-trixie-causing-smtp-authentication-failure-wrong-pid-path-in-service-file/134678/11

I have worked around this by shipping an override file

# cat /etc/systemd/system/saslauthd.service.d/override.conf
[Service]
PIDFile=/var/spool/postfix/var/run/saslauthd/saslauthd.pid

Since this is breaking upgrade to trixie, I think it should be considered a grave bug and an update should be provided in trixie to fix this. Other people also suggest this is a packaging bug and I agree with that assessment. I bumped severity to important (still not RC), but wanted to discuss before making it an RC bug.

OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key

OpenPGP_signature.asc
Description: OpenPGP digital signature