What Happens When You Block an Email Address?

You finally had enough. The pushy recruiter, the ex who will not stop emailing, the newsletter you unsubscribed from three times. You hit "block" and feel a wave of relief. Problem solved, right?

Not exactly. Blocking an email address does something different in every email client, and the result is rarely what people expect. In most cases, the blocked email still arrives — it just gets hidden from you. The sender has no idea they were blocked. And if they switch to a different address, the whole cycle starts over.

This guide breaks down what actually happens when you block someone in the five most popular email clients, whether the sender can tell, and what alternatives exist when blocking is not enough.

Blocking in Gmail

When you block a sender in Gmail, their future emails are automatically routed to your spam folder. The emails are not rejected, not bounced, and not deleted. They arrive at Google's servers, pass through the spam filter, and land in your spam folder regardless of their content.

What the sender sees: Nothing. The email is accepted by Gmail's servers and the sender receives a normal delivery confirmation. From their perspective, the email was delivered successfully.

What happens to the email: It sits in your spam folder for 30 days, then gets automatically deleted. If you search specifically in your spam folder, you can still find and read the message during that window.

Important detail: Gmail's block is tied to the sender's email address only. If the same person emails you from a different address, those messages arrive in your inbox as normal. There is no way to block a person across all possible addresses they might use.

Blocking in Outlook and Microsoft 365

Microsoft handles blocking slightly differently depending on whether you use Outlook.com (the web app), the desktop Outlook client, or Microsoft 365 in an enterprise environment.

Outlook.com and the new Outlook app

Blocked senders go to your Junk Email folder. Like Gmail, the email is accepted by Microsoft's servers and the sender receives no indication that they have been blocked. Messages stay in Junk for 30 days before automatic deletion.

Classic Outlook desktop client

The desktop client adds blocked senders to a local Blocked Senders list under Junk Email Options. This works as a client-side rule — the email is downloaded from the server first, then moved to Junk locally. If you access the same mailbox from a phone or web browser, blocked messages may still appear in your inbox because the rule only applies to the desktop client.

Microsoft 365 (enterprise)

Administrators can configure transport rules that reject emails at the server level before delivery. This is one of the few cases where blocking can result in a true rejection — but it requires admin access, not just clicking "block" in your inbox.

Blocking in Yahoo Mail

Yahoo Mail takes a more aggressive approach than Gmail or Outlook. When you block an address in Yahoo, incoming emails from that sender are automatically deleted. They do not go to spam or junk — they are discarded entirely.

What the sender sees: Nothing. Yahoo still accepts the email at the server level. The sender gets no bounce message or delivery failure notification. The email simply disappears into a void.

The limit: Yahoo allows you to block up to 500 addresses. If you are dealing with a high volume of unwanted email from many different senders, you can hit this ceiling.

Blocking in Apple Mail

Apple's blocking behavior depends on which device and which mail service you use.

iCloud Mail (server-side)

If you use an iCloud email address and block a sender through iCloud settings, the block applies at the server level. Blocked emails are moved to Trash automatically, and the behavior syncs across all Apple devices signed into the same Apple Account.

Apple Mail app with third-party accounts

If you use the Apple Mail app with a Gmail, Outlook, or other third-party account, blocking is handled locally by the Mail app. The email is downloaded first, then the app moves it to Trash. This means the block only works on that specific device. Your iPhone might block a sender while your Mac still shows their emails in your inbox.

For a step-by-step walkthrough, see our guide on how to block spam emails on iPhone and iPad.

Blocking in Thunderbird

Thunderbird is a desktop email client, which means all blocking is strictly client-side. When you add a sender to your Blocked Senders list (through junk mail settings), Thunderbird marks incoming messages from that address as junk and moves them to the Junk folder.

The critical limitation: Thunderbird downloads the email from the server before applying the block. The email is already delivered and stored on your mail server. Thunderbird simply hides it after the fact. If you access the same account from any other client — a phone, a web browser, a different computer — blocked messages appear normally.

Thunderbird also has no centralized block list that syncs with other clients. Each Thunderbird installation maintains its own separate list.

Does the sender know they have been blocked?

In almost every consumer email scenario, no. The sender receives no notification, no bounce message, and no error. Their email is silently accepted by the receiving mail server and then handled locally — moved to spam, junk, or trash depending on the client.

This is by design. Email protocols (SMTP) separate the act of accepting a message from what happens to it afterward. When Gmail or Yahoo accepts an email, the sending server's job is done. What the receiving server does with the message after acceptance is invisible to the sender.

There are only two scenarios where a sender might discover they have been blocked:

Scenario	What happens	How common
Server-level rejection	The receiving server refuses the email during SMTP delivery. The sender gets a bounce message (NDR) saying the message was rejected.	Rare for personal blocking. Common in corporate environments.
Read receipt silence	If the sender requested a read receipt and never gets one, they might suspect blocking — but this is not conclusive since most people never send read receipts anyway.	Very rare and unreliable as a signal.

