How to Block Emails: Stop Unwanted Senders at Every Level, From Inbox to Server

27 June 2026
by: Fatima Benali
in: Email services
Tags: block emails, email filtering, spam
note: no comments

If a particular sender keeps landing in your inbox and you just want it to stop, take a breath — this is one of the most fixable problems in email. The trick is knowing that “blocking emails” isn’t a single action. It happens at three different levels, and the right level depends on what you’re actually trying to stop: one annoying person, or a flood of spam from senders you’ve never heard of.

Table of Contents

Those are two genuinely different problems, and they call for different tools. In this guide I’ll walk you through every level where you can block email — calmly, in plain language — so you can pick the approach that actually fixes your situation instead of fighting it one message at a time. If you run your own domain or business email, I’ll spend extra time on the parts you control directly, because that’s where the real leverage is.

Key Takeaways
• You can block email at three levels: your client/webmail, your mailbox/server account, and the host’s spam-filtering layer.
• Blocking a *specific known person* is easy and reliable — use a block-sender rule or filter at the client or mailbox level.
• Blocking *spam* by address barely works, because spammers forge and rotate sender addresses constantly.
• For real spam, layered filtering — spam scoring, blocklists, greylisting, plus SPF, DKIM, and DMARC — beats any blocklist.
• Block people; *filter* spam. They’re different problems with different tools.

Here’s the thing almost nobody tells you: blocking individual email addresses is the least effective anti-spam tactic there is. Real spammers forge and rotate their sender addresses constantly — block one and the next message simply arrives from a different fake address, then another, endlessly. You can spend the rest of your life adding addresses to a blocklist and never gain ground, because you’re playing a game the spammer designed to be unwinnable. Blocking *is* genuinely great for one job: a known person — an ex, a pushy salesperson, that one contact you simply don’t want to hear from — whose real address never changes. For that, a block rule works perfectly and forever. But for actual spam, the durable solution is layered filtering that judges messages by behavior and reputation — spam scoring, reputation blocklists, and sender authentication like SPF, DKIM, and DMARC — not an ever-growing list of addresses. Block specific people; filter spam. Two different problems, two different tools.

What does “blocking emails” actually mean?

When people say they want to block emails, they usually mean one of two things. Either a specific person or company keeps emailing them and they want that to stop, or they’re drowning in spam and want the noise gone. The reason this matters is that the solutions sit at different levels of the email system, and reaching for the wrong one is why so many people feel like they’re losing.

Email passes through several stages before it reaches your eyes: it arrives at your hosting provider’s mail server, gets scored and screened by spam-filtering software, lands in your mailbox account, and finally appears in whatever client or webmail you read it in. You can intervene at any of those stages. The table near the end of this guide lays out which level suits which goal, but the short version is this: the closer to the server you act, the more powerful and automatic the protection — and the further from you it has to travel to bother you.

How do you block a specific sender at the client or webmail level?

This is the level most people already know, and for blocking a *known* person it’s perfect. Every modern email client and webmail interface — without naming any single brand — gives you a way to block a sender or mark a message as spam.

The pattern is almost always the same. Open the unwanted message, find the menu (often a three-dot icon or a right-click), and choose Block sender or Block [name]. From then on, mail from that exact address gets routed to junk or deleted automatically. Many clients also offer a separate Report spam or Mark as junk action, which does something subtly different — more on that distinction shortly.

If you want more control than a simple block, build a rule or filter instead. Most clients let you create a rule that says, in effect: *if a message comes from this address (or contains this word in the subject), move it to Trash or Junk automatically.* Rules let you block by address, by domain, or even by keyword, and they’re the client-side version of the more powerful mailbox filters we’ll get to next. If you want to go deeper on building these, .

Best for: one or two known senders you personally don’t want to hear from. Limitation: these rules usually live only in that one client or device, and they do nothing to slow down rotating spam.

How do you block emails at the mailbox or server level on hosted email?

