RBoy wrote: ↑
Does do you hMailServer to bind to the SSL certificate generated by Win Acme V2? It seems to generate a new certificate filename each time it renews the domain.
This is not an easy task to do because the issuing Letsencrypt ACME v2 Server checks your Host name while processing your SSL-Certificate request.
This means, you can only receive a SSL-Certificate from Letsencrypt for *.mydomain.com if your hMailServer is also running on the public internet on *.mydomain.com
if you do it the right way.
1) It only works if hMailServer runs on a Public Internet Domain (on NAT-Router cases , it can only work with port forwarding resolvable by a Public DNS-Server.
2) It will only work, if we implement a HTTP-Server in hMailServer on port 80 (unencrypted) because the issuing Letsencrypt server will check for it.
3) It will only work, if we implement also ACME v2 in hMailServer which can interfaces with hMailServers internal HTTP-Server on port 80
4) All above steps needs to be repeated every 90 Days to renew the outdated SSL-Certificates