similar to: Reload Dovecot with thousands of domains.

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

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

On Mon, Feb 25, 2019 at 11:54 PM Simon Matter via CentOS <centos at centos.org> wrote: > > > > What makes you think this has *anything* to do with systemd? Bitching > > about systemd every time you hit a problem isn't helpful. Don't. > > If it's not systemd, who else does it? Can you elaborate, please? > I'll wager it's the mdadm.service

Automatic renewal The Ubuntu package for certbot comes pre-configured with systemd timer that will automatically renew existing certificates. What it does not handle however is reloading postfix/dovecot so that they will begin using the new certificates. For that, we need to implement a hook. Certbot has both pre and post hooks that you can use to execute a script prior to and after the renewal

Apologies if it's considered off-topic, but I'm not sure in what part of the system the issue lies. So I am giving as much info as possible, not knowing which is most relevant. I have two VMs hosted on ESX, running CentOS 6.10 One has kernel 2.6.32-754.11.1.el6.i686 and the other has 2.6.32-754.18.2.el6.i686 Both have selinux, currently in permissive mode. On both machines we have

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

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

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

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.

El jue., 11 oct. 2018 a las 10:58, Reio Remma (<reio at mrstuudio.ee>) escribi?: > On 11/10/2018 11:55, Ignacio Garcia wrote: > > Hi there. I've been using Dovecot for quite some time now but I just > > started using Let's Encrypt certs. Since LE certs are renewed > > automatically without user intervention I'm wondering if I will need > > to restart

Hi Ricardo, On Mon, Mar 13, 2023 at 04:22:54PM +0100, Ricardo Garcia wrote: > This is a reminder that the deadline for new memberships and renewals > finishes in a couple of weeks. Original email follows. > > Thanks for your attention. I don't know if I'm the only one affected by this issue, but I've just received today two months of e-mails from x.org, including all the

And remove that "postfix reload" command - Postfix doesn't require explicit reloading. It'll pickup the changed cert automagically. Daniel On 9/12/2017 9:26 AM, Daniel Miller wrote: > What's wrong with using a certbot "post-hook" script such as: > > #!/bin/bash > echo "Letsencrypt renewal hook running..." > echo

Brian, I think you said we can let these go, correct? Russ -------------- next part -------------- An embedded message was scrubbed... From: <Renewals at godaddy.com> Subject: Certified GoDaddy.com Renewal Notice Date: 1 Oct 2008 06:10:10 -0700 Size: 42493 URL: <http://lists.centos.org/pipermail/centos/attachments/20081001/6eadca7f/attachment-0004.eml>

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

From my experience, restart is required. On Debian Strech, I edited cron job to: certbot -q renew --renew-hook 'service dovecot restart' --renew-hook 'service postfix reload' Milo Dne 2018-10-11 v 10:55 Ignacio Garcia napsal(a): > Hi there. I've been using Dovecot for quite some time now but I just > started using Let's Encrypt certs. Since LE certs are renewed

Install letsencrypt and request a certificate specifying the webroot of your Icecast server and the host.domain: certbot-auto certonly --webroot --webroot-path /usr/share/icecast2/web/ -d icecast.domain.name Now you should have a certificate for your server, it's only in the wrong format for Icecast, copy the key and the certificate to 1 file with the following cmd: cat

Hello, How did you get icecast and letsencrypt certificates working? Thanks. Dave. On 9/6/18, _zer0_ gravity <zer0___ at hotmail.com> wrote: > That’s what I have been looking for, thanks ! > > From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Tycho Eggen > Sent: donderdag 6 september 2018 22:21 > To: Icecast streaming server user discussions > Subject: Re:

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