maddy

maddy is a self-hosted mail server that implements SMTP for outbound and MX receipt, IMAP storage, DKIM, SPF, DMARC, DANE, and MTA-STS. It replaces the classic Postfix plus Dovecot plus OpenDKIM style stack with one daemon and one configuration model.

Judged purely as an API. What the request contract guarantees on retry, how complete the webhook event coverage is, whether suppressions are readable and writable programmatically, and how much the message log retains when something needs debugging in production.

Against high-frequency programmatic sends where a missed delivery is a product failure, maddy covers none of the capabilities this audience leans on (idempotency keys, webhook coverage, event stream, the suppressions API, batch sending, and SDK breadth), so it fits only where those needs are genuinely absent.

• Idempotency keys: No
• Webhooks: No
• Event stream: No
• Operating since: Not published
• Suppressions API: No
• Best published rate per 1,000: Tiers not published in comparable form
• Batch sending: No
• SDKs: None
• Deliverability: Self-hosted deliverability depends on DNS, IP reputation, queue management, bounce handling, and ongoing abuse controls. maddy includes DKIM, SPF, DMARC, DANE, and MTA-STS building blocks.

Self-hosted deliverability depends on DNS, IP reputation, queue management, bounce handling, and ongoing abuse controls. maddy includes DKIM, SPF, DMARC, DANE, and MTA-STS building blocks.

Infrastructure teams that want a compact self-hosted mail server with modern authentication primitives.

Product teams that need managed deliverability and support.