MailWizz Cron Jobs Configuration — Complete Setup for Campaign Sending and Queue Processing

MailWizz's campaign sending, bounce processing configuration, and maintenance tasks are all triggered by cron jobs. Incorrect cron configuration is one of the most common causes of campaigns not sending, bounces not processing, or lists not cleaning up.

Required Cron Jobs

# Add to crontab for www-data user: crontab -u www-data -e

# Send campaigns (run every minute)
* * * * * php -q /var/www/mailwizz/apps/console/console.php send-campaigns >> /dev/null 2>&1

# Process bounces (every 10 minutes)
*/10 * * * * php -q /var/www/mailwizz/apps/console/console.php process-delivery-and-bounce-log >> /dev/null 2>&1

# Process feedback loops (every hour)
0 * * * * php -q /var/www/mailwizz/apps/console/console.php process-feedback-loop-email >> /dev/null 2>&1

# Clean up (daily)
0 2 * * * php -q /var/www/mailwizz/apps/console/console.php lists-clean-up >> /dev/null 2>&1

# Delete campaign delivery logs (weekly archival)
0 3 * * 0 php -q /var/www/mailwizz/apps/console/console.php delete-campaign-delivery-logs >> /dev/null 2>&1

Running as the Correct User

All cron jobs must run as the same user that owns the MailWizz files (typically www-data or nginx). Running as root creates files with incorrect ownership that the web server cannot read, causing permission errors on subsequent runs.

Supervisord for the Campaign Daemon

# /etc/supervisor/conf.d/mailwizz-daemon.conf
[program:mailwizz-daemon]
command=php -q /var/www/mailwizz/apps/console/console.php campaigns-queue
user=www-data
autostart=true
autorestart=true
stdout_logfile=/var/log/mailwizz/daemon.log
stderr_logfile=/var/log/mailwizz/daemon-error.log
numprocs=1

# Start
supervisorctl reread && supervisorctl update && supervisorctl start mailwizz-daemon

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, 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.

Cron Configuration for High-Throughput Sending

The default MailWizz cron runs one worker per execution minute. For campaigns above 100,000 subscribers, configure parallel workers: add 3–5 separate cron entries for send-campaigns.php with --campaigns-limit parameters to distribute load. Monitor worker execution times — if any worker runs longer than its interval, tasks pile up and create memory exhaustion within hours.

Critical Crons to Monitor

The three most operationally critical crons are: send-campaigns.php (delivery throughput), bounce-handler.php (list hygiene automation), and process-delivery-bounces.php (suppression sync). A stopped bounce-handler means hard bounces accumulate without suppression — check all three run successfully at least every 30 minutes during active campaigns.