2023-03-28T15:15:29-0300 tars crond: procmail: Couldn't create "/var/spool/mail/marcelo"
2023-03-28T15:15:29-0300 tars crond: MDA returned nonzero status 73
2023-03-28T15:15:33-0300 tars crond: procmail: Couldn't create "/var/spool/mail/marcelo"
2023-03-28T15:15:33-0300 tars crond: MDA returned nonzero status 73
I enabled some backup scripts via crontab -e, and it looks like it started when I did it. Now I commented everything, but it keeps going. Removed my user’s crontab file; restored it; created and empty one…
Cron was firing with no problems, just one command I misstype and decide to check the logs and found those messages.
journalctl | grep AVC found nothing. As is an upgrade from F37 I ran the Post-upgrade option commands, one of them is related to SELinux.
Permissions on this directory only allow write access for root.
The mailbox should have been created automatically along with the user’s home directory.
Since it no longer exists, you can restore it manually like this:
Mucking about with system installed files is seldom fruitful and often breaks things.
SELinux may be interfering now and that can be fixed with sudo restorecon -R /var/spool. By temporarily disabling selinux with sudo setenforce 0 while testing you may find out if it is caused by selinux.
The permissions should be (by default)
# ls -lZ /var/spool/mail
-rw-rw----. 1 $USER mail system_u:object_r:mail_spool_t:s0 0 Mar 10 20:09 $USER
Previous post was the content of the directory. My last request was for the actual directory listing.
Just to add a bit of explanation to the post by Vladislav above.
When SELinux is disabled it does not do anything. Files created are not given an selinux content, nothing is checked to allow or restrict access, etc. Those files you posted with no context are possibly a very small percentage of the total files in the system that might not have an selinux context assigned.
The commands given will put selinux into enforcing mode and then relabel all the system files with the proper context during the reboot.
Also, when you ran restorecon with selinux disabled it had nothing to do (it was disabled) so could not tell you what it did.
Thanks for everything. I decided to do a fresh install.
Something was wrong. The selinux=1 line inside /etc/default/grub is not present on a fresh F38, it was inherited from previous installation and not corrected during the upgrade(s). As I had also various problems before and after upgrading with constant packages conflicts, restoring my snapshots or a fresh install were better options than digging it further.