Hey Barry,

Just a heads up, for the Let's Encrypt issue, it’s worth checking if the server can directly access the domains it’s trying to generate certificates for. If those URLs aren’t reachable from the server (due to DNS, firewall, or proxy issues), the renewal will fail.

On the IIS binding error that Pusparaj Raut ran into, it looks like SmarterMail is handling the cert import, but this error can also pop up if the Centralized Certificate Store is enabled while trying to assign a dedicated certificate manually. That combo tends to cause conflicts in IIS.

If the problem sticks around or you run into anything else, I’d suggest opening a ticket with the support team so they can dig in further.

Kind regards,

Glad to hear you’ve opened a ticket. Our support team has extensive experience with SSL related issues and should be able to help you get this resolved quickly.

Kind regards,

We encountered the issue again with one of our customer's email services. After verifying the DNS records and IIS bindings, everything appeared to be configured correctly; however, we were still unable to access webmail.

To resolve the issue, we:

• Manually removed the auto-installed SSL certificates from IIS.(Generated by Letsencrypt)

• Imported the .pfx file from the  Certificate Folder Path.

• Manually re-bound the certificate in IIS

After restarting the IIS service, the issue was resolved and webmail started functioning normally again.