saslauthd wrong permission of /var/spool/postfix/var/run/saslauthd

Bug #2078851 reported by Rene Schickbauer
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
postfix (Ubuntu)
Status tracked in Oracular
Noble
Triaged
Undecided
Unassigned
Oracular
Triaged
Undecided
Unassigned

Bug Description

Folder group permission of /var/spool/postfix/var/run/saslauthd gets reset to "root" (should be "sasl") every time saslauthd gets restarted.

This worked fine before upgrading from 22.04 to 24.04

My automated workaround currently is this crontab (root) entry:

*/1 * * * * /usr/bin/chgrp sasl /var/spool/postfix/var/run/saslauthd 2>&1

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: postfix 3.8.6-1build2
ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
Uname: Linux 6.8.0-41-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Sep 3 19:52:59 2024
SourcePackage: postfix
UpgradeStatus: Upgraded to noble on 2024-08-31 (3 days ago)
mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07

Revision history for this message
Rene Schickbauer (rene-schickbauer) wrote :
Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

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.

Changed in postfix (Ubuntu Noble):
status: New → Triaged
Changed in postfix (Ubuntu Oracular):
status: New → Triaged
Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.