Connect PING8 To KumoMTA
Open Settings > KumoMTA to connect PING8 to your KumoMTA deployment.
Start disabled
Before saving production settings, keep sending disabled:
- Enabled: off or enabled for test only.
- Campaign sending: off.
- Send API: off.
Turn sending on only after the connection test passes.
Required fields
| Field | What to enter | Notes |
|---|---|---|
| Base URL | https://mta.yourdomain.com | HTTPS endpoint that PING8 can reach. |
| Injection path | /api/inject/v1 | Path exposed by your KumoMTA/proxy injection service. |
| Metrics URL | https://mta.yourdomain.com/metrics | Restrict access to trusted clients. |
| Default pool | default | Pool used when no sender-specific profile overrides it. |
| Auth mode | Bearer token or your configured proxy mode | Must match the injection gateway. |
| Request timeout | Start with 10s | Increase only if the network path is slow. |
| TLS verification | Enabled | Disable only for isolated temporary testing. |
| Auth secret | Stored secret value | Never paste secrets into docs, tickets, or screenshots. |
| Webhook secret | Shared event secret | Must match the KumoMTA webhook publisher. |
Save and test
- Enter configuration.
- Click Save changes.
- Click Test.
- Confirm injection and metrics health.
- Click Refresh to update runtime status.
Enable traffic
After tests pass:
- Enable Send API for one test send.
- Send to one owned mailbox.
- Confirm lifecycle events.
- Enable campaign sending.
- Launch a tiny test group.
What the Test button proves
The connection test should prove that PING8 can reach the configured endpoint, authenticate, and read expected health information. It does not prove that Gmail or another provider will accept a full campaign. Always follow it with a one-recipient send and lifecycle-event check.
Common mistakes
- Saving a base URL without TLS.
- Pointing metrics to a public endpoint with no access control.
- Enabling campaign sending before webhook events are visible.
- Using the KumoProxy hostname as the injection endpoint when the injection endpoint actually lives on the KumoMTA host.
- Rotating secrets in one system and forgetting to update the other.