# Allow to block full domain(or server)

**URL:** <https://forum.delta.chat/t/allow-to-block-full-domain-or-server/376>\
**Category:** Feature Proposal\
**Created:** [April 17, 2019, 12:20pm UTC](https://forum.delta.chat/t/allow-to-block-full-domain-or-server/376 "2019-04-17T12:20:49Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\
**Post date:** [April 17, 2019, 12:20pm UTC](https://forum.delta.chat/t/allow-to-block-full-domain-or-server/376/1 "2019-04-17T12:20:49Z")

</div>

When I tap in a message I am asked to block that user, but for a self-hosted annoying “friend” or spammer is really easy to just send the message with other email address from their server, so it would be really nice to ask to block user or full domain when I tap in a contact request, ex. when I tap a message from _[acc1@spammingserver.com](mailto:acc1@spammingserver.com)_ I am asked to block _[acc1@spammingserver.com](mailto:acc1@spammingserver.com)_ or to block all messages coming from server _@spammingserver.com_ so all messages from _[acc2@spammingserver.com](mailto:acc2@spammingserver.com)_, _[acc3@spammingserver.com](mailto:acc3@spammingserver.com)_, …, _[accN@spammingserver.com](mailto:accN@spammingserver.com)_

---

<div class="post-metadata">

**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\
**Post date:** [April 17, 2019, 12:23pm UTC](https://forum.delta.chat/t/allow-to-block-full-domain-or-server/376/2 "2019-04-17T12:23:18Z")

</div>

This will be useful to block some services that sent you generated email address to notify you, ex. github, or if I would like to block the Matrix email bridge since it is not compatible with DC, every people that write me from Matrix has a different email address, etc

---

<div class="post-metadata">

**Author:** ![Simon](https://forum.delta.chat/user_avatar/forum.delta.chat/simon/32/287_2.png) [@Simon](https://forum.delta.chat/u/Simon)\
**Post date:** [April 17, 2019, 4:31pm UTC](https://forum.delta.chat/t/allow-to-block-full-domain-or-server/376/3 "2019-04-17T16:31:45Z")

</div>

Blocking in the meaning that they don’t show up or in the meaning that they get rejected by your mail server?

Either way, I think setting up a filter in the providers settings is the better way to go (although we can and probably should provide tutorials on how to do it)

---

<div class="post-metadata">

**Author:** ![Simon](https://forum.delta.chat/user_avatar/forum.delta.chat/simon/32/287_2.png) [@Simon](https://forum.delta.chat/u/Simon)\
**Post date:** [April 17, 2019, 4:35pm UTC](https://forum.delta.chat/t/allow-to-block-full-domain-or-server/376/4 "2019-04-17T16:35:35Z")

</div>

Also if we do enable blocking client side we should warn the user about the consequences of blocking email domains so they don’t block legit services by accident.

---

<div class="post-metadata">

**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\
**Post date:** [April 17, 2019, 6:18pm UTC](https://forum.delta.chat/t/allow-to-block-full-domain-or-server/376/5 "2019-04-17T18:18:22Z")

</div>

“blocking” here has the same meaning than blocking an user, and mean that all users from “[somedomain.com](http://somedomain.com)” will be blocked **in Delta Chat** ,  
not all servers provide filters, ex. mine, Nauta 😉 and playing with server filters are not for a solution for an average user  
and this will be useful to block emails form GitHub for example.

---

<div class="post-metadata">

**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\
**Post date:** [April 17, 2019, 6:21pm UTC](https://forum.delta.chat/t/allow-to-block-full-domain-or-server/376/6 "2019-04-17T18:21:33Z")

</div>

message similar to what you show when blocking an user:  
“block all users from [spammers.com](http://spammers.com)?, you will no longer see their messages in Delta Chat”

does this need more explanations??  
also users can see the domain in the blocked list.

---

<div class="post-metadata">

**Author:** ![zgzgng](https://forum.delta.chat/user_avatar/forum.delta.chat/zgzgng/32/529_2.png) [@zgzgng](https://forum.delta.chat/u/zgzgng)\
**Post date:** [February 5, 2020, 9:50am UTC](https://forum.delta.chat/t/allow-to-block-full-domain-or-server/376/7 "2020-02-05T09:50:47Z")

</div>

> [@Simon](#):
>
> Blocking in the meaning that they don’t show up or in the meaning that they get rejected by your mail server?

Block in this context means _hide_ in the client. The server parlance for block is _reject_. A softer case, like colloquial ghosting, is _blackhole_.

Reject generates an MTA response message.

Blackhole tosses messages into the void never hitting the inbox. This is not ‘trash’

An example for MTA rejection response is to send an email to a non-extant user in a domain

[notreal@delta.chat](mailto:notreal@delta.chat)

(assuming there is not a blackholing default sieve)

---

<div class="post-metadata">

**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\
**Post date:** [October 5, 2026, 12:36pm UTC](https://forum.delta.chat/t/allow-to-block-full-domain-or-server/376/8 "2026-10-05T12:36:17Z")

</div>

closing stale issue.

meanwhile, a contact does not have a binding to an address; but a contact can have multiple relays, that are not even of interest, so blocking a domain or server as suggested years ago needs to be overthought

---

<div class="post-metadata">

**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\
**Post date:** [October 5, 2026, 12:36pm UTC](https://forum.delta.chat/t/allow-to-block-full-domain-or-server/376/9 "2026-10-05T12:36:21Z")

</div>


