57
Spam blocking in 2026
(downonthestreet.eu)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Apr 2026
57 points (98.3% liked)
Selfhosted
61021 readers
250 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
Most effective method for me has been to use 1 e-mail address alias per service. If that address starts receiving spam then you know who is to blame for the leak, can move that service to a new e-mail address and then blackhole all e-mails sent to the old address. That obviously means having to setup a new address for every service though so I usually setup 20 at a time and hand them out as needed.
That seems overkill, in fact my 20y old only address still works pretty fine, and with rspamd setup, with basic settings, the annoying few emails have been intercepted now.
But indeed an extreme but effective approach, yours.