Note that the Mailcow Sender ACL is now automated, not a manual step

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-30 08:59:47 -04:00
parent 57dbaf25f7
commit 96eaf88067
1 changed files with 1 additions and 1 deletions
@@ -24,4 +24,4 @@ The workflows in `.gitea/workflows/` pin a specific `eec-campaigns` version (cur

 ## Sending as hello@thistleandmoth.org

-Listmonk sends everything — every domain's campaigns — authenticated as one shared identity, `hello@reground.org`. For a campaign here to actually go out `From: hello@thistleandmoth.org` instead of bouncing as a spoofing attempt, Mailcow's Sender ACL on `hello@reground.org` has to explicitly allow it. That's already done — no action needed unless the sending address ever changes.
+Listmonk sends everything — every domain's campaigns — authenticated as one shared identity, `hello@reground.org`. For a campaign here to actually go out `From: hello@thistleandmoth.org` instead of bouncing as a spoofing attempt, Mailcow's Sender ACL on `hello@reground.org` has to explicitly allow it — this is set automatically by `reground-infrastructure`'s `mailcow` role (it derives the full Sender ACL from `mailcow_mailboxes`, so any co-hosted client's `hello@` mailbox is covered without a manual step).