Block entire domain (@foo.com) for an alias

[markliederbach]

We currently have the ability to disable a single contact's email address for a given alias. This is a nice feature, but spam is trickier than that. There should be an option to disable an entire sender's domain.

Use case: I have an issue where I receive spam from different addresses within a set of domains. Short of having more complicated sieve-like filters (or trying to do this on client-side which is not ideal), it would be nice to disable an entire sender's domain.

This idea was originally pitched on this discussion (view comment) and received a decent amount of community support.

[IanNorris]

I've also spotted that a bunch of companies are now using solutions (Intercom I think?) where you get emails from hello+@sender.com. Presumably so they can handle return email in the same way we do? What this means is that blocking specific senders to an alias is not possible.

[IanNorris]

I've come across a few domains that appear to be being used liberally for a variety of spam campaigns. I'd love to just blackhole these domains somehow because I can't shutdown the aliases they're being sent to.

[jonathandotbz]

Yes, the ability to both globally and per-alias create a block list (whether as sender@spam.com or *spam.com, etc.) would be greatly appreciated!

[a1phawof]

Desperately need ability to block by domain and subdomain!

[wkhayrattee]

+1
I am also seeing an increased number in spammers using variance in their sender email like {random_pattern}-newsletter@spammerDomain.com
Specially from non-ethical recruiter agencies.

I made a similar request 2 years ago by email. I was told this would be implemented, but did not hear anything back.
So this is a good moment to push this forward.

[schmitzel76]

I also see an increase in spam with different addresses within the same domain, so I would definitely like to have this.

But then I would also be able to have a wildcard for subdomaiins, as that is something I also see more lately. Spam coming from multiple subdomains under the same domain

[Nortonko]

+1 for this feature

[ploum]

I would also like this feature. For example, Slack use different address for each mails and I dont’t want to receive mail from Slack, even when someone want to invite me there.

But, more importantly, I think this should be done globally. Why not global block list? Is there any usecase where you want to block a sender for an alias and not for another one?

See #1488

[tnonate]

Wow, this has been open since 2022 and no response.

+1, I desperately need this feature. While I do sometimes get one-off spammers with unique email addresses (or domains that clearly aren't malicious like Gmail), I definitely have a few top offenders who repeatedly make the rounds. I would love to be able to block an entire domain and cut my spam problem in half. This is not an email address I can disable or replace at this time, so simply disabling it is not an option here.

[nicerobot]

I'd like to generalize this idea slightly. If we had the ability to allow (or deny) specific sender-patterns per alias, it would be the final feature for a perfect email filter.

[douma]

With the possibility of chat control, we might want/ or need(!) to have more control over what gets delivered in our mailbox. Someone (could be spammer or someone else) could send you some content, just to harm you, and you are reported to the police by the algorithm. So a whitelist would be perfect of the exact mail, domains, domains with a range of subdomains.

[IanNorris]

I've started getting huge amounts of spam from TLDs za.com and sa.com, different domains each time, I never get legitimate emails from either so I'd like to block the whole TLD. I can't block this alias unfortunately.

[Chinoman10]

Shall we talk about Beehiiv and their unethical policy that allows any of their clients to import email addresses from wherever without the end-user confirming if they want to be subscribed or not? You can't even report to beehiiv that "I never signed-up for this mailing list" like some other providers (Mailgun, Brevo, etc.) allow you to do.
I'd love to simply block the beehiiv domain (and all their client sub-domains) entirely.

[brenjenny]

Completely, if a domain is not willing to take down information that is private then trash it is what I say. I mean this is how they make their money most of the time. Like been verified or ancestry or whatever but I have seen some pretty terrible people use info for reasons uncalled for. These companies make plenty of money to take down an individuals information upon their request. It's only going to get worse. There will be no such thing as privacy with AI running this world. Might as well live in glass houses. I say sue the domains that are not willing to remove personal info that was put up based on Facebook and other social media sites that are very far from accurate btw. Just because I maybe had an acquaintance I went to school with on my space doesn't mean they are a relative lol pathetic

[hiccups1980]

Any news on this? @nguyenkims

[javaskript]

Let’s make this happen @simple-login