MailWizz + PowerMTA Production Integration
Connect MailWizz to PowerMTA through authenticated or network-restricted submission with correct bounce handling.
Architecture
MailWizz generates campaign mail and submits it to PowerMTA. PowerMTA handles outbound delivery, while bounce servers, feedback loops and suppression controls return delivery intelligence to MailWizz.
Submission choice
Use SMTP authentication where possible. Network allowlisting may be appropriate on a private network, but should never become broad relay permission.
Separation
- Separate customers or traffic classes
- Use stable envelope-from domains
- Keep DKIM ownership explicit
- Map streams to intended VMTA or pool
- Apply provider-aware rates
- Process bounces and complaints quickly
MailWizz delivery server
Configure the actual PowerMTA submission host, port, encryption and credentials in MailWizz. Test with a mailbox you control before enabling campaigns.
Bounce processing
Use a dedicated return-path domain and validated bounce mailbox or webhook workflow. Verify that hard bounces, complaints and transient failures are classified correctly.
Cron and throughput
Campaign throughput depends on both MailWizz cron scheduling and PowerMTA acceptance/delivery capacity. Increasing cron frequency cannot solve provider throttling.
Go-live checklist
- SMTP test succeeds
- Envelope and header identities verified
- DKIM passes
- Bounce processing confirmed
- Feedback loops registered where available
- Suppression tested
- Per-provider monitoring enabled