alias | grep mail, so I take it there is no alias. Using /usr/bin/mail does not change the output.I'm out of ideasHi mer,
thank you again.
I did not know that the prompt can be changed. In any event, there is no output fromalias | grep mail, so I take it there is no alias. Using/usr/bin/maildoes not change the output.
Maybe I should just redirect the root's mail to username. The problem is that I am using mail/aerc and have it setup for reading Maildir format.
Kindest regards,
M
echo $MAIL
/var/mail/username
# cat ~root/.forward
cat: /root/.forward: No such file or directory
Agree: The human system administrator should (a) read the mail that is sent to root, and (b) should not use the root account for that, but a sensible account. For example, I don't store any mail on my FreeBSD servers (their /var/spool/mail is empty), and instead forward it off the host to my ISP, using a different account than my regular user account so ralph@example.com doesn't get mixed with the messages intended for root). Many other ways of storing mail are possible.yes, redirecting root's mail is what the general recommendation is, which I learned trying to figure out how to read the root's daily, weekly, etc., mail. So, have just set it up.
That is broken. After doing "su -", in the shell you are presented with, you should see: id = "uid=0(root) gid=0(wheel) groups=0(wheel),..." (the output of the id command), and $HOME=/root and $MAIL=/var/mail/root. I'm very surprised that "su -" did not change those two variables. Are you sure you used "su -", and not "su" by mistake? Read the man page to figure out the difference.echo $MAIL.Code:/var/mail/username
I was demonstrating the best way to forward(5) root's email...# cat ~root/.forwardCode:cat: /root/.forward: No such file or directory