Sending Infrastructure
PING8 supports several delivery paths. Choose the simplest path that meets your volume, control, and deliverability needs.
Delivery engine options
| Engine | Best for | Notes |
|---|---|---|
| Local Postfix | Low-volume self-hosted tests and mailbox-driven sending | Requires working server DNS, PTR, and open outbound mail ports. |
| External SMTP | Teams already using Gmail, SES, SendGrid, Mailgun, or another SMTP provider | Useful for controlled migration or backup paths. |
| KumoMTA | High-volume outbound mail with lifecycle telemetry | Requires a healthy KumoMTA host and PING8 connection settings. |
| Tenant default | Production default after configuration | Lets administrators choose the tenant-level engine/profile while users send normally. |
Recommended progression
- Verify your domain and DNS.
- Send a low-volume test through the simplest available engine.
- Configure KumoMTA only when the domain path is healthy.
- Set tenant default after the KumoMTA connection and event flow are working.
- Run one-recipient smoke tests before group campaigns.
What to monitor
- DNS verification status.
- Queue size and oldest queue age.
- Message lifecycle states: queued, accepted, delivered, deferred, bounced, expired, complained.
- Provider-level bounce or deferral patterns.
- Webhook/event ingestion health.
Common mistakes
- Sending from a domain before SPF/DKIM/DMARC verify.
- Treating task progress as final delivery.
- Sending to a large list before one-recipient smoke tests pass.
- Enabling tracking without updating privacy notices.
- Using KumoMTA before the webhook path is confirmed.