Feedback email stack is mautic resend not listmonk

---

name: Email stack is Mautic + Resend; Listmonk is a dead false-start description: Correct memory error: Justin's live email stack is Mautic (CT112) + Resend, not Listmonk — Listmonk was deployed then abandoned. type: feedback

---

Assistant incorrectly asserted 'Listmonk' repeatedly as the email-capture backend during a planning conversation. Justin caught it. Verified via files: Mautic (forge-mail, CT112, 192.168.86.87) + Resend (delivery/SMTP) is the actual live stack. Listmonk (v6.2, port 9000, lists.justinsforge.com) was deployed during an earlier multi-brand email plan but its API auth never worked (required direct Postgres inserts) and the Sip N Serve handoff explicitly says it's "likely being retired in favor of Mautic." It's a dead deployment.

Why: existing memory file reference_forge_mail_mautic.md may not clearly flag Listmonk as superseded, and an older plan doc (multi-brand-email-listmonk-resend-2026-07-01.md) still specifies Listmonk, which is what misled the assistant.

How to apply: Any future mention of email-capture-to-list architecture should say Mautic + Resend, never Listmonk. If asked to build capture flows, wire to Mautic API. Consider flagging/tearing down the CT112 Listmonk container as dead weight (not yet done, pending confirmation no data lives only there).

[auto-memory session d316bfec-dd4c-4598-92d1-2ec51bac5a91, confidence 0.85, mode direct]