From a809f4d12481fa4de477a0e0278b05258b0c590b Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 26 Feb 2026 02:42:07 +0000 Subject: [PATCH] Changes before error encountered Co-authored-by: spantaleev <388669+spantaleev@users.noreply.github.com> --- docs/configuring-playbook-email.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md index abdfca6a4..859da8cf2 100644 --- a/docs/configuring-playbook-email.md +++ b/docs/configuring-playbook-email.md @@ -19,11 +19,11 @@ The [Ansible role for exim-relay](https://github.com/mother-of-all-self-hosting/ ## Why use exim-relay? -**Benefits of using exim-relay** instead of configuring SMTP directly in each service ([Synapse](configuring-playbook-synapse.md), [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), bridges, bots, etc.): +**Benefits of using exim-relay** instead of configuring SMTP directly in each service: 1. **Final delivery capability**: Can deliver emails directly if you don't have an SMTP server -2. **Centralized configuration**: Configure your upstream SMTP server once in exim-relay, then point all services there—no need to configure SMTP in each component +2. **Centralized configuration**: Configure your upstream SMTP server once in exim-relay, then point all services ([Synapse](configuring-playbook-synapse.md), [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), etc.) there—no need to configure SMTP in each component 3. **Local spooling**: Stores messages locally and retries delivery if your upstream SMTP server is temporarily unavailable