Choose a WildDuck standalone or full mail-suite deployment

WildDuck itself provides IMAP, POP3, and HTTP API services. A complete mail suite adds inbound Haraka and outbound ZoneMTA; the standalone WildDuck image does not include those services automatically.

Still choosing a mailbox backend? See WildDuck in our Linux mail-server comparison.

Select and secure the topology

1. Follow the current installation guide for scripted, Compose, or standalone deployment.
2. Check the actual Node.js/MongoDB/Redis requirements for the chosen release and pin compatible components.
3. Configure persistent database/attachment storage and restrict internal network access.
4. If using the full suite, configure SMTP components and their integration credentials separately from WildDuck API/client listeners.

The current standalone documentation uses TLS IMAP/POP3 ports 9993/9995, while full-suite deployments may publish 993/995. Use the actual deployment’s ports and trusted certificate names, not a guessed universal setting.

Verify the selected services

Protect API access before allowing another host to reach it. Create one controlled account through the supported administration path and test mailbox login.

Then test incoming receipt and approved outbound sending only if their SMTP integrations are configured. A successful IMAP connection does not prove MX or outbound transport exists. Keep production DNS unchanged until the whole selected path and its recovery requirements are understood; do not expose MongoDB, Redis, or internal integration APIs as public mail interfaces.