Policy Preview And Dry Run

The Policy Preview area lets operators inspect generated KumoMTA policy output before changing runtime behavior.

Controls

• Preview config: generate and inspect current policy output.
• Dry run deploy: validate the selected preview without mutating KumoMTA.

What to review

• Alerts.
• Warnings.
• Generated version.
• File list.
• Pool and source references.
• DKIM signing assumptions.
• Webhook configuration.

Review questions

• Does every referenced pool exist?
• Does the default pool match the PING8 tenant default?
• Are sender domains mapped to the intended signing keys?
• Are webhook settings present and protected by the expected secret?
• Are any warnings acceptable for a test environment but unsafe for production?

Safe workflow

1. Preview config.
2. Read alerts and warnings.
3. Fix configuration issues.
4. Run dry run deploy.
5. Record the version.
6. Deploy through your approved operations path.

Do not skip dry run

Dry run catches configuration errors before traffic depends on the policy.

Change control

For production:

1. Save the preview version identifier or timestamp.
2. Record what changed and why.
3. Run dry run.
4. Deploy during a low-volume window.
5. Send one owned test email.
6. Watch runtime metrics and webhook events before resuming campaigns.