Fix permissions of /Library/Mail if the folder does not yet exist to avoid problems with custom umasks
Reported by Support | January 25th, 2022 @ 06:11 PM | in 2022.1 (closed)
Assigned to
Stable #115468. The default umask of macOS is 0022 which in
turn also creates folder with read permissions for users of the
same group and all "other".
The default umask can however be modified and set to a more
restrictive version, e.g.: 0077
In that case users of the same group and "other" would not have any
access what so ever to the folder.
To properly work with custom umasks the installer must set explicit permissions for any folders it creates that don't exist yet.
How to configure a custom umask for testing is described
here:
https://support.apple.com/en-us/HT201684)
sudo launchctl config user umask 077 Reboot and verify: shell
# umask 077
The user reporting this issue had a custom umask set which lead to the problem that the /Library/Mail folder couldn't be read by the Upgrader or Mail and thus the plugin can't be copied to the container path or be enabled manually in Mail.
Comments and changes to this ticket
-
-
Luke Le February 9th, 2022 @ 11:39 PM
- State changed from “new” to “fixed”
- Tag cleared.
- Assigned user set to “Luke Le”
- Milestone changed from “2021.2” to “2022.1”
- Importance changed from “” to “Low”
-
steve February 10th, 2022 @ 04:36 PM
- State changed from “fixed” to “verified”
macOS 12.3 Beta (21E5206e)
GPG SUite 3112n
verified -
steve March 30th, 2022 @ 02:02 AM
- State changed from “verified” to “released”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Luke Le
steve
Support