mailu/core/nginx
bors[bot] e600f20762
Merge
2468: Ensure that Mailu keeps working even if it can't obtain a certificate from LE r=mergify[bot] a=nextgens

## What type of PR?

bug-fix

## What does this PR do?

Ensure that Mailu keeps working even if it can't obtain a certificate from letsencrypt for one of the HOSTNAMES

Without this TLS configuration would fail and Mailu would operate without TLS completely.

I haven't tested it but thought this used to work previously... maybe certbot has changed something

### Related issue(s)
- closes 

## Prerequisites
Before we can consider review and merge, please make sure the following list is done and checked.
If an entry in not applicable, you can check it or remove it from the list.

- [x] In case of feature or enhancement: documentation updated accordingly
- [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/workflow.html#changelog) entry file.


Co-authored-by: Florent Daigniere <nextgens@freenetproject.org>
..
conf ghostwheel42's suggestions
static set expire headers only for mailu content
Dockerfile Merge branch 'master' of github.com:Mailu/Mailu into feature-switch-snappymail
certwatcher.py Use environment variables for cert paths/names in nginx certwatcher
config.py ghostwheel42's suggestions
letsencrypt.py Ensure that Mailu keeps working even if it can't obtain a certificate from letsencrypt for one of the HOSTNAMES
start.py Add certificate watcher for external certs to reload nginx