What Is Email Bounce vs Email Block vs Email Filter?

Bounce, block, and filter are three different things that happen to email. The terms sound similar, get used interchangeably in casual conversation, and refer to genuinely different events with different implications for sender and recipient.

This post clarifies the precise difference, what each one does to your email, and where Rythm sits in the taxonomy.

Bounce: A Delivery Failure

An email bounce is what happens when a message cannot be delivered to the intended recipient. The sender receives a non-delivery report (NDR) explaining why. The bounce is a feedback signal that something in the delivery chain did not work.

There are two flavors.

Hard bounce. A permanent delivery failure. The recipient address does not exist, the domain is invalid, or the receiving server has explicitly rejected the address as undeliverable. Common causes: typo in the address, the recipient closed their account, the domain has expired, the receiving server has the address on a permanent blocklist. Hard bounces tell the sender to stop trying.

Soft bounce. A temporary delivery failure. The recipient address exists but the message could not be delivered right now. Common causes: the recipient’s mailbox is full, the receiving server is temporarily down, the message exceeded the server’s size limit, the recipient’s storage quota is exceeded. Mail servers typically retry soft bounces over a 24 to 72 hour window before giving up.

Bounces are not blocks. They are reports back to the sender that delivery did not happen. The sender’s mail server logs the bounce and, in most well-configured systems, removes the address from future sends to avoid sending to dead addresses.

Block: A Refusal Before Delivery

An email block is when the receiving server refuses to accept the message. The block happens before the message reaches the recipient’s mailbox at all. The sender may or may not get a notification depending on how the block is implemented.

Common reasons for blocks:

Domain or IP blocklist. The sending domain or IP address has been added to a blocklist (Spamhaus, Barracuda Reputation Block List, and similar services maintain these). Receiving servers consult blocklists before accepting mail from a sender. If the sender is on the list, the message is rejected.

Authentication failure. The message fails SPF, DKIM, or DMARC checks. The receiving server cannot verify that the message actually came from the claimed sending domain, so the receiving server refuses to accept it. Properly configured receiving servers reject mail that fails authentication, particularly for domains with strict DMARC policies.

Rate limiting. The sender is sending too quickly or in too high a volume. The receiving server temporarily blocks further messages from the sender to prevent abuse.

Connection-level rejection. The sending server’s IP has a poor reputation score, the connection looks suspicious, or the sender violated a connection-level rule. The receiving server drops the connection before any messages are exchanged.

A block is a strong action. The message never reaches the recipient at all. The sender often does not know which specific recipient was blocked, only that the receiving server refused the connection or the message.

Filter: A Routing Decision After Delivery

An email filter is what happens after the receiving server has accepted the message. The message is in the recipient’s mailbox or has reached the routing layer. The filter decides where to put it.

Common filter destinations:

Spam folder. Messages classified as likely spam by the provider’s content classifier. The recipient can review the spam folder and recover real messages that were misclassified.

Promotions / Updates / Forums (Gmail). Gmail’s category system that automatically sorts mail into separate tabs based on content patterns. Promotional mail, social notifications, automated updates. Each category is a kind of filter destination.

Junk / Focused (Outlook). Outlook’s equivalent. Junk for likely spam, Focused for likely-important mail, Other for less-important accepted mail.

Custom labels. Filters the user has set up. “Apply label ‘Newsletters’ to anything from substack.com.” “Skip the inbox for receipts and invoices.”

Holding folders. For services like Rythm, mail from senders who are not on the guest list is filed into a separate folder until the recipient reviews it.

The defining property of filtering is that the message has been accepted by the receiving server and is now somewhere in the user’s mailbox. The filter only changes which folder. The recipient can typically move the message to the inbox if the filter routed it elsewhere.

What Most People Mean When They Say “Block”

Casual usage often blurs the distinction. “I blocked that sender” usually means one of two things:

