Hi Yassine, hi Kostya,
On 14.03.19 10:17, Kostya Vasilyev via dovecot wrote:
On Thu, Mar 14, 2019, at 12:09 PM, Yassine Chaouche via dovecot wrote:
On 3/14/19 9:55 AM, Patrick Cernko via dovecot wrote:
[...] the way we have configured exim, it neither needs reload or
restart but reads the
On Thu, Mar 14, 2019, at 12:09 PM, Yassine Chaouche via dovecot wrote:
> On 3/14/19 9:55 AM, Patrick Cernko via dovecot wrote:
>
> > [...] the way we have configured exim, it neither needs reload or
> > restart but reads the certificate file every time it has to use it.
>
> What happens if you
On Thu, Mar 14, 2019, at 11:33 AM, Yassine Chaouche via dovecot wrote:
On 3/14/19 9:32 AM, Yassine Chaouche via dovecot wrote:
The general answere here is try and see, as you could totally test it
on your own. The certificate is read at startup and put in memory for
the rest of the execution
On 3/14/19 9:55 AM, Patrick Cernko via dovecot wrote:
[...] the way we have configured exim, it neither needs reload or
restart but reads the certificate file every time it has to use it.
What happens if you goof off in the middle of an opeartion, temporarily
putting a wrong file instead of
On Thu, Mar 14, 2019, at 11:33 AM, Yassine Chaouche via dovecot wrote:
> On 3/14/19 9:32 AM, Yassine Chaouche via dovecot wrote:
> > The general answere here is try and see, as you could totally test it
> > on your own. The certificate is read at startup and put in memory for
> > the rest of the
Hi,
On 14.03.19 09:33, Yassine Chaouche via dovecot wrote:
On 3/14/19 9:32 AM, Yassine Chaouche via dovecot wrote:
The general answere here is try and see, as you could totally test it
on your own. The certificate is read at startup and put in memory for
the rest of the execution time.
On 3/14/19 9:32 AM, Yassine Chaouche via dovecot wrote:
The general answere here is try and see, as you could totally test it
on your own. The certificate is read at startup and put in memory for
the rest of the execution time. Dovecot won't monitor the file for
changes on disk, as this would
The general answere here is try and see, as you could totally test it on
your own. The certificate is read at startup and put in memory for the
rest of the execution time. Dovecot won't monitor the file for changes
on disk, as this would waste CPU cycles and make dovecot only slower for
no
Running dovecot 2.2, apologies if this question has been asked before:
I've done the research but couldn't find anything.
I run a server that uses dovecot as a MUA for Postfix and have a Let's
Encrypt certificate that auto-renews through certbot on Ubuntu server
16.04. Dovecot did not pick up
