Dear Maintainer,
* What led up to the situation?
After upgrade to trixie, saslauhd systemd service forces pid path to be /run in
place of /var/run.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Adding this as symbolic link allows saslauthd to continue working when path
changed to run instead of var/run inside chroot.
* What was the outcome of this action?
Without this symlink, we cannot use run/saslsuthd and authentication is broken.
* What outcome did you expect instead?
With -m option set to run/saslauthd inside chroot, saslauthd should continue to
work.
More details in #1110309