From: g1 <myglc2@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: working dovecot-service config anyone?
Date: Fri, 19 Aug 2016 12:52:28 -0400 [thread overview]
Message-ID: <86twegvgz7.fsf@gmail.com> (raw)
I am using 7.2.7.7 Mail Services and finding the dovecot-service config
to be a bit, mmh, opaque. w/Google, I found a trivial example ...
https://wingolog.org/pub/alt-os-config.scm
... and got this to work ...
#:config (dovecot-configuration
(listen '("127.0.0.1"))
(mail-location "maildir:~/.maildir")
(postmaster-address "g1@localhost")
))
... but I am having trouble making the leap between the guix
documentation and dovecot syntax. Does anyone have a non-trivial
dovecot-service config they could share?
How do one check the config that was generated and herd is actually
running? Like this?
g1@g1 ~/src$ pstree -pa | grep dovecot
|-dovecot,24213 -F -c /gnu/store/fq2spszyidjp56wmy38b1wma1p2irqgc-dovecot.co
... or is there a better way?
And this must be obvious ... how do I view the dovecot config that _will
be_ generated by system reconfigure?
TIA - George
next reply other threads:[~2016-08-19 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 16:52 g1 [this message]
2016-08-19 17:53 ` working dovecot-service config anyone? myglc2
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=86twegvgz7.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).