Hi,
I have a setup with several dovecot-servers (2.2.35) and I use dovecot
proxy. I upgraded one server to 2.3.1 and got the configs fixed so far
that it started again. But when I tried to add it into the proxying
again with "doveadm director add" I see the following in the logfiles:
May 6 07:19
Hi all,
New to the mailing lists but have joined up because of above */2.3.1
Replication is throwing scary errors
/*Brief system configuration
MX1 - Main
Freebsd 11.1-Release-p9
Hosted on a Vultr VM in Sydney AU
MTA = Postfix 3.4-20180401
Dovecot = 2.3.1
On 2018-05-05 (11:19 MDT), Aki Tuomi 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
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
The /file/to/put/mail/in?
Or ?
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: larry...@gmail.com
US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106
On 5/5/18, 3:21 PM, "dovecot on behalf of @lbutlr"
wrote:
On 2018-05-05 (11
On 2018-05-05 (11:19 MDT), Larry Rosenman 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
On 2018-05-05 (11:19 MDT), Aki Tuomi 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." - M
> On 05 May 2018 at 20:14 "@lbutlr" wrote:
>
>
> On 2018-05-05 (06:52 MDT), Benny Pedersen 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 sen
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: larry...@gmail.com
US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106
On 5/5/18, 12:15 PM, "
On 2018-05-05 (06:52 MDT), Benny Pedersen 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 fo
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, may
11 matches
Mail list logo
