STAMPWING / MISSING EMAIL TRIAGE
Last reviewed: October 4, 2026

1. Identify the logical event and exact recipient. Record request/message IDs,
   UTC timestamps and environment. Do not paste credentials or reset tokens.
2. No API result? Check validation/authentication and your durable outbox.
3. Queued? Check worker health, age, pauses, and limits.
4. Submitted/unknown? Check provider events. Do not blindly resend.
5. Rejected/bounced? Read the SMTP response and suppression reason. Resolve the
   cause; do not bypass complaints or repeatedly retry permanent failures.
6. Accepted by receiving server? Search spam/quarantine/rules; ask the recipient
   administrator for a message trace using Message-ID and acceptance timestamp.
7. Header available? Read receiver-added Authentication-Results; distinguish
   authentication from inbox placement. Remove private data before sharing.
8. Close with evidence: what was observed, what remains unknown, next action,
   owner and next check time. Never label an unknown outcome as delivered.

Support handoff:
Environment:
Application event ID:
Provider/message ID:
Recipient (redact for public sharing):
UTC send/acceptance times:
Last observed status and SMTP response:
Actions already taken:
Next action and owner: