Occasionally, when upgrading SmarterMail from an earlier Build to one of the latest Builds (e.g., Build 8747, December 13, 2023) a system administrator may see the following toast notification:
The toast notification states "One or more port bindings contain a certificate without a private key. Protocols may not function properly."
What this means is that there are one or more SSL certificates that have a mismatched private key, or the certificate wasn't initially exported and set up using a .PFX file. In order to correct this, the affected certificates will need to be re-exported as .PFX files with the primary key included. Then, the affected bindings need to be updated.
To find which bindings are affected, simply go to Settings -> Bindings. Any affected bindings will be noted with a red icon. Once the new certs are exported and added to the Certificates folder (by default, C:\SmarterMail\Certificates), these bindings can be updated.
The affected bindings will look like this: