mailcow/mailcow-dockerized

mailcow: dockerized - 🐮 + 🐋 = 💕

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 6 minutes ago
Added to GitGenius on September 4th, 2026
Created on December 9th, 2016
Open Issues & Pull Requests: 518 (+0)
GitHub issues: Enabled
Number of forks: 1,801
Total Stargazers: 13,390 (+0)
Total Subscribers: 195 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 21.3 hours
Mean response time: 46.2 days
90th percentile: 60.3 days
Tracked items: 833

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "not reproduceable" is answered fastest, typically in about 4 hours, while "neverstale" waits about 6 days. 49% of tracked open issues have had no activity in three months. Only 6% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 273
New in 7 days: 7
Closed in 7 days: 2
Avg open age: 656 days
Stale 30+ days: 227
Stale 90+ days: 173

Recent activity

Opened in 7 days: 5
Closed in 7 days: 2
Comments in 7 days: 4
Events in 7 days: 9

Top labels

  • bug (460)
  • enhancement (352)
  • stale (185)
  • confirmed (47)
  • neverstale (25)
  • not-a-bug (24)
  • upstream (19)
  • support (17)

Detailed Description

mailcow: dockerized is a mail server platform that bundles multiple open-source components into a Docker-based system for managing email infrastructure.

The project solves the complexity of deploying and maintaining a complete mail server by containerizing essential components including Postfix for SMTP, Dovecot for IMAP, Rspamd for spam filtering, ClamAV for antivirus scanning, and SOGo for groupware functionality. It handles certificate management through ACME integration and provides a unified Docker Compose setup that abstracts away the configuration burden of running these services individually.

Organizations running their own mail infrastructure should choose this tool if they want a pre-integrated, containerized mail server without managing each component separately. It suits projects where teams need full control over their email system and prefer Docker-based deployment. The project includes administrative interfaces and documentation pointing users to official resources for installation and support guidance.

Development activity shows sustained engagement with the project maintaining responsiveness to issues and pull requests. The maintainers actively solicit community feedback through multiple channels including a dedicated community forum, Telegram groups, and social media accounts. The project accepts financial support through GitHub Sponsors and commercial support contracts, indicating a structured approach to sustainability. Security issues are handled through a dedicated disclosure process rather than public issue tracking.