Mailtrain was created by Peter Štefanec (peterstefanec) and Nemanja Avramović as an open-source alternative to commercial email marketing platforms like Mailchimp. The project emerged from a need for a self-hosted solution that could handle newsletter campaigns without the costs and data privacy concerns of SaaS providers.
The first version was released in 2014, built on Node.js with a focus on:
- List segmentation capabilities
- Template management
- Campaign analytics
- Self-hosted deployment
During its early years, Mailtrain established its core feature set:
- Version 1.x: Basic newsletter functionality
- Subscriber list management
- Custom fields for segmentation
- HTML email templates
- Campaign reporting
The project gained popularity among developers and agencies who needed a reliable, self-hosted email marketing solution.
A major rewrite led to Mailtrain 2.0, which introduced significant architectural changes:
- MongoDB: For storing campaign logs and analytics
- Redis: For queue management and caching
- MySQL/MariaDB: For core application data
- Zone-MTA integration: Built-in MTA for direct email delivery
- Multi-user support with role-based permissions
- RSS-to-email campaigns
- Automation workflows (triggered campaigns)
- MJML template support
- Improved API
Mailtrain found its niche among:
- Web agencies: Managing multiple client newsletters
- E-commerce businesses: Product announcements and promotions
- Non-profits: Cost-effective donor communications
- Developers: API-driven email campaigns
¶ Maintenance Mode (2021-Present)
As of 2021, Mailtrain entered maintenance mode:
- Last major release (v2) was in June 2021
- Core development slowed significantly
- Community continues to use and maintain installations
- Some community forks and patches exist
¶ Why Maintenance Mode?
Several factors contributed to reduced development activity:
- Market saturation: Increased competition from specialized tools
- Complexity: Multi-service architecture (MySQL + MongoDB + Redis) increased maintenance burden
- Resource constraints: Limited core maintainer availability
- Shift to SaaS: Many users migrated to hosted alternatives
Despite reduced active development, Mailtrain contributed important innovations:
Mailtrain bundled Zone-MTA, an open-source MTA that allowed direct email delivery without relying on external SMTP providers. This was significant for:
- Cost reduction for high-volume senders
- Full control over email infrastructure
- Learning tool for email delivery protocols
Mailtrain’s user role system allowed agencies to:
- Manage multiple clients from one installation
- Restrict access by client/campaign
- Provide limited access to client users
As of 2026:
- Repository: Still available on GitHub (Mailtrain-org/mailtrain)
- Docker image: Official
mailtrain/mailtrain image maintained
- Installations: Thousands of active installations worldwide
- Support: Community support via GitHub issues
- Development: Minimal active development, bug fixes only
For new projects, consider these actively maintained alternatives:
- Listmonk: High-performance, simpler architecture (Go + PostgreSQL)
- Mautic: Full marketing automation suite
- Keila: Modern Elixir-based platform
- phpList: Long-established, actively maintained
Mailtrain’s history offers insights for self-hosted software:
- Architecture matters: Simpler stacks are easier to maintain long-term
- Community sustainability: Projects need multiple active maintainers
- Market timing: Open-source email tools face strong SaaS competition
- Documentation: Critical for community adoption and contribution