From c09e206bdb05a8057c5b4f2b90593837792ecc2f Mon Sep 17 00:00:00 2001
From: Adrien Reslinger <adrien@reslinger.net>
Date: Mon, 4 Jan 2021 01:30:44 +0100
Subject: [PATCH] Fix certificate for lego

---
 templates/etc/dovecot/conf.d/10-ssl.conf.j2 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/templates/etc/dovecot/conf.d/10-ssl.conf.j2 b/templates/etc/dovecot/conf.d/10-ssl.conf.j2
index 31485ed..cceaae7 100644
--- a/templates/etc/dovecot/conf.d/10-ssl.conf.j2
+++ b/templates/etc/dovecot/conf.d/10-ssl.conf.j2
@@ -11,8 +11,8 @@ ssl = required
 # dropping root privileges, so keep the key file unreadable by anyone but
 # root. Included doc/mkcert.sh can be used to easily generate self-signed
 # certificate, just make sure to update the domains in dovecot-openssl.cnf
-ssl_cert = </etc/letsencrypt/live/{{ postfix_myhostname }}/cert.pem
-ssl_key = </etc/letsencrypt/live/{{ postfix_myhostname }}/privkey.pem
+ssl_cert = </etc/lego/certificates/{{ postfix_myhostname }}.crt
+ssl_key = </etc/lego/certificates/{{ postfix_myhostname }}.key
 
 # If key file is password protected, give the password here. Alternatively
 # give it when starting dovecot with -p parameter. Since this file is often
@@ -23,7 +23,7 @@ ssl_key = </etc/letsencrypt/live/{{ postfix_myhostname }}/privkey.pem
 # PEM encoded trusted certificate authority. Set this only if you intend to use
 # ssl_verify_client_cert=yes. The file should contain the CA certificate(s)
 # followed by the matching CRL(s). (e.g. ssl_ca = </etc/pki/dovecot/certs/ca.pem)
-ssl_ca = /etc/letsencrypt/live/{{ postfix_myhostname }}/chain.pem
+ssl_ca = /etc/lego/certificates/{{ postfix_myhostname }}.issuer.crt
 
 # Require that CRL check succeeds for peer certificates.
 #ssl_require_crl = yes