similar to: Graceful dovecot reload for LE certificate renewals

Hi Dovecot-gurus With the introduction of LE certificates the certificate renewal cycle is a lot faster, unfortunately even a "dovecot reload" cuts the existing connections when doing the cert updates, which is quite frustrating - and yes most clients automatically reconnect but still... Is any work going into implementing a more ?graceful reload? for dovecot like the one for nginx

Hi ppl. I am trying to locate the best prometheus exporter for use with Dovecot 2.3 in connection with the new metrics/stats module. Any pointers in the right direction will be appreciated - seems like there is a bunch out there which all works with the old stats module. Anybody have something ?in the works? for 2.3 ? Kind Regards, Sidsel Jensen -------------- next part --------------

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 time. Dovecot won't monitor the file for > > changes on

Hi We are very eager to test the zstd compression in the upcoming Dovecot 2.3.12 release - any pointer as to when that is expected to be released? Kind Regards, Sidsel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 874 bytes Desc: Message signed with OpenPGP URL:

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 reason. The process (or person) that changes the file is responsible to restart dovecot to reload

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. Dovecot won't monitor the file for >> changes on disk, as this

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 goof off in the middle of an opeartion, temporarily > putting a wrong file

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 on the new certificate for the hostname. It did after a restart. To be clear: Let's

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 the new certificate, and exim starts delivering the new broken certificate right away ? or

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 waste CPU cycles and make dovecot only > slower for no reason. The process

On 16/02/16 16:59, david wrote: > Folks > > This might be the wrong place to ask, but I don't know where to turn. > My internal home network, including wireless, is controlled by a > Centos6 server, which provides dhcpd services, along with NAT. I have > DHCPD configured with the addresses 192.168.155.200 through > 192.168.155.254 as the range for dynamic allocations.

Rob DNS service for my clients is provided by my gateway server, the same machine as the DHCPD server. I think that's what the "option domain-name-servers" line does. This allows me to provide 192.168 addresses to them when they try to access anything inside the house with a name. If it's not a locally defined name, BIND forwards the request to the internet. I'm not

Folks This might be the wrong place to ask, but I don't know where to turn. My internal home network, including wireless, is controlled by a Centos6 server, which provides dhcpd services, along with NAT. I have DHCPD configured with the addresses 192.168.155.200 through 192.168.155.254 as the range for dynamic allocations. The default-lease time is 1800 seconds, the maximum is 3600

On Sun, 22 Jul 2018, Voytek Eymont wrote: > [...] > so, basically, after each renewal of server's cert I should remember to > reload Dovecot (and maybe Postfix too?) You can add a hook (script) to /etc/letsencrypt/renewal-hooks/deply/ which restarts the services you need. In my case, I have /usr/sbin/apache2ctl graceful /usr/sbin/dovecot reload /usr/sbin/postfix reload This way

Is it enough to issue a `service restart dovecot` when a certificate renews or do I need to service stop/start? -- "A thousand years ago we thought the world was a bowl. Five hundred years ago we knew it was a globe. Today we know it is flat and round carried through space on the back of a turtle. Don't you wonder what shape it will turn out to be tomorrow?" [Lord Vetinari]

On Sun, July 22, 2018 11:22 pm, dclist at list.jmatt.net wrote: > Usually, a browser connects to a web server on port 443, while an email > client connects to an IMAP or POP server on a different port, served by > different software. Just because your browser receives a current/valid > cert, that doesn?t mean your dovecot server is sending the same > certificate. > >

I purchased a new SSL certificate and installed it correctly, using the same combine procedures I?ve always used. I tried to reload the configuration, but it didn?t work. When I try the secure port, it still tells me my key has expired. I have to really think hard about when it will be appropriate to restart the server, so I was hoping that reload would work. Looks like a restart is needed. Is

I tried everything, including changing the name of the new PEM containing the properly concatenated certificates as specified in the Icecast configuration. The reload command did not, does not appear to, re-read the certificate file even though the filename has been changed. To make it work, I had to restart the Icecast server in the usual manner. Is this a bug or is it by design?

On 31 Jul 2024, at 0:05, Steve Matzura wrote: > I tried everything, including changing the name of the new PEM containing the properly concatenated certificates as specified in the Icecast configuration. The reload command did not, does not appear to, re-read the certificate file even though the filename has been changed. To make it work, I had to restart the Icecast server in the usual

Hello!, I have a dovecot server configured with about 3k different domains. It worked without problems until SSL certificates has been installed. After increase available RAM and stabilizing the service my current problem is in renewals. Dovecot reload process consumes a lot of memory for every one certificate renewal. The server has enough memory to support reload in most cases, but if server