This is where things get interesting if you have business email on your own domain — and it’s the level most people overlook. Instead of blocking inside one app, you block at the mailbox account itself, on the server. That means the block applies no matter where or how you read your mail: webmail, phone, laptop, all of it. Set it once, and it follows you everywhere.

On most hosted email — through cPanel, a hosting control panel, or webmail’s settings — you’ll find a few tools:

Account-level filters. These are server-side rules attached to your mailbox. You can discard, redirect, or junk messages based on the sender address, the sender’s domain, the subject line, or specific keywords in the body. Because they run on the server, they apply before mail ever reaches any of your devices.
Address and domain blocklists. You can block a single address ([email protected]) or an entire domain (everything from @spammydomain.example) in one move. Blocking a whole domain is far more efficient than chasing individual addresses when a single source is the problem.
Per-mailbox spam settings. Many hosts let each mailbox tune its own spam sensitivity, choose whether flagged mail is deleted or quarantined, and maintain personal allow/block lists.

Server-side filters are the unsung heroes here. A rule like *discard any message whose subject contains “final notice” from outside my company* runs on the mail server itself, consistently, for every device you own. If you want the full mechanics of these, see .

Best for: anyone with their own domain who wants blocks that stick across all devices, plus the ability to block whole domains at once. Limitation: like all address-based blocking, it still can’t keep up with spammers who change addresses every message.

How does blocking work at the server and spam-filter level?

Now we reach the most powerful level — and the one that does the most for you while asking the least. This is your host’s spam-filtering layer, the screening that happens to *every* message before it ever touches your mailbox.

Good email hosting runs incoming mail through several checks:

Spam scoring. Software in the style of SpamAssassin assigns each message a score based on dozens of signals — suspicious phrasing, deceptive formatting, mismatched headers, known spam fingerprints. Score too high, and the message is quarantined or rejected. Crucially, this judges the *message*, not just the address it claims to come from.
Reputation blocklists (RBLs). The server checks the sending machine’s IP address against shared, constantly updated lists of known spam sources. Mail from a flagged server can be refused at the door.
Greylisting. The server temporarily defers mail from unknown senders and asks them to try again. Legitimate mail servers retry automatically and get through; many spam systems don’t bother, so they never deliver. It’s a simple, quiet, effective filter.

This is filtering by *behavior and reputation* rather than by maintaining a list of addresses, which is exactly why it survives address rotation. For a fuller picture of how this whole screening layer fits together, see .

Block, report, or unsubscribe — which action should you take?

People reach for “block” reflexively, but it’s often not the right tool. Three different actions handle three different situations:

Block when it’s a *known person or company* whose real address won’t change and you simply never want to hear from them again. Personal, deliberate, durable.
Report spam / mark as junk when it’s *unsolicited junk* from a sender you don’t recognize. This doesn’t just hide the message — it teaches the filtering system, improving detection for you (and often other users) going forward. For spam, reporting is usually more valuable than blocking.
Unsubscribe when it’s *legitimate mail you once opted into* — a newsletter, a store, a service — that you no longer want. A genuine sender honors unsubscribe requests, and this is cleaner than blocking because it stops the mail at the source.

A useful rule of thumb: unsubscribe from senders you trust, report senders you don’t, and block specific people you simply want gone.

Why isn’t blocking emails always enough?

If you’ve ever blocked address after address and watched the spam keep coming, you weren’t doing anything wrong — the approach itself is the problem. Spammers don’t send from one fixed address. They forge sender names, spin up throwaway addresses by the thousand, and rotate them faster than any human could ever block. Each blocklist entry you add is already obsolete by the time the next message arrives.

That’s why the durable answer to spam is layered filtering plus sender authentication. Filtering catches mail by what it *does* and where it *comes from*, not by a name it claims. And authentication — SPF, DKIM, and DMARC — lets receiving servers verify whether a message genuinely came from the domain it says it did, which shuts down a huge category of spoofing and impersonation. These records protect both your inbound screening and your own domain’s reputation. If you haven’t set them up, that’s the highest-value thing you can do, and walks through it step by step.

