MailWizz Inbox Placement Testing — Tools and Methods for Verifying Gmail and Outlook Inbox Landing

Inbox placement testing verifies whether campaigns sent through MailWizz are arriving in the inbox, the spam folder, or not being delivered at all. This verification is distinct from delivery rate — a message can be delivered to Gmail and still land in the spam folder.

Seed-List Inbox Placement Testing

Seed-list tools (GlockApps, Mail-tester.com, Litmus Email Analytics) provide email addresses at major ISPs that are used exclusively as test recipients. Sending a campaign to these seed addresses and checking the results shows inbox vs. spam placement before sending to the full list.

# Simple inbox placement test workflow:
# 1. Add seed addresses to MailWizz as test subscribers
# 2. Send the campaign to the seed list only
# 3. Check results in the testing tool dashboard
# 4. Verify Gmail, Outlook, Yahoo, and relevant regional ISPs separately

Manual Testing at Gmail

# Create test Gmail accounts for each sending scenario:
# - A fresh account with no sending history to it (cold relationship)
# - An account that has previously opened emails from this sender
# - An account that has never interacted with any email from this sender

# Send to all three and compare inbox placement
# Engaged-recipient accounts should inbox; cold accounts test ISP filtering

Interpreting Inbox Placement Test Results

• Inbox at all ISPs: Authentication correct, content clean, reputation positive
• Spam at Gmail only: Gmail domain reputation issue — check Google Postmaster Tools integration spam rate
• Spam at Outlook only: IP or domain reputation with Microsoft — check Microsoft SNDS
• Spam at all ISPs: Content triggering spam filters — test with simplified HTML content
• Not delivered: IP or domain blacklisted — check blacklist detection and delisting status immediately

Content-Specific Spam Testing

# Use mail-tester.com for content analysis
# Send a campaign test message to the provided address
# Review score and specific issues flagged:
# - Authentication failures
# - URL blacklist hits on tracking domain
# - HTML spam triggers
# - Missing or broken unsubscribe link

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.

Integrating Inbox Placement Tests with MailWizz Workflow

Seed-list-based inbox placement testing (GlockApps, MailGenius, EmailOnAcid) requires sending to a set of seed addresses before the full campaign. In MailWizz, create a dedicated test list with seed addresses. Send the test campaign, review placement results, address any inbox placement issues, then send the production campaign. This workflow adds 30-60 minutes to the campaign cycle but prevents deliverability surprises at scale.

Content Scoring Tools

Content scoring tools (mail-tester.com, SpamAssassin score checking) evaluate message content against spam filter rules. High content scores indicate elements that trigger ISP content filters. Common triggers: excessive punctuation in subject lines, all-caps words, specific phrases associated with spam. Run content scoring on every new template before first use in production.