cqrenet/matrix-docker-ansible-deploy
3
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2026-02-28 09:53:09 +00:00
Code Issues Wiki Activity

Changes before error encountered

Browse Source 
Co-authored-by: spantaleev <388669+spantaleev@users.noreply.github.com>
This commit is contained in:
copilot-swe-agent[bot]
2026-02-26 02:42:07 +00:00
committed by Slavi Pantaleev
parent ceebf644a3
commit a809f4d124
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/configuring-playbook-email.md
View File

@@ -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