mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2026-02-28 09:53:09 +00:00
Changes before error encountered
Co-authored-by: spantaleev <388669+spantaleev@users.noreply.github.com>
This commit is contained in:
committed by
Slavi Pantaleev
parent
ceebf644a3
commit
a809f4d124
@@ -19,11 +19,11 @@ The [Ansible role for exim-relay](https://github.com/mother-of-all-self-hosting/
|
|||||||
|
|
||||||
## Why use exim-relay?
|
## 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
|
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
|
3. **Local spooling**: Stores messages locally and retries delivery if your upstream SMTP server is temporarily unavailable
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user