How do you reduce spam at the root?

The calmest inbox isn’t the one with the longest blocklist — it’s the one spam struggles to reach in the first place. A few habits cut the problem down at the source:

Don’t expose your address publicly. Posting your real address on websites, forums, or social profiles feeds it straight to the harvesting bots that build spam lists. Use a contact form or an image instead of plain text where you can.
Use aliases. Create disposable or purpose-specific addresses ([email protected], [email protected]) for sign-ups. If one starts attracting spam, you retire just that alias without touching your main mailbox.
Set up proper authentication. A domain with correct SPF, DKIM, and DMARC is both harder to spoof and more trusted by other servers — which keeps *your* mail out of spam folders and makes impersonation of your domain much harder.

Do these, and the layered filtering above has far less to do, because most of the junk never finds you to begin with.

Which method should you use? A quick reference

Here’s the whole picture in one place — the level, how you do it, and what it’s best suited for.

Level	How you block	Best for
Client / webmail	Block-sender button, mark as spam, personal rules/filters	One or two known senders on a single device
Mailbox / server account	cPanel/webmail filters, account-level rules, address & domain blocklists	Blocks that stick across all your devices; blocking whole domains
Server / spam-filter layer	Host’s spam scoring, reputation blocklists (RBLs), greylisting	Stopping high-volume, rotating spam automatically
Authentication (cross-cutting)	SPF, DKIM, DMARC	Verifying real senders and stopping spoofing at the root

The pattern is clear: act close to *you* for a specific person, and close to the *server* for spam at scale.

Cleaner inboxes with DarazHost business email

This is exactly the problem DarazHost business email is built to solve. You get strong, layered spam filtering working on the server before mail ever reaches you — spam scoring, reputation blocklists, and greylisting — so rotating spam gets caught automatically without any effort on your part. At the same time, easy per-mailbox filters and blocklists in webmail and cPanel let you block specific senders or entire domains in a couple of clicks, and those blocks follow you across every device. It’s all backed by proper SPF, DKIM, and DMARC, configured correctly so your domain is both trusted and protected from spoofing. The result is a genuinely cleaner inbox on email you actually control — and if you ever need a hand, our support team is here 24/7. For the complete picture of running professional email on your own domain, read our business email hosting guide.

Frequently asked questions

Will blocking an email address stop all spam from that sender? For a real person whose address stays the same, yes — blocking is reliable and permanent. For spam, no. Spammers forge and rotate sender addresses constantly, so a blocked address is usually abandoned before your next piece of junk even arrives. For spam, lean on filtering and the “report spam” action rather than blocking individual addresses.

Should I block or report a spam email? Report it. Blocking only hides that one address, while reporting (marking as junk or spam) trains the filtering system to recognize similar messages in future, which protects you against the next variation too. Reserve blocking for known senders you simply never want to hear from.

Can I block an entire domain instead of one address? Yes, if you have hosted email with mailbox or server-level controls. In cPanel or webmail filters you can block every message from a whole domain (for example, all mail from @example.com) in a single rule — far more efficient than blocking addresses one at a time when one source is the problem.

What’s the difference between blocking and filtering? Blocking acts on a specific sender address you choose. Filtering judges each message by its content, behavior, and the reputation of the server that sent it — spam scoring, blocklists, greylisting — so it catches junk even from addresses you’ve never seen. Block known people; filter unknown spam.

Do SPF, DKIM, and DMARC really help reduce unwanted email? Yes, significantly. These authentication records let receiving servers verify that a message genuinely came from the domain it claims, which blocks a large share of spoofing and impersonation. They also protect your own domain’s reputation so your legitimate mail stays out of recipients’ spam folders. They’re a core part of any serious anti-spam setup.