The short answer: blocking is invisible to the sender in Gmail, Outlook.com, Yahoo, Apple Mail, and Thunderbird.

Client-side vs server-side blocking — why it matters

The biggest misconception about email blocking is that it stops the email from arriving. In reality, most blocking falls into one of three categories, and only one of them actually prevents delivery.

Client-side blocking (most common)

Used by: Thunderbird, Apple Mail (with third-party accounts), classic Outlook desktop.

The email is fully delivered to your mailbox. The email client downloads it, then moves it to junk or trash based on a local rule. The email still consumes server storage, still passes through your mail server, and is still visible from any other client or device. This is filtering, not blocking.

Provider-side filtering

Used by: Gmail, Outlook.com, Yahoo, iCloud Mail.

The email is accepted by the provider's servers but diverted to spam, junk, or trash before it reaches your inbox. This is better than client-side blocking because it works across all devices. But the email still arrives at your provider — it is stored on their servers, it uses your storage quota (in the case of spam folders), and the sender's message is technically delivered.

Server-level rejection

Used by: Corporate email gateways, mail server administrators, dedicated email security services.

The email is refused during the SMTP transaction itself. The sending server receives a 5xx rejection code, and the message is never stored on the receiving server. This is the only form of blocking that truly prevents delivery. The sender typically receives a bounce notification explaining that the message was rejected.

For most individual users, true server-level rejection is simply not available. Gmail does not offer it. Outlook.com does not offer it. You cannot configure it in Yahoo or Apple Mail. You are limited to filtering — which hides the problem rather than solving it.

The real problems with email blocking

Even when blocking works as intended, it has fundamental limitations that make it an unreliable long-term solution:

It is per-address only. Block one address and the sender can use another. This is especially common with spam operations that rotate through thousands of sending addresses. Blocking each one individually is a losing game.

It does not revoke access to your address. The sender still has your email address. They can share it, sell it, or add it to other lists. Blocking hides their messages from you, but it does not undo the fact that your address is in their system.

It fragments across clients. If you read email on your phone, your laptop, and a web browser, a block applied in one place may not carry over to the others — unless your provider supports server-side blocking.

It does not scale. If you receive unwanted email from dozens of sources, managing a blocklist becomes a chore. Yahoo caps the list at 500 entries. Other providers have similar practical limits. And every new unwanted sender requires manual action.

These limitations exist because blocking treats the symptom (unwanted messages appearing in your inbox) rather than the cause (your email address being known to unwanted senders).

A different approach — blocking at the source with aliases

The permanent fix for unwanted email is not better blocking — it is controlling who has your real address in the first place.

An email alias is a separate address that forwards incoming mail to your real inbox. You give the alias to a service, a company, or a person instead of your real address. If the alias starts receiving unwanted email, you deactivate it. No blocking, no filtering, no cat-and-mouse game with rotating sender addresses. The alias simply stops accepting mail, and your real address remains untouched.

This is fundamentally different from blocking because you are cutting off the channel, not just hiding messages that come through it. The sender cannot work around it by switching addresses, because they never had your real address to begin with.

If you gave out a unique alias to each service, you also know exactly which company leaked or sold your address when spam starts arriving on a specific alias. That kind of accountability is impossible with traditional blocking.

How Cleanbox handles unwanted senders

Cleanbox evaluates every incoming email before it reaches your inbox, using Rspamd to score messages based on authentication, sender reputation, and content analysis. Emails that fail these checks are rejected at the server level during the SMTP transaction — not hidden in a spam folder, not silently deleted, but refused before delivery. This is the server-level rejection that consumer email providers do not offer to individual users.

Beyond spam filtering, Cleanbox provides receive-only email aliases that you can create for any situation. Each alias forwards to your real inbox, and each one can be individually managed — whitelisting trusted senders, muting low-priority ones, or blocking specific addresses permanently. When an alias is no longer useful, you disable it with one click.

Quick reference — blocking behavior by client

Email client	Block type	Where blocked mail goes	Sender notified?	Syncs across devices?
Gmail	Provider-side filter	Spam folder (30 days)	No	Yes
Outlook.com	Provider-side filter	Junk folder (30 days)	No	Yes
Outlook desktop	Client-side rule	Junk folder	No	No
Yahoo Mail	Provider-side filter	Deleted (no folder)	No	Yes
Apple Mail (iCloud)	Provider-side filter	Trash	No	Yes (Apple devices)
Apple Mail (third-party)	Client-side rule	Trash	No	No
Thunderbird	Client-side rule	Junk folder	No	No

The bottom line

Blocking an email address feels decisive, but in practice it is a cosmetic fix. The email still arrives, the sender still has your address, and the block only works reliably if you stick to a single device and a single client. For occasional annoyances, blocking is fine. For persistent or escalating unwanted email, you need either server-level rejection, aliases that let you cut off channels entirely, or both.

The best long-term strategy is to stop giving out your real email address to services and contacts you do not fully trust. When every signup gets its own alias, the question changes from "how do I block this sender" to "do I still want this alias active?" That is a much simpler problem to solve.