An email can leave your Sent folder without appearing in the recipient’s inbox. One possible explanation is a rule or blocked-sender setting on the recipient’s side. Depending on how their mail service handles it, the message might be rejected, filtered away from the inbox, or handled without a notice reaching you. That uncertainty makes it easy to mistake a block for a technical failure. Here’s how to check the possibility respectfully, what the recipient can review, and how to confirm whether an ordinary message is getting through—without trying to get around someone’s choice.
The useful bits
- A missing bounce does not prove that a message reached the inbox.
- Ask the recipient through a trusted, appropriate route whether they blocked your address.
- Let the recipient review their own settings; respect a decision not to receive messages.
What a recipient-side block can do
A recipient may block a particular sender address using their mail service or an email app. The result depends on the recipient’s provider and settings. A message might be refused, routed away from the inbox, or treated in another way. You generally cannot see the recipient’s settings from your account, so the message’s apparent status on your side does not establish what happened after it was sent.
A block is only one possible explanation. A typo in the address, a full mailbox, a temporary service issue, or the recipient overlooking the message can also matter. Avoid treating a delayed or absent reply as proof that you were blocked.
Why you may not get a clear notice
Mail systems do not all report filtering decisions to senders in the same way. Some rejected messages may produce an automated delivery failure, while a message filtered after acceptance may not generate a useful notice. Notices can also be delayed or unclear. The absence of a bounce therefore does not confirm delivery, and a message in Sent only confirms that it was sent from your account—not that the recipient read it or saw it in the inbox.
If you do receive a failure notice, read the details rather than assuming it means the recipient blocked you. The notice may identify a different address or delivery problem. Do not repeatedly resend the same message while the cause is uncertain.
Ask through a trusted route
If you have a legitimate reason to follow up, use another route the recipient has already made appropriate for contact—for example, a conversation in person or an established work channel. Keep the question brief and neutral: ask whether they are receiving your email and whether they chose to block your address. Do not create a new account, use another person’s address, or switch channels to continue a conversation after the recipient has said they do not want contact.
A non-response on the other route is not permission to escalate. If the recipient does not respond, or has asked you not to contact them, stop. A delivery concern does not override their stated preference.
What the recipient can review
If the recipient wants to receive your messages, ask them to inspect their own blocked-sender list, filters, rules, spam or junk folder, and any forwarding or sorting they configured. The exact names and locations vary by service and app. They can look for the precise address you send from and check whether a rule moves or deletes messages from it.
The recipient should make any change themselves, using their own account and judgment. If they find an entry and choose to remove or adjust it, they can also check that your address is spelled correctly in their contacts or permitted-sender settings, where those controls are available. These steps do not guarantee delivery; other filters or service conditions may still apply.
A respectful check, step by step
Keep the check small and agreed. First verify the recipient address for a simple typing error. Then ask the recipient, through a trusted route, whether they want to receive your email and whether they can review their settings. If they confirm they want the messages and make a change, agree on one ordinary follow-up message. Avoid sending sensitive information or multiple test messages.
For example, a colleague expecting a project attachment could ask in an established work chat whether the colleague wants to receive the email and can check their blocked-sender and filtering rules. If the colleague confirms, they can request one follow-up with a clear subject and no attachment. If they do not want the message, the sender should not send it.
Subject: Follow-up we discussed To: [recipient@example.com] From: [sender@example.com] Body: As agreed, I’m sending this brief follow-up. Please let me know through our usual channel if it arrived.
How to tell whether the check helped
The clearest practical confirmation is the recipient telling you they received the agreed follow-up, or replying to it. A sent-message entry or lack of a bounce is not equivalent confirmation. If the recipient says they changed a setting but still does not see the message, ask them to check the relevant folders and filters again, if they wish, and consider whether another delivery issue needs attention.
If the recipient cannot confirm receipt, do not keep sending tests or try alternate addresses to defeat a block. You can explain the uncertainty once through the agreed route, then leave the next step to them. Respecting their choice is more important than obtaining a delivery confirmation.
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