Hi Rene,
Thank you for filing a bug.
Indeed, I can confirm that the problem exists. It's caused by the fact
that Noble's saslauthd ships a systemd unit now, and that unit is not
setting the "Group" parameter for the service.
Your workaround is OK, but if you want a better one, you can do the
following (as root):
# systemctl edit saslauthd.service
Then, put the following lines inside the file:
[Service]
Group=sasl
Save the file, and restart the service. You should now see the right
permissions/owner/group under /run/saslauthd.
I'm going to mark this bug as Triaged.
Thanks.
** Also affects: postfix (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: postfix (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: postfix (Ubuntu Noble)
Status: New => Triaged
** Changed in: postfix (Ubuntu Oracular)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078851
Title:
saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/2078851/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
