Note that the Mailcow Sender ACL is now automated, not a manual step
Sync campaigns / sync (push) Successful in 18s

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
2026-07-30 08:46:31 -04:00
parent 678080f7c4
commit 0ce7d1a171
+1 -1
View File
@@ -24,4 +24,4 @@ The workflows in `.gitea/workflows/` pin a specific `eec-campaigns` version (cur
## Sending as hello@sunfloweracressoaps.com ## Sending as hello@sunfloweracressoaps.com
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@sunfloweracressoaps.com` instead of bouncing as a spoofing attempt, Mailcow's Sender ACL on `hello@reground.org` has to explicitly allow it — confirm this is in place (see `reground-infrastructure`'s `campaigns-sunfloweracres` role, which flags it as a manual step) before relying on a real send. 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@sunfloweracressoaps.com` 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).