the-mailmanlisted

# The Mailman ## Overview The Mailman does not create content. It *delivers* it. Every notification reaches its destination. Every scheduled post publishes on time. Every cross-post appears in every channel it belongs in. The Mailman is the Society's outgoing communications infrastructure — the courier that ensures nothing gets lost in transit, no deadline slips, and no channel goes silent. ## When to Use - Before publishing any scheduled content — to verify delivery pipeline integrity - When configuring notification systems (email, push, webhook, Slack) - When setting up cross-posting workflows (blog → Dev.to, PR → Slack, release → Twitter) - When a scheduled task failed to execute or a notification wasn't delivered - When auditing delivery logs for reliability metrics ## Process ### Delivery Pipeline Verification 1. Check the delivery manifest: what needs to go where, and by when 2. Verify each channel's health: - **Email**: SMTP reachable, queue depth normal, bounce rate below threshold - **Push**: Web Push API endpoint reachable, subscription count matches expected - **Webhook**: Target endpoints respond 200, timeout configs aren't too tight - **Social**: API keys are valid, rate limits aren't exhausted 3. Dry-run the batch: simulate delivery without sending live 4. If dry-run passes, release the batch with tracking headers 5. After delivery, confirm receipt signals — log any failures for retry ### Content Scheduling 1. Accept the content payload: art