unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Marek Paśnikowski" <marek@marekpasnikowski.pl>
To: thorondir+guix@thorondir.com,help-guix@gnu.org
Subject: Re: Abstractio of Dovecot Users
Date: Wed, 22 Nov 2023 17:44:48 +0000	[thread overview]
Message-ID: <pu9xcq.s4jdap.rv0cvq-qmf@localhost> (raw)
In-Reply-To: <d9c84539-0357-4922-90f9-25cc5be352f3@thorondir.com>



Email z Środa, 22 listopada 2023 od Thorondir:
> Hi Marek,
> 
> On 11/20/23 23:40, Marek Paśnikowski wrote:
> > I would like to ask you, which dovecot service configuration parameters should I look at, for declaration of what I have seen on the net named “vmail”.
> >
> > My immediate goal is to declare a dedicated inbox for DMARC reports and a bunch of aliases for 'marek' mail account, stored separately from the system's 'marek' account.
> 
> Way back when I first started on the journey of email self-hosting, I 
> found the ArchWiki[0] to have enough information to get me started. 
> After doing that, do try to understand why it does what it does, because 
> there is quite a bit of complexity in there.
> 
> But in short:
> 
>   * you create a local user [yes, usually "vmail"] who gets everything
>     and stores it according to who it's supposed to be for
>   * the question of "who is it for" is usually answered by entries in a
>     database or map file
>   * both postfix and dovecot need to know about and use the database or
>     map file

The reminder to reconfigure OpenSMTPD is helpful, thank you.

  reply	other threads:[~2023-11-22 18:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 22:40 Abstractio of Dovecot Users Marek Paśnikowski
2023-11-22 16:43 ` Felix Lechner via
2023-11-22 17:28   ` Marek Paśnikowski
2023-12-19 18:43   ` Marek Paśnikowski
2023-12-20  9:15   ` Marek Paśnikowski
2023-11-22 17:25 ` Thorondir via
2023-11-22 17:44   ` Marek Paśnikowski [this message]
2023-11-22 18:32     ` Wojtek Kosior via

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pu9xcq.s4jdap.rv0cvq-qmf@localhost \
    --to=marek@marekpasnikowski.pl \
    --cc=help-guix@gnu.org \
    --cc=thorondir+guix@thorondir.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).