The frontend can spend more time on large message lists, previews and uploads.
Power users with large mailboxes.Configuration matérielle requise pour SnappyMail : RAM, CPU, PHP et serveur de messagerie en arrière-plan
Planifiez le matériel SnappyMail pour PHP, IMAP, SMTP, les données persistantes et Docker, avec des recommandations pratiques d’installation personnalisée de ZimaOS pour le webmail.
SnappyMail requirements at a glance
SnappyMail is a webmail frontend, so the IMAP/SMTP server normally consumes far more resources than the frontend itself.
- RAM
- No numerical official server RAM minimum published. SnappyMail is explicitly positioned as lightweight.
- CPU
- No numerical official core minimum. Normal webmail frontend use is light.
- PHP
- Current project requirements specify PHP 7.4 or newer; the maintained project Dockerfile currently uses PHP 8.2 FPM on Alpine.
- Database
- No database is required for core SnappyMail use; optional plugins or address-book integrations can add database dependencies.
- Mail backend
- SnappyMail depends on IMAP and SMTP services for actual mailbox access and message delivery.
- Best Zima starting point
- ZimaBoard 2 832 is far more than enough for SnappyMail; size larger hardware for the co-located mail server, not the webmail frontend.
From official requirements to the right setup
Treat SnappyMail as a lightweight PHP frontend to an existing mail backend.
-
Official requirements
Use the official SnappyMail container or a PHP 7.4+ web-server environment; the project Dockerfile currently packages PHP 8.2 FPM.
-
Confirm your needs
Configure IMAP and SMTP endpoints separately. Do not treat mailbox storage, spam filtering or SMTP queues as SnappyMail's own hardware requirement.
-
Leave room to grow
Persist /var/lib/snappymail when using the official container so application data and configuration survive container recreation.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with the official GHCR image, map port 8888 for the web UI, and place the service behind HTTPS.
Check every playback client
- PHP runtime
- IMAP server
- SMTP server
- Persistent data volume
- HTTPS
- Optional plugins
- Address-book DB needs
- Other mail services
Official minimum requirements
SnappyMail publishes software/container requirements rather than numerical whole-host hardware minimums.
Do not invent RAM or CPU numbers. Core SnappyMail needs no database and is lightweight; the actual mail server is a separate infrastructure layer.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM minimum | No numerical official minimum published | Project describes SnappyMail as lightweight. |
| CPU minimum | No numerical official minimum published | Normal webmail frontend use is light. |
| PHP minimum | 7.4+ | Current project README requirement. |
| Current Docker PHP | PHP 8.2 FPM | Current official project Dockerfile. |
| Database | Not required for core use | Optional integrations may add DB dependencies. |
| Container ports | 8888 and 9000 | Current project Dockerfile exposes web and PHP-FPM ports. |
When to upgrade your hardware
SnappyMail rarely needs hardware upgrades on its own; scale when the broader mail stack or plugins become heavier.
Large mailboxes and attachment workflows grow
Plugins and integrations expand
The mail server shares the host
Contacts, SSO and other extensions can add PHP and external-service work.
Customized installations.IMAP, SMTP, spam filtering and mailbox storage can dominate CPU, RAM and disk.
All-in-one mail systems.Plan hardware growth with confidence
Scale the actual mail platform rather than SnappyMail itself.
Keep SnappyMail on ZimaBoard 2 832
The webmail frontend is lightweight and does not justify high-end hardware.
ZimaBoard 2 832.Persist application data on durable storage
Keep /var/lib/snappymail outside the disposable container filesystem.
Any Zima SATA/NVMe-backed app storage.Use 16 GB when the full mail server is co-located
Extra RAM is for IMAP/SMTP/filtering/database services.
ZimaBoard 2 1664.Use ZimaCube for mailbox retention
Large local mailboxes and backups may justify multi-drive capacity.
ZimaCube 2 Standard.Can it run on ZimaOS?
No public official ZimaOS one-click SnappyMail App Store page was verified for this guide. SnappyMail can be deployed through Install Custom App using its official project container.
Custom install SnappyMail in ZimaOS
Use Install Custom App with ghcr.io/the-djmaze/snappymail, persist /var/lib/snappymail and map port 8888 to an available host port.
Custom install SnappyMail in the ZimaOS app ↗Use SnappyMail's maintained container
The project publishes a GHCR image and packages nginx plus PHP-FPM in the container.
Review SnappyMail container package ↗Keep the mail backend separate in sizing
SnappyMail is a webmail client and depends on IMAP/SMTP services for mailbox access and delivery.
Review SnappyMail project ↗Choose Zima hardware for SnappyMail
SnappyMail itself is extremely light; hardware choice should follow the mail server if it runs on the same device.
Is SnappyMail only a frontend or part of an all-in-one mail host?
Frontend to an external mail server
Use ZimaBoard 2 832; SnappyMail needs very little compute.
- Best starting pointZimaBoard 2 832
Full mail stack on one host
Add RAM and storage for mail services rather than the frontend.
- More mail-stack headroomZimaBoard 2 1664
- Mailbox-storage platformZimaCube 2 Standard
These recommendations cover the SnappyMail frontend, not the independent IMAP/SMTP infrastructure.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | SnappyMail with external IMAP/SMTP. | Webmail frontend and persistent app configuration. |
|
Far more compute than SnappyMail alone requires. | Get Now |
| ZimaBoard 2 1664 | SnappyMail on a broader mail host. | Webmail plus IMAP/SMTP, filtering and other services. |
|
Extra RAM is for the mail stack. | Get Now |
| ZimaCube 2 Standard | Mailbox-heavy local mail systems. | SnappyMail plus large mailbox retention and backups. |
|
Choose it for storage rather than frontend compute. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
These answers cover SnappyMail RAM, CPU, PHP, database needs, mail backend and ZimaOS deployment.
How much RAM does SnappyMail need?
SnappyMail does not publish a numerical official server RAM minimum.
How many CPU cores does SnappyMail need?
No numerical official core minimum is published.
Which PHP version does SnappyMail require?
The current project README requires PHP 7.4 or newer; its maintained Dockerfile currently uses PHP 8.2 FPM.
Does SnappyMail require a database?
No database is required for core SnappyMail operation.
Does SnappyMail include IMAP or SMTP?
No. It is a webmail client and connects to existing IMAP and SMTP services.
Does SnappyMail need a GPU?
No dedicated GPU is required.
Can ZimaBoard 2 run SnappyMail?
Yes. The 8 GB model is far more than enough for the frontend.
When should I choose larger Zima hardware?
When the co-located mail server, mailbox storage or other services need more RAM or drives.
What sources informed this SnappyMail hardware guide?
Current SnappyMail repository, container package and Dockerfile plus current Zima product pages.
