Skip to main content

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.

SymptomCheckNext action
Domain is not readyTXT ownership, MX destination, endpoint, plan and billingCorrect DNS or configuration and run Check DNS again. Exact-address routes can work without a catch-all, see routing behavior.
SMTP 550 at recipient admissionUnknown address, unready domain, inactive or suspended routeConfirm the exact receiving address and domain status.
SMTP 451 at admissionMonthly allowance, storage quota, rate limits, temporary service availabilityCheck account usage. Allow normal sender retries. Contact support if failures persist.
SMTP 552 for message sizeEntire raw email size, including headers and encoded attachmentsReduce the message size to fit your plan. Retrying the unchanged email will not resolve it.
SMTP succeeds but no webhook arrivesDelivery status, next retry time, attempts and current endpoint statusInspect Deliveries. Allow the bounded retry window to run. Contact support with the receipt ID and event ID if it remains pending.
Webhook signature failsRaw body capture, signing-key version, header names and clock skewFollow the verification example. Verify before parsing or reserializing the JSON.
HTTP 401 or 403 in delivery attemptsYour receiver's authentication or verification policyFix receiver credentials or signature verification, then replay while the message remains available.
HTTP 429 or 5xxReceiver capacity or outageRestore receiver capacity. Positive-retention mail retries within the bounded window. A 0-day message gets at most one attempt.
Redirect responseEndpoint URL redirects to a different host or pathConfigure the final HTTPS URL. Wildmail does not follow redirects.
Raw message or attachment unavailableCurrent account retention, message expiry and API-key scopeRetrieve retained content before expiry. At 0 days, attachment bytes are available inline in the webhook event only.
Replay returns 409Attempt in progress, endpoint paused, signing key unavailable or mapping invalidFollow 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 410Content expired or the message uses 0-day retentionUse 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.