From 0ce7d1a1713cb4f00c8ac3148d439ab9a6854718 Mon Sep 17 00:00:00 2001 From: Will Estes Date: Thu, 30 Jul 2026 08:46:31 -0400 Subject: [PATCH] Note that the Mailcow Sender ACL is now automated, not a manual step Co-Authored-By: Claude Sonnet 5 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e832408..34f388a 100644 --- a/README.md +++ b/README.md @@ -24,4 +24,4 @@ The workflows in `.gitea/workflows/` pin a specific `eec-campaigns` version (cur ## 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).