Mailcow in Production: Experience, Backup Strategy & High Availability

abdullah0samy

Hi everyone,

I’m planning to deploy Mailcow in a production environment as an email service provider, and I’d really appreciate insights from people who have already gone through this journey.

I have a few key areas I’d like to understand better:

🔹 Real-world experience

Has anyone here built a business or service using Mailcow?
How stable has it been in production over time?
Did you face any major issues (performance, crashes, deliverability, etc.)?

🔹 High availability & reliability

What architecture are you using to achieve high availability?
Are you running multiple Mailcow instances, backup MX, or load balancing?
Any recommendations to avoid single points of failure?

🔹 Security & protection

What are the must-have measures to protect:
- the server itself
- client mailboxes
- outbound abuse (spam from compromised accounts)?
Are you using additional tools like gateways or intrusion prevention systems?

🔹 Backup strategy (very important for me)
From what I understand, Mailcow does not provide native incremental backups out of the box.

What is your recommended approach for incremental backups?
- Borg/Borgmatic, rsync snapshots, Veeam, or something else?
Do you perform:
- cold backups (stopping containers)
- or hot backups? How do you ensure consistency?
What exactly are you backing up?
- Full mailcow-dockerized directory
- or specific volumes (vmail, mysql, etc.)?
What retention policy are you using?
- (daily / weekly / monthly)
How often do you test restores?
- Full restore vs single mailbox restore?

🔹 Monitoring & management

What tools are you using for monitoring (system + mail flow)?
Any GUI-based backup or monitoring solutions you recommend?

My goal is to build a stable, secure, and scalable email hosting service from the beginning, so I’m trying to avoid common mistakes and follow best practices.

Thanks a lot in advance for sharing your experience!

esackbauer

abdullah0samy

Running mailcow on a high available proxmox cluster solves for most parts the load balancing/HA topics. One mailcow installation is not suited for hosting thousands of mailboxes.
For backup then Proxmox backup server or Veeam solves most parts, and can do snapshot based backups.

Other than that I would recommend talking to the folks of servercow.de, they can help you probably more with real world business examples and proper commercial support.

ETNyx

Hi,

Mailcow is more o less designed as single-node solution, good for small hosting, self-hosting. So if you really want highly scalable, and HA solution, I do not think MC is for you.

abdullah0samy

esackbauer

Hi everyone,

Thanks a lot for your insights so far, really helpful.

To give more context, I’m currently building a small startup focused on providing email hosting services. At the moment, I only have around 4 clients, each with roughly 20 mailboxes and ₂₀ GB storage per client — so still a small-scale setup.

My main goal is to start with a stable, secure, and cost-efficient (open-source) solution, and then scale gradually over time as the business grows.

From your experience:

Do you think Mailcow is a good fit for this stage and can scale reasonably for small-to-medium growth?
Or would you recommend a different open-source solution that is more suitable for a growing email hosting business?

I’m also considering whether using a control panel that combines web hosting + email (instead of a dedicated mail stack) is a better approach, but I’m concerned about security, deliverability, and long-term stability.

If you have real-world experience running a similar setup (even small scale), I’d really appreciate your recommendations.

Thanks again!

Ganzjahresgriller

I am a great Fan of MC but in this case i would watch https://stalw.art

shlomi

I built myself an SMTP service on mailcow. Works great.