From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Email clients
Date: Sat, 29 Jul 2023 12:20:53 +0100 [thread overview]
Message-ID: <76dffd3b-ebbd-f8a1-5d5e-bfa3e0c5bdac@youngman.org.uk> (raw)
In-Reply-To: <86wmyj10td.fsf@gentoo.org>
On 29/07/2023 11:13, Arsen Arsenović wrote:
> Wols Lists<antlists@youngman.org.uk> writes:
>
>> On 29/07/2023 03:37, Bryan Gardiner wrote:
>>> User of Claws with a local maildir here. One mail per file always
>>> felt safer to me. If you do want to keep using maildir,
>>> net-mail/dovecot provides IMAP access to ~/.maildir out of the box,
>>> and I've found this combination to be reliable.
>> Just a tip which bit me when I first installed dovecot ...
>>
>> The master config file actually chain-loads a local config file, make sure you
>> use it. I edited the master file directly, so of course the first update
>> overwrote and trashed it ...
> That should not happen. Where's the master config file? Is it under a
> directory masked by CONFIG_PROTECT?
And then the dovecot maintainers update things, update the config file,
and it breaks for all users because the config version no longer matches
the program version ...
The master config file is in the obvious place -
/etc/dovecot/dovecot.conf. Just like postfix breaks exactly the same way
- /etc/postfix/main.cf.
Imho dovecot has got this (almost) exactly right. Just like systemd. You
have your master file that is updated by the distro, and you have your
local file that is updated by the sys admin.
dovecot.conf points to a file local.conf, which does not error if it
doesn't exist, but over-rides dovecot.conf if it does. The proper way to
do it!
Unlike postfix - where I can't find a place to split my local config
away from the default config - so every time postfix is updated I have
to make sure it doesn't try to update main.cf !!!
Cheers,
Wol
next prev parent reply other threads:[~2023-07-29 11:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 0:29 [gentoo-user] Email clients Peter Humphrey
2023-07-29 0:38 ` Jack
2023-07-29 2:37 ` Bryan Gardiner
2023-07-29 8:52 ` Wols Lists
2023-07-29 10:13 ` Arsen Arsenović
2023-07-29 11:20 ` Wols Lists [this message]
2023-07-29 13:54 ` Arsen Arsenović
2023-07-29 14:21 ` Wols Lists
2023-07-29 14:50 ` Arsen Arsenović
2023-07-29 16:27 ` Wols Lists
2023-08-02 7:16 ` [gentoo-user] " Nuno Silva
2023-07-29 5:53 ` [gentoo-user] " Philip Webb
2023-07-30 12:07 ` Frank Steinmetzger
2023-07-30 12:25 ` Peter Humphrey
2023-07-29 6:56 ` Neil Bothwick
2023-07-29 11:01 ` Peter Humphrey
2023-07-29 11:23 ` Wols Lists
2023-07-30 19:02 ` Neil Bothwick
2023-07-30 22:53 ` Peter Humphrey
2023-07-30 23:11 ` Neil Bothwick
2023-07-31 7:34 ` Wols Lists
2023-07-31 12:33 ` Peter Humphrey
2023-07-31 13:26 ` Neil Bothwick
2023-07-31 16:03 ` Peter Humphrey
2023-07-31 16:25 ` Peter Humphrey
2023-07-31 17:26 ` Peter Humphrey
2023-07-31 18:13 ` Neil Bothwick
2023-07-31 18:17 ` Michael
2023-08-01 9:53 ` Peter Humphrey
2023-08-01 10:42 ` Michael
2023-08-01 16:56 ` Peter Humphrey
2023-07-31 17:57 ` Michael
2023-08-01 9:55 ` Peter Humphrey
2023-07-31 18:14 ` Neil Bothwick
2023-07-31 14:19 ` Wols Lists
2023-07-31 15:55 ` Peter Humphrey
2023-08-01 18:51 ` Wols Lists
2023-08-01 23:39 ` Peter Humphrey
2023-07-29 9:26 ` Michael
2023-07-31 1:12 ` Matt Connell
2023-07-31 16:14 ` Peter Humphrey
2023-07-31 16:59 ` Matt Connell
2023-07-31 17:16 ` Alexe Stefan
2023-07-31 17:23 ` Matt Connell
2023-07-31 17:32 ` Kusoneko
2023-07-31 17:52 ` [gentoo-user] " Grant Edwards
2023-07-31 18:46 ` Kusoneko
2023-07-31 18:57 ` Matt Connell
2023-07-31 20:22 ` Grant Edwards
2023-07-31 20:24 ` David Rosenbaum
2023-07-31 19:27 ` [gentoo-user] " Laurence Perkins
2023-07-31 17:36 ` Jack
2023-07-31 17:43 ` [gentoo-user] " Grant Edwards
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=76dffd3b-ebbd-f8a1-5d5e-bfa3e0c5bdac@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=gentoo-user@lists.gentoo.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