From eb0c652cedb24c7a09fcbe66a8c43fdba10dad98 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Thu, 31 Jul 2025 17:25:16 -0600 Subject: [PATCH] Redacted Michael Levesque and Deeptree References --- .../Microsoft Exchange/Configuring ACME LetsEncrypt Bot.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Servers/Microsoft Exchange/Configuring ACME LetsEncrypt Bot.md b/Servers/Microsoft Exchange/Configuring ACME LetsEncrypt Bot.md index 5cf51a1..bb5b047 100644 --- a/Servers/Microsoft Exchange/Configuring ACME LetsEncrypt Bot.md +++ b/Servers/Microsoft Exchange/Configuring ACME LetsEncrypt Bot.md @@ -29,8 +29,8 @@ wacs.exe --target manual --host mail.example.org,autodiscover.example.org --certificatestore My --acl-fullcontrol "network service,administrators" --installation iis,script --installationsiteid 1 --script "./Scripts/ImportExchange.ps1" --scriptparameters "'{CertThumbprint}' 'IIS,SMTP,IMAP' 1 '{CacheFile}' '{CachePassword}' '{CertFriendlyName}'" --verbose ``` -* When the command is running, it will ask for an email address for alerts and abuse notifications, just put ["helpdesk@deeptree.tech"](http://%22helpdesk@deeptree.tech%22) as the email address -* If you run into any unexpected errors that result in anything other than exiting with a status "0", consult with Michael Levesque or Nicole Rappe to proceed +* When the command is running, it will ask for an email address for alerts and abuse notifications, just put "**infrastructure@bunny-lab.io**" +* If you run into any unexpected errors that result in anything other than exiting with a status "0", consult with Nicole Rappe to proceed * Check that the domain of the Exchange Server is reachable on port 80 as Let's Encrypt uses this to build the cert. * Searching the external IP of the server on [Shodan](https://www.shodan.io/) will reveal all open ports.