The user added the sender to a personal block list. Gmail and Outlook both have a per-user block feature. Mail from that sender is automatically routed to spam (Gmail) or junk (Outlook). This is technically filtering, not blocking, because the message was still accepted by the server. The user just told the provider where to put it.

The user reported the sender as spam. Reporting trains the provider’s filter. Future messages from that sender are more likely to be classified as spam. This is also filtering, with a feedback loop into the classifier.

True server-level blocks are usually invisible to end users. They happen at the IT level for businesses or at the provider’s anti-abuse infrastructure. End users who say “I blocked someone” are almost always describing filtering.

Where Rythm Sits

Rythm is a filter, not a blocker, and it does not bounce. The distinction matters because some users assume any tool that prevents unwanted email from reaching them must be blocking it.

The actual mechanism: Rythm runs as an OAuth-connected layer on top of Gmail or Outlook. When a message arrives, Rythm checks whether the sender is on the user’s guest list. Known senders’ messages reach the inbox normally. Unknown senders’ messages are filed into a separate folder (“RYTHM: REJECTED” by default, though the recipient can rename it). The message was accepted by the receiving server and exists in the user’s mailbox. Rythm just routed it to a different folder.

Nothing is deleted. The recipient can review the held folder at any time and rescue any message with one click. Rescuing adds the sender to the guest list permanently. The held folder is a filtering destination, not a deletion.

This is intentional. Blocking is destructive (the message is gone, the sender may or may not know). Filtering is reversible (the message is somewhere, the recipient decides what happens next). Rythm runs as a filter so that errors are recoverable. We covered the holding-folder design in what happens to filtered emails.

Why the Distinction Matters

For senders, the distinction determines what feedback they get and what they can do about it.

A bounce tells the sender the address was undeliverable, and the sender can update their list.

A block tells the sender (often through their email service provider’s reports) that their sending pattern or domain has reputation issues, and the sender can take steps to improve deliverability.

A filter tells the sender almost nothing. The message was accepted; what happened to it after acceptance is between the recipient and their email client. A sender whose mail consistently lands in the spam folder may not realize this without active monitoring of test inboxes.

For recipients, the distinction determines whether mistakes are recoverable.

Bounces are usually correct (the address really does not work) and easy to diagnose.

Blocks are usually correct (the sending pattern really does look like spam) but can produce false positives if a legitimate sender has reputation issues.

Filters produce both false positives (real mail in spam) and false negatives (spam in the inbox). The recipient has to triage to catch mistakes. The triage cost is the price of probabilistic content filtering.

Why Filters Are the Common Case

Most modern email defense happens through filtering rather than blocking or bouncing. The reason is that bounces and blocks are blunt: the message is gone, and false positives are expensive to recover from. Filters are softer: the message is somewhere, and the recipient can adjust if the filter got it wrong.

Provider design has trended toward filtering for the same reason. Gmail almost never bounces or blocks legitimate-looking mail; it accepts and routes. Outlook does the same. The decision-making has moved from the receiving server (which used to bounce or block more aggressively) to the inbox-level filter (which accepts and sorts).

Rythm follows this design. Mail is accepted by Gmail or Outlook, then routed by Rythm based on the guest list and cover charge logic. The result is that no error is fatal: the recipient can rescue any held message, and senders never see a hard rejection.

For the broader frame on what economic email filtering is and how it differs from spam filtering, see what is economic email filtering and email paywall vs spam filter.

The Quick Reference

• Bounce. Delivery failure. Sender gets a non-delivery report. Often “address not found” or “mailbox full.”
• Block. Refusal before delivery. Receiving server rejects the message. Often due to authentication failure or blocklist match.
• Filter. Routing decision after delivery. Message is accepted and placed in a folder (inbox, spam, junk, custom label, holding folder). Recipient can move the message.

Rythm is a filter that runs on top of Gmail or Outlook, holds unknown-sender mail in a separate folder, and accepts a small cover charge in lieu of guest list status. Nothing is bounced. Nothing is blocked. Nothing is deleted. Everything is filed, and rescue is one click.