From: Anachron <Anachron@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Dovecot package is broken in various ways
Date: Tue, 09 Aug 2022 21:58:12 +0200 [thread overview]
Message-ID: <20220809195812.zCnrKL0za-xr9xI_hyGxsLlCV_XDbOqx4RsbdqeEn24@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38551@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
New comment by Anachron on void-packages repository
https://github.com/void-linux/void-packages/issues/38551#issuecomment-1209814639
Comment:
Ah I installed `dovecot` before https://github.com/void-linux/void-packages/commit/b49fd851309d6593fbb6fb8ae191f796a98ee96a probably, so that's why I have
```
grep 'dovecot' /etc/passwd
dovecot:x:994:993:dovecot unprivileged user:/var/chroot:/sbin/nologin
_dovecot:x:991:990:_dovecot unprivileged user:/var/empty:/sbin/nologin
```
Can you redact your config and paste it here?
Because for example this is inside `/usr/share/examples/dovecot/conf.d/10-master.conf`:
```
# Login user is internally used by login processes. This is the most untrusted
# user in Dovecot system. It shouldn't have access to anything at all.
#default_login_user = dovenull
# Internal user is used by unprivileged processes. It should be separate from
# login user, so that login processes can't disturb other processes.
#default_internal_user = dovecot
```
next prev parent reply other threads:[~2022-08-09 19:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 9:09 [ISSUE] " TwinkleToes777
2022-08-09 11:21 ` Anachron
2022-08-09 19:04 ` TwinkleToes777
2022-08-09 19:05 ` TwinkleToes777
2022-08-09 19:25 ` Anachron
2022-08-09 19:47 ` TwinkleToes777
2022-08-09 19:58 ` Anachron [this message]
2022-08-09 20:28 ` TwinkleToes777
2022-08-09 20:28 ` [ISSUE] [CLOSED] " TwinkleToes777
2022-08-09 20:31 ` Anachron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220809195812.zCnrKL0za-xr9xI_hyGxsLlCV_XDbOqx4RsbdqeEn24@z \
--to=anachron@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).