Webhooks And Lifecycle Events
PING8 relies on KumoMTA lifecycle events to show delivery telemetry.
Events PING8 expects
- Accepted or queued.
- Delivered.
- Deferred.
- Bounced.
- Expired.
- Complained.
- Suppressed when applicable.
Why events matter
Campaign progress only means PING8 attempted recipients. Delivery telemetry comes from lifecycle events.
Without events, a task can look attempted while delivered, bounced, and deferred counts remain incomplete.
Webhook checklist
- KumoMTA can reach the PING8 event endpoint.
- The webhook secret matches PING8 configuration.
- TLS is valid.
- Firewalls allow the request.
- PING8 logs accepted webhook events.
- Duplicate events are deduplicated, not counted as new delivery.
Event durability
Webhook delivery should be treated as part of the mail pipeline. If events are delayed, PING8 may show attempted progress while delivered, deferred, or bounced counts remain incomplete. Investigate event delivery before rerunning campaigns.
Test flow
- Send one message through KumoMTA.
- Confirm KumoMTA logs the injection.
- Confirm a lifecycle event is posted.
- Confirm PING8 updates the task or API log.
- Only then test a group send.
Troubleshooting event gaps
| Symptom | Likely cause | First action |
|---|---|---|
| KumoMTA accepts message, PING8 stays queued | Webhook not reaching PING8 | Check event endpoint reachability and logs. |
| Security failure count rises | Secret mismatch | Rotate or re-enter the shared webhook secret on both sides. |
| Duplicate count rises | Retries or replay | Confirm dedupe behavior and provider/network stability. |
| Provider details missing | Event mapping issue | Compare raw KumoMTA event with PING8 failure details. |