Prompt
How do I debug why one specific email never arrived?
Latest observation
Nov 6, 2026
OpenAI APIWeb search: off
To debug why one specific email never arrived, treat it like tracing a message through a pipeline: sender → outbound mail server → recipient mail server → mailbox filters/folders. Here’s a practical checklist.
1) Confirm the basics
- Verify the exact recipient address was correct.
- Check whether the sender got a bounce / rejection / delivery failure message.
- Ask the sender whether the email was actually sent, and at what time/date.
- If possible, compare with a known-good test email sent to the same address.
2) Check the recipient side first
If it’s your mailbox:
- Look in:
- Spam/Junk
- All Mail / Archive
- Deleted/Trash
- Any custom folders or inbox rules
- Search by:
- sender address
- subject
- date/time window
- unique words from the email body
- Check mailbox rules/filters:
- Was it auto-sorted, deleted, or forwarded?
- If this is work email, ask IT whether there are:
- quarantine systems
- anti-phishing/anti-spam logs
- mail flow rules
3) Get the message headers or logs
If the email reached the recipient domain but not the inbox, headers can show where it went.
Ask the sender for:
- Full message headers
- Exact send time
- The Message-ID
If you administer the mail system, inspect:
- Mail server logs
- Queue logs
- Spam filter logs
- SMTP transaction logs
You’re looking for:
- accepted by recipient server
- rejected with a specific code
- quarantined
- delivered to a different folder
- delayed in queue
4) Interpret the SMTP result if there was one
Common clues:
550/551/553: address invalid, blocked, or policy rejection554: often spam/policy rejection421/451/452: temporary failure or throttling- No bounce at all: could be silent filtering, forwarding issue, or sender-side failure
5) Check domain reputation and authentication
If the email came from a domain or service that might trigger filtering:
- Confirm SPF, DKIM, and DMARC are valid
- Check whether the sending IP/domain is on a blocklist
- Review whether the email had suspicious content:
- attachments
- links
- image-only message
- unusual wording
6) Look for forwarding or alias problems
If the recipient address is an alias or group:
- Verify forwarding rules
- Make sure the alias expands correctly
- Check whether one member received it but others didn’t
7) Try to reproduce
Have the sender resend:
- same content
- then a plain-text version
- then a minimal test message with only “test” If only one version fails, the issue may be content-based filtering.
8) If you control the mail system, trace it end-to-end
Use tools/logs to answer:
- Did the message leave the sender?
- Did the remote server accept it?
- Was it quarantined?
- Was it delivered to another mailbox?
- Was it rejected after acceptance?
9) If the email was from a major provider
For Gmail/Outlook/Yahoo/etc.:
- Check spam/quarantine
- Search all mail
- Verify the sender wasn’t blocked
- Review security notifications
- In corporate accounts, check admin quarantine and message trace
10) What to ask the sender for
Ask for:
- exact recipient address
- send time and timezone
- subject line
- full headers
- bounce message, if any
- whether they used a mailing service or personal mailbox
If you want, I can give you a step-by-step troubleshooting flow for:
- personal Gmail/Outlook,
- corporate Microsoft 365 / Google Workspace, or
- your own mail server.