5 May
2018
5 May
'18
3:52 p.m.
And yet it is.
in muttrc you miss ~ or $(HOME)/something
root: some-other-unix-login
Root has been aliased for decades. This has no impact on where and how mutt stores the mail it sends as root out of root’s crontab.
root user can read mail files for all unix users, thats your fail, maybe crontab miss $(HOME) where it matters, but if it have and you start mutt as root it does not help, and you see the problem in allow root to do too much
i dont know mutt in detail, but its a fail to start mutt as root
mutt must be started as some-other-unix-login
the remaining fail is then in that users muttrc