MailWizz Multi-Server Setup — Separating Web Frontend, Queue Workers, and Database

A single-server MailWizz installation limits scalability — the web frontend, campaign processing, and database compete for the same resources. Splitting these functions across dedicated servers enables each component to scale independently.

Architecture: Three Server Roles

• Web Frontend Server(s): Handles the admin and subscriber-facing application, API requests, and tracking pixel/click redirect requests
• Queue Worker Server(s): Runs only the campaign sending daemon and cron jobs — no web server required
• Database Server: Dedicated MySQL/MariaDB instance with no other workloads

Shared Filesystem Requirement

MailWizz's apps/common/runtime/ and apps/frontend/runtime/ directories must be writable and shared across all application servers. Use NFS or a cloud-native shared storage mount. The queue workers and web frontend must read/write the same runtime directory.

# /etc/fstab on all application servers
# Mount shared storage
nfs-server:/var/mailwizz-shared /var/www/mailwizz/apps/common/runtime nfs defaults 0 0

Queue Worker Server Configuration

# The queue worker server needs:
# 1. PHP-CLI with all required extensions
# 2. Access to the shared runtime filesystem
# 3. Access to the database server
# 4. Supervisord for daemon management

# /etc/supervisor/conf.d/mailwizz.conf
[program:mwz-queue]
command=php -q /var/www/mailwizz/apps/console/console.php campaigns-queue
user=www-data
autostart=true
autorestart=true
numprocs=4

Database Server Configuration

# Grant MailWizz app servers access
CREATE USER 'mailwizz'@'10.0.1.0/255.255.255.0' IDENTIFIED BY 'password';
GRANT ALL PRIVILEGES ON mailwizz.* TO 'mailwizz'@'10.0.1.0/255.255.255.0';

# Bind MySQL to private network interface
# /etc/mysql/mysql.conf.d/mysqld.cnf
bind-address = 10.0.1.10

Troubleshooting Common Issues

Production MailWizz deployments encounter predictable issues at predictable stages. Understanding the diagnostic workflow for the most common problems in this configuration area saves time and prevents the escalating complexity that comes from applying fixes to a misdiagnosed problem. The diagnostic approach is always the same: identify the symptom precisely (not just "it's not working"), isolate the layer where the failure occurs (MailWizz application, delivery server connection, DNS, ISP rejection), and fix at the correct layer.

Systematic Diagnosis Approach

Check MailWizz logs first (available in Backend → Misc → Application Logs), then check the delivery server SMTP logs, then check the PowerMTA accounting log. Most issues surface in one of these three places. A problem that does not appear in any of these logs is almost always a configuration issue — the system is not attempting what you expect it to attempt.

# MailWizz diagnostic log locations:
# Application logs: Backend → Misc → Application Logs
# Delivery logs: Backend → Campaigns → [Campaign] → Delivery Logs
# Bounce logs: Backend → Bounce Servers → [Server] → Logs

# Server-side logs:
# MailWizz application: /path/to/mailwizz/apps/common/runtime/application.log
# PowerMTA delivery: /var/log/pmta/pmta.log
# PowerMTA accounting: /var/log/pmta/accounting.csv

Performance Optimization for Production Scale

MailWizz performance at scale depends on three infrastructure layers: the web application server (PHP/nginx or Apache), the database (MySQL — query optimization is critical at high subscriber counts), and the delivery infrastructure (PowerMTA connection pool sizing). Performance problems in any of these layers manifest as slow campaign sends, delayed processing, or timeouts that appear unrelated to the specific configuration area being managed.

The most common performance constraint in production MailWizz environments is MySQL query efficiency. As subscriber lists grow beyond 500,000 records, unoptimized database queries for segmentation, bounce processing configuration, and campaign statistics become significant bottlenecks. Ensure that subscriber tables have appropriate indexes on email, status, date_added, and any custom field columns used for segmentation.

# MySQL optimization for large MailWizz installations
# Check slow query log:
SHOW VARIABLES LIKE 'slow_query_log%';
SET GLOBAL slow_query_log = 'ON';
SET GLOBAL long_query_time = 1;  # Log queries over 1 second

# Key indexes to verify exist:
SHOW INDEX FROM mailwizz_lists_subscribers;
# Should have indexes on: email, status, date_added, list_id

# Add missing index if needed:
ALTER TABLE mailwizz_lists_subscribers 
  ADD INDEX idx_email_status (email, status);
  
# Campaign sends table — index on campaign_id + subscriber_id:
ALTER TABLE mailwizz_campaigns_tracking_opens
  ADD INDEX idx_campaign_sub (campaign_id, subscriber_id);

Security Considerations

MailWizz installations handling production sending volumes are valuable targets. Key security practices: use HTTPS for all MailWizz access (including tracking and unsubscribe links), restrict Backend access to authorized IP ranges via web server configuration, rotate API keys periodically and revoke unused keys, maintain regular database backups (automated, offsite), and ensure PHP and MailWizz are kept current with security patches.

The tracking domain (used for open and click tracking) requires special attention: it must have a valid SSL certificate (Let's Encrypt is acceptable), and its DNS records must point exclusively to your MailWizz server. A compromised tracking domain can redirect recipients to malicious sites or reveal subscriber click data to third parties.

Campaign Analytics Integration

Track this MailWizz configuration area through two complementary metric layers: MailWizz campaign statistics (open rate, click rate, bounce rate, unsubscribe rate) and PowerMTA accounting log data (ISP-specific deferral rate, bounce classification, queue depth). Gaps between the two layers reveal delivery problems invisible to MailWizz statistics alone — high MailWizz "sent" counts with elevated PowerMTA deferral rates indicate a queue buildup that campaign dashboards don't surface.

Review campaign metrics against your own historical baselines rather than industry benchmarks. Your list composition, acquisition source, and engagement history define what normal looks like for your environment. Use rolling 7-day and 30-day averages to distinguish trend changes from campaign-specific variance.

Implementation Checklist

Before deploying this configuration to production MailWizz, verify: delivery server connection test passes in Backend → Servers → Delivery Servers, cron jobs are running on the correct schedule, bounce server mailbox is accessible and IMAP credentials are valid, tracking domain has valid SSL and loads within 500ms, and PHP memory limit is set to at least 256MB.

After deploying, send a test campaign to a controlled list of seed addresses across Gmail, Outlook, and Yahoo. Verify Authentication-Results headers show dkim=pass and spf=pass in the received messages. Check that open and click tracking are registering correctly in MailWizz statistics. Confirm bounce processing is updating subscriber status within 15 minutes of a test bounce event.

For managed MailWizz environments operated by Cloud Server for Email, these verification steps are performed automatically after any configuration change. The managed service includes continuous monitoring of delivery server health, cron job execution, and tracking domain availability. Contact infrastructure@cloudserverforemail.com for information about managed MailWizz hosting.

Multi-Server Shared State Management

MailWizz multi-server setups share the database layer. File storage (uploads, exports) must be network-accessible to all nodes via NFS or S3-mounted storage. Session handling requires a shared backend — Redis or database sessions, not file-based sessions. Load balancer sticky sessions are a simpler alternative to shared session storage for environments where session sharing is complex to implement.

Campaign Distribution Across Nodes

In a multi-server MailWizz deployment, configure each node to handle different campaign segments to prevent duplicate processing. Use MailWizz's built-in locking mechanism (semaphores) — don't disable it. Monitor campaign processing logs from all nodes in a centralized system to detect conflicting operations across nodes.