Archive-Team
/
docker-mailserver
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: Add LDAP compatibility caveat for `RELAY_HOST`

This commit is contained in:
polarathene 2024-01-31 17:00:03 +13:00
parent ae075d87e8
commit 525d9f0e15
3 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/content/config/advanced/mail-forwarding/aws-ses.md
View File

@ -15,7 +15,7 @@ title: 'Mail Forwarding | AWS SES'
```env
RELAY_HOST=email-smtp.us-west-2.amazonaws.com
RELAY_PORT=587
# Alternative to RELAY_HOST + RELAY_PORT:
# Alternative to RELAY_HOST + RELAY_PORT which is compatible with LDAP:
DEFAULT_RELAY_HOST=[email-smtp.us-west-2.amazonaws.com]:587
RELAY_USER=aws-user

2
docs/content/config/advanced/mail-forwarding/relay-hosts.md
View File

@ -22,8 +22,8 @@ All mail sent outbound from DMS (_where the sender address is a DMS account or a
Configure the default relayhost with either of these ENV:
- Preferable (_LDAP compatible_): `DEFAULT_RELAY_HOST` (eg: `[mail.relay-service.com]:25`)
- `RELAY_HOST` (eg: `mail.relay-service.com`) + `RELAY_PORT` (default: 25)
- `DEFAULT_RELAY_HOST` (eg: `[mail.relay-service.com]:25`)
Most relay services also require authentication configured:

2
docs/content/config/environment.md
View File

@ -1020,6 +1020,8 @@ Supported ENV for the [Relay Host][docs::relay-host] feature.
This is advised unless you need support for sender domain opt-out (via `setup relay exclude-domain`).
The implementation for `RELAY_HOST` is not compatible with LDAP.
!!! tip "Opt-in for relay host support"
Enable relaying only for specific sender domains instead by using `setup relay add-domain`.