On 2018-05-05 (06:52 MDT), Benny Pedersen <me at junc.eu> wrote:> >> And yet it is. > > in muttrc you miss ~ or $(HOME)/somethingNo.>> 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 muchThere seems to be a basic misunderstanding here. root has a crontab. Part of that crontab parses some system log files (that only root has access to) for user data and generates an email in HTML. That email is sent via mutt because the basic mail commands could not send an HTML email properly. Mutt stores that email in ~root, and the email comes from the root user because that is who wins the crontab. The $HOME fro the user is /root/> i dont know mutt in detail, but its a fail to start mutt as rootSince the mail is generated out of root's cron, however the mail is sent, that process is going to be started by root.> mutt must be started as some-other-unix-loginSee above.> the remaining fail is then in that users muttrcThere is nothing wrong in the root muttrc. -- U is for UNA who slipped down a drain V is for VICTOR squashed by a train
> On 05 May 2018 at 20:14 "@lbutlr" <kremels at kreme.com> wrote: > > > On 2018-05-05 (06:52 MDT), Benny Pedersen <me at junc.eu> wrote: > > > >> And yet it is. > > > > in muttrc you miss ~ or $(HOME)/something > > No. > > >> 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 > > There seems to be a basic misunderstanding here. > > root has a crontab. Part of that crontab parses some system log files (that only root has access to) for user data and generates an email in HTML. That email is sent via mutt because the basic mail commands could not send an HTML email properly. > > Mutt stores that email in ~root, and the email comes from the root user because that is who wins the crontab. > > The $HOME fro the user is /root/ > > > i dont know mutt in detail, but its a fail to start mutt as root > > Since the mail is generated out of root's cron, however the mail is sent, that process is going to be started by root.You could use tool like sudo or su to run mutt as non-root, instead of running it as root? Aki
What happens if you put the following in /root/.muttrc:
Set record='/file/to/put/mail/in'
?
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: larryrtx at gmail.com
US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106
?On 5/5/18, 12:15 PM, "dovecot on behalf of @lbutlr"
<dovecot-bounces at dovecot.org on behalf of kremels at kreme.com> wrote:
On 2018-05-05 (06:52 MDT), Benny Pedersen <me at junc.eu> wrote:
>
>> And yet it is.
>
> in muttrc you miss ~ or $(HOME)/something
No.
>> 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
There seems to be a basic misunderstanding here.
root has a crontab. Part of that crontab parses some system log files (that
only root has access to) for user data and generates an email in HTML. That
email is sent via mutt because the basic mail commands could not send an HTML
email properly.
Mutt stores that email in ~root, and the email comes from the root user
because that is who wins the crontab.
The $HOME fro the user is /root/
> i dont know mutt in detail, but its a fail to start mutt as root
Since the mail is generated out of root's cron, however the mail is
sent, that process is going to be started by root.
> mutt must be started as some-other-unix-login
See above.
> the remaining fail is then in that users muttrc
There is nothing wrong in the root muttrc.
--
U is for UNA who slipped down a drain
V is for VICTOR squashed by a train
On 2018-05-05 (11:19 MDT), Aki Tuomi <aki.tuomi at dovecot.fi> wrote:> > You could use tool like sudo or su to run mutt as non-root, instead of running it as root?Maybe. Not sure if piping output in front to su will work, but I can certainly try it. -- "Making music should not be left to the professionals." - Michelle Shocked
On 2018-05-05 (11:19 MDT), Larry Rosenman <larryrtx at gmail.com> wrote:> > What happens if you put the following in /root/.muttrc: > Set record='/file/to/put/mail/in'I get a mail still owned by root. -- May you live in interesting times
Larry Rosenman skrev den 2018-05-05 19:19:> What happens if you put the following in /root/.muttrc: > Set record='/file/to/put/mail/in' > ?indeed possible, but this file will only be possible to read from root user if it can be readed by other, its a security problem
On 2018-05-05 (11:19 MDT), Aki Tuomi <aki.tuomi at dovecot.fi> wrote:> > You could use tool like sudo or su to run mutt as non-root, instead of running it as root?Thanks, that did work. Took a little, but no more sent mail in ~root. -- Vi Veri Veniversum Vivus Vici