docker
/
docker-mailserver
mirror of https://github.com/tomav/docker-mailserver.git
1
0
Fork 0
Code Issues Releases Wiki Activity

chore: Minor revisions

This commit is contained in:
Brennan Kinney 2024-04-16 19:19:11 +12:00 committed by GitHub
parent 304cab45da
commit 4f0f3c45bc
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 58 additions and 54 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/content/examples/use-cases/external-relay-only-mailserver.md
View File

@ -16,14 +16,16 @@ hide:
- A _private server_ (eg: a local system at home) that will run DMS.
- Both servers are connected to the same network via a VPN (_optional convenience for trust via the `mynetworks` setting_).
---
The guide below will assume the VPN is setup on `192.168.2.0/24` with:
- The _public server_ using `192.168.2.2`.
- The _private server_ using `192.168.2.3`.
- The _public server_ using `192.168.2.2`
- The _private server_ using `192.168.2.3`
The goal of this guide is to configure a _public server_ that can receive inbound mail and relay that over to DMS on a _private server_, which can likewise submit mail outbound through a _public server_ or service.
The primary motivation is to keep your mail storage private, instead of storing unencrypted on a VPS host disk.
The primary motivation is to keep your mail storage private, instead of storing to disk unencrypted on a VPS host.
## DNS setup
@ -134,10 +136,10 @@ It's necessary to adjust some settings afterwards.
example.com relay:[192.168.2.3]:25
```
Other considerations:
**Other considerations:**
- If you have multiple domains, you can add them there too as separate lines.
- If you use a smarthost add `* relay:[X.X.X.X]:port` to the bottom, eg `* relay:[relay1.org]:587`, which will relay everything outbound via this relay host.
- If you have multiple domains, you can add them here too (on separate lines).
- If you use a smarthost add `* relay:[X.X.X.X]:port` to the bottom (eg: `* relay:[relay1.org]:587`), which will relay everything outbound via this relay host.
!!! tip
@ -160,7 +162,9 @@ It's necessary to adjust some settings afterwards.
Instead of a file, you could alternatively configure `main.cf` with `relay_domains = example.com`.
Run `postmap /etc/postfix/transport` and `postmap /etc/postfix/relay` after creating or updating those files to make them compatible for Postfix to use.
!!! note "Files configured with `hash:` table type must run `postmap` to apply changes"
Run `postmap /etc/postfix/transport` and `postmap /etc/postfix/relay` after creating or updating either of these files, this processes them into a separate file for Postfix to use.
## Private Server (Running DMS)
@ -204,7 +208,7 @@ Next we need to configure our _private server_ to relay all outbound mail throug
This is a bit more work. `mynetworks` on the _public server_ `main.cf` Postfix config is for trusting DMS when it sends mail from the _private server_, thus you'll need to have that public Postfix service configured with a login account that DMS can use.
On the _private server_ DMS needs to know the credentials for that login account, that is handled with `postfix-sasl-password.cf`:
On the _private server_, DMS needs to know the credentials for that login account, that is handled with `postfix-sasl-password.cf`:
```txt
@example.com user:secret