When one email goes missing, it is tempting to resend it immediately or assume the recipient never received it. First, gather a few details and follow the same sequence each time. That helps separate a simple address or filtering issue from a delay or a problem that needs an administrator’s attention. It also sets a useful limit: a sent message, delivery notice, or header can offer clues about handling, but none alone proves that the message reached the recipient’s inbox or was seen.
The useful bits
- Confirm the exact recipient address and send time before resending.
- Ask the recipient to search other folders and check relevant filters.
- Use bounces and matching headers as clues, then escalate with a concise record.
Start with the exact message and destination
Find the original message in Sent or the relevant conversation. Record the recipient exactly as it appears in the To, Cc, or Bcc field, along with the date, time, and time zone shown by your mail service. Check for a misspelled letter, an outdated address, an unintended alias, or a recipient selected from autocomplete. If there were several recipients, identify which person is missing the message.
Confirm what you actually sent. A message may have remained a draft, gone to a different address, or been sent without the attachment or details you intended. Keep the subject line and approximate send time handy; they can help the recipient search without asking you to forward sensitive content.
Recipient checked: [name] <[person@example.com]> Subject: [subject] Sent: [date and time, including time zone] Expected attachment or detail: [brief description]
Look for a bounce or a delay before resending
Check your inbox and other folders for a delivery failure, rejection, or delay notice related to the message. Search using the recipient address, subject, and send time. Read the notice for the affected address and any explanation it provides. A bounce generally indicates that delivery was refused or could not be completed as described in that notice; a delay notice indicates that delivery is still being attempted or that the status is not yet final.
No notice is not confirmation of successful inbox delivery. Notices can be absent, delayed, or limited in what they explain. Avoid sending repeated copies while the status is unclear: duplicates can confuse the recipient. If the message is time-sensitive, send a brief separate note through an appropriate channel to ask whether it arrived, rather than treating the original as confirmed.
Ask the recipient to search beyond the inbox
Ask the recipient to search all mail, not just the visible inbox. Useful search details include your full sending address, the subject, and a narrow time window. They can also inspect spam or junk, archive, deleted items, and any folders where their mail service sorts messages. Folder names and search behavior vary by provider.
If the message appears in another folder, ask the recipient to check any rule or filter that might have moved it. A filter can route mail based on sender, subject, or other conditions. The recipient should review the rule before changing it, especially if it handles other messages too. If no match appears, ask them to verify the address they expected and whether they can receive other mail at that address.
Use headers as clues, not a receipt
If the message is available in Sent or the recipient can locate a related copy, compare the full message headers when both services make them available. Check that the sender, recipient, subject, and time correspond to the message in question. A Message-ID can help distinguish one message from another. Received lines may show systems that handled the message along its route.
Interpret those details cautiously. Header formats and visibility differ, and a line naming a receiving system does not establish that the message landed in the inbox, avoided filtering, or was read. A sent copy shows what your service retained as sent; by itself, it does not prove the recipient’s final mailbox placement. If comparing headers, share only what is needed and avoid exposing unrelated private message content.
Escalate with a concise record
Involve the recipient’s mail administrator when the address is confirmed, the recipient has searched relevant folders and filters, and the message is still missing—or when a bounce or header points to a rejection or handling issue on the recipient’s domain. The recipient should contact their administrator, since that person may have access to domain-side settings or delivery records unavailable to an outside sender. If the evidence instead points to your sending account or service, contact your own provider’s support.
Provide the exact recipient address, subject, send time with time zone, any bounce text, and relevant headers if available. Do not send passwords, one-time codes, or unrelated mailbox contents. Ask what the available evidence establishes and what remains uncertain; an administrator’s investigation may identify a delivery event without proving inbox placement or that the person saw the message.
Close the loop without overstating the result
After any correction—such as fixing an address or adjusting a recipient-side filter—ask the recipient to confirm whether they can now locate the original or a clearly identified resend. Record which message they found and where, if they are comfortable sharing that. If a resend is necessary, mention that it is a resend so the recipient can distinguish it from the original.
A useful outcome is a specific, limited finding: for example, “the recipient found it in spam” or “a rejection notice named the address as invalid.” If the only evidence is that you sent the message or that a system handled it, say so. Keeping the conclusion precise makes the next troubleshooting step clearer and avoids presenting a clue as proof.
- Confirm recipient, subject, send time, and time zone.
- Check for a bounce or delay notice; note its wording.
- Ask the recipient to search folders and review relevant filters.
- Compare matching headers if available, without treating them as proof of inbox placement.
- Escalate to the recipient’s administrator when the evidence suggests a recipient-domain issue.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction
