foxcpp/maddy

✉️ Composable all-in-one mail server.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 56 minutes ago
Added to GitGenius on September 11th, 2026
Created on November 7th, 2016
Open Issues & Pull Requests: 143 (+0)
GitHub issues: Enabled
Number of forks: 327
Total Stargazers: 6,085 (+0)
Total Subscribers: 56 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.9 days
Mean response time: 77.7 days
90th percentile: 203.6 days
Tracked items: 74

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 73% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 5% of issues opened in the past year have been closed. Three people close 79% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 55
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 892 days
Stale 30+ days: 53
Stale 90+ days: 49

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (44)
  • new feature (25)
  • ready-for-release (17)
  • good first issue (8)
  • help wanted (5)
  • mta-in (5)
  • filter (2)
  • imap (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Maddy is a mail server that provides SMTP, IMAP, and related email services in a single composable application.

The project addresses the complexity of running email infrastructure by combining multiple mail server functions into one unified system. Rather than deploying separate components for SMTP relay, IMAP access, and authentication, maddy integrates these capabilities with support for DKIM, DMARC, and SPF authentication protocols. The composable architecture allows operators to enable or disable modules based on their specific needs, reducing unnecessary overhead for simpler deployments while supporting full-featured setups.

Maddy suits operators who want to self-host email without managing multiple interdependent services. It works well for small to medium deployments where simplicity and maintainability matter more than scaling to massive user bases. The all-in-one approach eliminates coordination problems between separate SMTP and IMAP daemons and reduces the configuration surface area compared to traditional mail server stacks. Those evaluating alternatives should note that the README does not position maddy against other mail servers by name, so direct comparisons to established options are not documented in the project itself.

The project shows consistent maintenance with regular commits addressing bugs and features. Pull requests receive timely review and feedback from maintainers. The codebase demonstrates active refinement of the configuration system and protocol implementations. Issue discussions indicate engagement with user problems and feature requests, though some issues remain open for extended periods. The project maintains documentation through its homepage and README, though the depth of certain operational topics varies.