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

chore: update demo-setups 

I think this is not nicely maintainable in the long run; hence, I
changed the v14 references to point to the most current state. This way,
we avoid the necessity for changes on each release, which I am unwilling
to accept.

Signed-off-by: Georg Lauterbach <44545919+georglauterbach@users.noreply.github.com>
This commit is contained in:
Georg Lauterbach 2025-02-16 20:30:38 +01:00
parent 0ebf820b00
commit 335a64c7bc
No known key found for this signature in database
GPG Key ID: D84CD4AA46D7F099
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
demo-setups/fetchmail-compose.yaml
View File

@ -1,10 +1,10 @@
# Docs: https://docker-mailserver.github.io/docker-mailserver/v14.0/config/advanced/mail-fetchmail # Docs: https://docker-mailserver.github.io/docker-mailserver/latest/config/advanced/mail-fetchmail
# Additional context, with CLI commands for verification: # Additional context, with CLI commands for verification:
# https://github.com/orgs/docker-mailserver/discussions/3994#discussioncomment-9290570 # https://github.com/orgs/docker-mailserver/discussions/3994#discussioncomment-9290570
services: services:
dms-fetch: dms-fetch:
image: ghcr.io/docker-mailserver/docker-mailserver:latest # :14.0 image: ghcr.io/docker-mailserver/docker-mailserver:latest
hostname: mail.example.test hostname: mail.example.test
environment: environment:
ENABLE_FETCHMAIL: 1 ENABLE_FETCHMAIL: 1
@ -26,7 +26,7 @@ services:
target: /tmp/docker-mailserver/fetchmail.cf target: /tmp/docker-mailserver/fetchmail.cf
dms-remote: dms-remote:
image: ghcr.io/docker-mailserver/docker-mailserver:latest # :14.0 image: ghcr.io/docker-mailserver/docker-mailserver:latest
hostname: mail.remote.test hostname: mail.remote.test
environment: environment:
# Allows for us send a test mail easily by trusting any mail client run within this container (`swaks`): # Allows for us send a test mail easily by trusting any mail client run within this container (`swaks`):

8
demo-setups/relay-compose.yaml
View File

@ -1,11 +1,11 @@
# Docs: https://docker-mailserver.github.io/docker-mailserver/v14.0/config/advanced/mail-forwarding/relay-hosts/ # Docs: https://docker-mailserver.github.io/docker-mailserver/latest/config/advanced/mail-forwarding/relay-hosts/
# Additional context, with CLI commands for verification: # Additional context, with CLI commands for verification:
# https://github.com/docker-mailserver/docker-mailserver/issues/4136#issuecomment-2253693490 # https://github.com/docker-mailserver/docker-mailserver/issues/4136#issuecomment-2253693490
services: services:
# This would represent your actual DMS container: # This would represent your actual DMS container:
dms-sender: dms-sender:
image: mailserver/docker-mailserver:latest # :14.0 image: mailserver/docker-mailserver:latest
hostname: mail.example.test hostname: mail.example.test
environment: environment:
# All outbound mail will be relayed through this host # All outbound mail will be relayed through this host
@ -37,7 +37,7 @@ services:
# Pretend this is your third-party relay service: # Pretend this is your third-party relay service:
dms-relay: dms-relay:
image: mailserver/docker-mailserver:latest # :14.0 image: mailserver/docker-mailserver:latest
hostname: smtp.relay-service.test hostname: smtp.relay-service.test
environment: environment:
# WORKAROUND: Bypass security checks from the mail-client (dms-sender container) # WORKAROUND: Bypass security checks from the mail-client (dms-sender container)
@ -58,7 +58,7 @@ services:
# Pretend this is another mail server that your target recipient belongs to (like Gmail): # Pretend this is another mail server that your target recipient belongs to (like Gmail):
dms-destination: dms-destination:
image: mailserver/docker-mailserver:latest # :14.0 image: mailserver/docker-mailserver:latest
hostname: mail.destination.test hostname: mail.destination.test
# WORKAROUND: dms-relay must be able to resolve DNS for `@destination.test` to the IP of this container: # WORKAROUND: dms-relay must be able to resolve DNS for `@destination.test` to the IP of this container:
# Normally a MX record would direct mail to the MTA (eg: `mail.destination.test`) # Normally a MX record would direct mail to the MTA (eg: `mail.destination.test`)