From 9b6310d10db1f91492cd2e5f3c01441d51bf7e47 Mon Sep 17 00:00:00 2001
From: Nicolas Dupont <npg.dupont@gmail.com>
Date: Mon, 19 Jan 2026 11:32:12 +0100
Subject: [PATCH 1/2] Update SMTP config

---
 content/collections/reference/configuration.md | 9 ++++++++-
 content/deployment/how-to/deploy.md            | 5 ++++-
 2 files changed, 12 insertions(+), 2 deletions(-)

diff --git a/content/collections/reference/configuration.md b/content/collections/reference/configuration.md
index 3c32adeb..06b73ad5 100644
--- a/content/collections/reference/configuration.md
+++ b/content/collections/reference/configuration.md
@@ -93,7 +93,14 @@ The logger section configures logging and error notification settings.
     name="logger.smtp.host"
     type="string"
     description="SMTP server hostname."
-    default="smtp-relay.sendinblue.com"
+    default="smtp-relay.brevo.com"
+/>}}
+
+{{< refItem
+    name="logger.smtp.port"
+    type="number"
+    description="SMTP server port."
+    default="587"
 />}}
 
 {{< refItem
diff --git a/content/deployment/how-to/deploy.md b/content/deployment/how-to/deploy.md
index d862d0e2..362665d3 100644
--- a/content/deployment/how-to/deploy.md
+++ b/content/deployment/how-to/deploy.md
@@ -218,7 +218,7 @@ This section uses [Ansible Vault](https://docs.ansible.com/ansible/latest/vault_
 
 This section describes how to configure the engine to use a specific SMTP server to send email notifications when it encounters errors during the tracking process. This helps you stay informed about issues that need attention and allows you to restart the tracking process if needed.
 
-1. Get the SMTP credentials (host, username, password) from your email provider
+1. Get the SMTP credentials (host, port, username, password) from your email provider
 
 2. Update collection SMTP configuration within the `logger` key of `@opentermsarchive/engine` in the `config/production.json` file:
 
@@ -226,11 +226,14 @@ This section describes how to configure the engine to use a specific SMTP server
       "logger": {
          "smtp": {
             "host": "<smtp_host>",
+            "port": <smtp_port>,
             "username": "<smtp_username>"
          },
       },
    ```
 
+   > **Note**: The default port is 587. If your hosting provider blocks standard SMTP ports (25, 465, 587), you can try to use port 2525 as an alternative.
+
 3. Store the password in `deployment/.env`:
 
    ```shell

From 0c624f7d5e5fe6f1f4363aa498cf30318a667bd4 Mon Sep 17 00:00:00 2001
From: Nicolas Dupont <npg.dupont@gmail.com>
Date: Mon, 19 Jan 2026 14:32:06 +0100
Subject: [PATCH 2/2] Improve wording
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-authored-by: Clément Biron <clement.biron@gmail.com>
---
 content/deployment/how-to/deploy.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/deployment/how-to/deploy.md b/content/deployment/how-to/deploy.md
index 362665d3..430b1047 100644
--- a/content/deployment/how-to/deploy.md
+++ b/content/deployment/how-to/deploy.md
@@ -232,7 +232,7 @@ This section describes how to configure the engine to use a specific SMTP server
       },
    ```
 
-   > **Note**: The default port is 587. If your hosting provider blocks standard SMTP ports (25, 465, 587), you can try to use port 2525 as an alternative.
+   > **Note**: If the default port (587) is blocked by your hosting provider, you can try using 2525 as an alternative.
 
 3. Store the password in `deployment/.env`: