You are not logged in.
I noticed that local Unix mail stopped being delivered. 'mail' (s-nail) command succeeds but opensmtpd-7.8.0p rejects to lock /var/mail directory (which is symlink to /var/spool/mail):
Apr 17 17:34:35 dimich lockspool[3595]: /var/mail: will not deliver to world-writable spool
Apr 17 17:34:35 dimich mail.local[3594]: lockspool: unable to get lockFound this discussion upstream: https://github.com/OpenSMTPD/OpenSMTPD/issues/1296
"chmod o-w /var/mail" fixes the issue, but obviously, until next filesystem package update.
Is this filesystem package issue or opensmtpd requirement for non-world-writability is incorrect?
Offline
"sketchy"?
What about ACLs?
What if smtpd doesn't run as root?
Why not test the ownership of the relevant files in /var/spool/mail ?
but obviously, until next filesystem package update.
https://wiki.archlinux.org/title/System … rary_files
https://gitlab.archlinux.org/archlinux/ … work_items - but if there's conflicting demands this might be better handled w/ a tmpfile snippet in the opensmtp package.
Offline
"sketchy"?
Sorry, didn't get what does it mean in this context.
What about ACLs?
What if smtpd doesn't run as root?
Why not test the ownership of the relevant files in /var/spool/mail ?
These questions are more to authors of opensmtpd. However, there is the package in official repository which requires manual workaround to work properly.
but if there's conflicting demands this might be better handled w/ a tmpfile snippet in the opensmtp package.
Shouldn't filesystem package drop /var/mail in this case? Because with tmpfile snippet pacman is not happy:
warning: directory permissions differ on /var/spool/mail/
filesystem: 1775 package: 1777There are multiple ways to workaround this issue permanently, but I think it's better is to fix the root cause rather than implement workaround. So trying to figure out which package submit the issue to. Or submit to both and let them figure it out themselves? ![]()
Offline
Sorry, didn't get what does it mean in this context.
or opensmtpd requirement for non-world-writability is incorrect?
I don't think there's a "correct" answer but don't quite follow their reasoning (hence the questions put up)
Because with tmpfile snippet pacman is not happy:
You're creating a conflicting situation, as long as all you get out of that is a warning/reminder, that's probably even desirable.
Or submit to both and let them figure it out themselves?
Submit to opensmtp (the immediate offender) and have them decide whether they want to punt to the filesystem package and then watch them fight to the death!!! ![]()
This might trigger upstream to review their position - another solution would be for opensmtp to create and use 755 /var/spool/mail/opensmtp
Offline
Thanks, seth.
https://gitlab.archlinux.org/archlinux/ … rk_items/7
Offline