From 4cdd93e16ea80775c595d2ae660aaa33a58ed837 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Sat, 6 Jan 2024 20:42:33 -0700 Subject: [PATCH] Update Servers/Linux/iRedMail.md --- Servers/Linux/iRedMail.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Servers/Linux/iRedMail.md b/Servers/Linux/iRedMail.md index 8cfdbdc..3f8b8de 100644 --- a/Servers/Linux/iRedMail.md +++ b/Servers/Linux/iRedMail.md @@ -67,7 +67,7 @@ reboot ``` !!! warning "Automatically-Generated Postmaster Password" - When you deploy iRedMail, it will give you a username and password for the postmaster account. If you accidentally forget to document this, you can log back into the server via SSH and see the credentials at `/root/iRedMail-$VERSION/iRedMail.tips`. This file is critical and contains passwords and DKIM information as well. + When you deploy iRedMail, it will give you a username and password for the postmaster account. If you accidentally forget to document this, you can log back into the server via SSH and see the credentials at `/root/iRedMail-$VERSION/iRedMail.tips`. This file is critical and contains passwords and DNS information such as DKIM record information as well. ## Nested Reverse Proxy Configuration In my homelab environment, I run Traefik reverse proxy in front of everything, which includes the NGINX reverse proxy that iRedMail creates. In my scenario, I have to make some custom adjustments to the reverse proxy dynamic configuration data to ensure it will allow self-signed certificates from iRedMail to communicate with the Traefik reverse proxy successfully. You will see an example Traefik configuration file below.