Troubleshooting intake and delivery
Use the receipt ID to find a stored message, the event ID to correlate webhook retries, and the attempt ID to investigate one HTTP request.
Wildmail parses and stores the email before SMTP acceptance, then prepares webhook delivery. A successful SMTP response confirms storage, not successful webhook delivery.
| Symptom | Check | Next action |
|---|---|---|
| Domain is not ready | TXT ownership, MX destination, endpoint, plan and billing | Correct DNS or configuration and run Check DNS again. Exact-address routes can work without a catch-all, see routing behavior. |
SMTP 550 at recipient admission | Unknown address, unready domain, inactive or suspended route | Confirm the exact receiving address and domain status. |
SMTP 451 at admission | Monthly allowance, storage quota, rate limits, temporary service availability | Check account usage. Allow normal sender retries. Contact support if failures persist. |
SMTP 552 for message size | Entire raw email size, including headers and encoded attachments | Reduce the message size to fit your plan. Retrying the unchanged email will not resolve it. |
| SMTP succeeds but no webhook arrives | Delivery status, next retry time, attempts and current endpoint status | Inspect Deliveries. Allow the bounded retry window to run. Contact support with the receipt ID and event ID if it remains pending. |
| Webhook signature fails | Raw body capture, signing-key version, header names and clock skew | Follow the verification example. Verify before parsing or reserializing the JSON. |
HTTP 401 or 403 in delivery attempts | Your receiver's authentication or verification policy | Fix receiver credentials or signature verification, then replay while the message remains available. |
HTTP 429 or 5xx | Receiver capacity or outage | Restore receiver capacity. Positive-retention mail retries within the bounded window. A 0-day message gets at most one attempt. |
| Redirect response | Endpoint URL redirects to a different host or path | Configure the final HTTPS URL. Wildmail does not follow redirects. |
| Raw message or attachment unavailable | Current account retention, message expiry and API-key scope | Retrieve retained content before expiry. At 0 days, attachment bytes are available inline in the webhook event only. |
Replay returns 409 | Attempt in progress, endpoint paused, signing key unavailable or mapping invalid | Follow the returned error. Wait for an active attempt or correct the endpoint or mapping. A failed render cannot be repaired by replaying the same pinned mapping. |
Replay returns 410 | Content expired or the message uses 0-day retention | Use content already stored by your application. Expired and 0-day messages cannot be replayed. |
Intake failures
Malformed email, size limits, recipient routing, or temporary service failures can cause SMTP to reject a message. The sending mail server should retry temporary 4xx responses. A rejected message has no webhook delivery to replay.
Delivery failures
Wildmail sends the signed event using the endpoint and payload mapping selected when the email was accepted. An expired message, unavailable endpoint revision, or invalid mapping can stop delivery. The delivery detail page shows content-free attempt results and the latest safe error code. Contact Wildmail support with the receipt ID and event ID if a message stays pending beyond its delivery window.
Send test checks endpoint connectivity and signature verification with a synthetic event. Send a real email to your receiving address to verify SMTP intake, email parsing, message access, and attachment handling.