Auto update certificates in MS Exchange after auto renew

Hello,

I can't find anything on Google.

Is there a way, to setup auto update/set/install of let's encrypt certificates of services like imap, 143, 587, 465, etc. on MS exchange server after auto renewal? I know win-acme but I think that only auto updates certificates in IIS bindings (443).

Regards

Hello @mj-network, welcome to the Let's Encrypt community. :slightly_smiling_face:

Let’s Encrypt offers Domain Validation (DV) certificates.

Thus you need to own and have control over the Domain Name (or have a subdomain under an existing domain name, for example pointed to your server by your employer or school) you wish to obtain a certificate for, from an ICANN Accredited Registrar.

For Let’s Encrypt to issue a Domain Validation (DV) certificate Domain Validation must happen
and it is a CA/Browser Forum Baseline Requirement.

Best Practice - Keep Port 80 Open

What IP addresses does Let’s Encrypt use to validate my web server?
Let’s Encrypt does not publish a list of IP addresses we use to validate,
and these IP addresses may change at any time.

Let's Encrypt uses Multi-Perspective Validation Improves Domain Validation Security - Let's Encrypt

Since these are Domain Validation (DV) certificates the Domain Name System (DNS) is used extensively in the validation process as well a allowing us to assist here on Let's Encrypt community.
DNS Queries need to give consistent results from any location on the Internet, all your authoritative DNS Servers for the Domain need to also give consistent results as well.

Testing and debugging are best done using the Staging Environment as the Rate Limits are much higher. Rate Limits are per week (rolling).

And to assist with debugging there is a great place to start is Let's Debug.

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

Thank you for assisting us in helping YOU!

1 Like

Here are some links to articles that may or may not help

  1. Additional SSL certificates for IMAP and SMTP
  2. How to get iOS email to accept cert renewals for IMAP and SMTP servers?
  3. Mail Certificate smtp/imap problem
  4. Using Let's Encrypt Certificates for Mail and other Apps [ClearOS Documentation]
  5. Using Let’s Encrypt TLS Certificates for SMTP, IMAP, and HTTP
  6. How to secure Postfix using Let’s Encrypt - UpCloud
  7. Install FREE Let's Encrypt certificate in Exchange Server - ALI TAJRAN
1 Like

I don't have a specific suggestion for you, but it sounds like something that most Windows ACME clients ought to be able to do. If nothing else, most clients should have a concept of a "deploy hook" that can run whatever custom script you want in order to handle reloading services after getting new certificates. See win-acme's script documentation, for instance.

You might also want to look through the other Windows-based clients to see if one of them has more out-of-the-box support for what you're trying to do.

2 Likes

win-acme has an example powershell script for (multi-service) Exchange deployment, Certify The Web (which I develop) also has a similar Deployment task available, or you can script your own (e.g. let the app install the cert to the store then run your own powershell to update the cert thumbprint against each service).

4 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.