unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Wojtek Kosior via <help-guix@gnu.org>
To: "Marek Paśnikowski" <marek@marekpasnikowski.pl>
Cc: thorondir+guix@thorondir.com, help-guix@gnu.org
Subject: Re: Abstractio of Dovecot Users
Date: Wed, 22 Nov 2023 19:32:57 +0100	[thread overview]
Message-ID: <20231122193257.3816b931.koszko@koszko.org> (raw)
In-Reply-To: <pu9xcq.s4jdap.rv0cvq-qmf@localhost>

[-- Attachment #1: Type: text/plain, Size: 2903 bytes --]

Cześć Marek :)

I also did set up self-hosted email under Guix (in a Guix container)
this year, with configuration here[1]. Right now I can describe it with
the same words you used – "ugly monolith".

So, you're using OpenSMTPD? Does it serve its purpose well? I used Exim
(since that was what I used before under Debian) but the Guix Exim
service misses some parts (e.g. working setuid in child Exims) so I
made a few workarounds. Does OpenSMTPD also have similar problems?

> Would you like a copy of my current system configuration for
> reference?

Sure :)

> prepare to use Linux From Scratch books to build my personal
> distribution of Guix

It can't be that bad? :) After all, it should be possible to either
include custom code in your projects via recursive git repositories or
put it into packages in your personal Guix channel or (I suppose this
is what you want) make your patches live on a git branch of Guix that
can be just `guix pull`'d.

Either way, I'd find it useful to see which of the approaches works out
the best for you. Would you be so nice to share your experiences after
a few months?

Best
Wojtek

[1] https://git.koszko.org/koszko-org-server/tree/container.scm


-- (sig_start)
website: https://koszko.org/koszko.html
fingerprint: E972 7060 E3C5 637C 8A4F  4B42 4BC5 221C 5A79 FD1A
follow me on Fediverse: https://friendica.me/profile/koszko/profile

♥ R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ== | ÷ c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ==
✝ YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ== | ? U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=
-- (sig_end)


On Wed, 22 Nov 2023 17:44:48 +0000 Marek Paśnikowski <marek@marekpasnikowski.pl> wrote:

> 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.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2023-11-22 18:33 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
2023-11-22 18:32     ` Wojtek Kosior via [this message]

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=20231122193257.3816b931.koszko@koszko.org \
    --to=help-guix@gnu.org \
    --cc=koszko@koszko.org \
    --cc=marek@marekpasnikowski.pl \
    --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).