✉PowerMTA.inEmail Infrastructure & Deliverability
LATESTGmail Sender RequirementsSMTP TLS ExplainedPTR & Reverse DNSDeliverability ChecklistAuthentication Troubleshooting
SELF-HOSTED EMAIL SOFTWARE

Self-hosted email infrastructure installation guides

By Abhishek Sharma · Published 2026-08-21 · Last reviewed 2026-08-21

Step-by-step installation guides for MailWizz, Sendy and Acelle Mail on Ubuntu VPS, cPanel, Caddy and Docker, with HTTPS, cron, databases and delivery setup.

How to use this hub: Start with the VPS or cPanel guide if you want the simplest path. Use Caddy when you specifically want its reverse-proxy and automatic HTTPS workflow. Use Docker when you already understand persistent volumes, container networking, backups and upgrades. Each guide distinguishes vendor-documented steps from adapted infrastructure patterns.
MAILWIZZ

MailWizz installation guides

Choose the hosting method that matches your infrastructure experience and operational requirements.

Primary deployment guide

Install MailWizz on Ubuntu VPS with PHP, database, HTTPS and scheduled jobs. This is the primary production deployment guide; adapt the application layer to your hosting stack as needed.

Read the MailWizz deployment guide →
SENDY

Sendy installation guides

Choose the hosting method that matches your infrastructure experience and operational requirements.

Primary deployment guide

Install Sendy on Ubuntu VPS, connect the application to Amazon SES, configure HTTPS, database access and cron, and verify the production workflow.

Read the Sendy deployment guide →
ACELLE MAIL

Acelle Mail installation guides

Choose the hosting method that matches your infrastructure experience and operational requirements.

Primary deployment guide

Install Acelle Mail on Ubuntu VPS with PHP, database, web-server routing, HTTPS and the background services required for a production deployment.

Read the Acelle Mail deployment guide →

Build the application layer first.

MailWizz, Sendy and Acelle Mail manage campaigns and subscribers; your delivery provider or MTA still determines how messages leave the server. Continue with SPF, DKIM, DMARC and deliverability guides after installation.

Read deliverability checklist