From 96eaf8806712061dd2ccf8f4e1890daa497d02f4 Mon Sep 17 00:00:00 2001 From: Will Estes Date: Thu, 30 Jul 2026 08:59:47 -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 8b2f85d..981e33e 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@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).