Using letsencrypt key and cert instead of iRedMail.key and iRedMail.crt

[martin-jamszolik]

Hello,
This is more of a question then an issue. I would like to upgrade to the latest lejmr/iredmail 0.9.8 Version, but I noticed a lot of development around generating certificates etc... I was wondering if the following would still work for me if I upgrade?

docker run -dit --restart always --privileged -p 80:80 -p 443:443 -p 25:25 -p 587:587 -p 993:993  \   
     #snip#   
           -v /opt/docker-volumes/iredmail/mysql:/var/lib/mysql \
           -v /opt/docker-volumes/iredmail/vmail:/var/vmail \
           -v /opt/docker-volumes/iredmail/clamav:/var/lib/clamav \
           -v /etc/letsencrypt/live/mail.example.com/privkey.pem:/etc/ssl/private/iRedMail.key:ro \
           -v /etc/letsencrypt/live/mail.example.com/fullchain.pem:/etc/ssl/certs/iRedMail.crt:ro \
           --name=iredmail lejmr/iredmail:mysql-latest

Overall, thank you for this project and everyone's contribution. It has been really helpful.

[lejmr]

Oh yes, this is still valid configuration. The new development was around the moment these files are not present in the container, so they are generate ad-hoc.. In other words, if you mount your certs into the container, your ad-hoc certificates are not generated.