rspamd is used nowadays. Add sieve filtering to automatically move mails with a 7.0 or higher to a spam-folder. Manually move mails there that haven't been detected and move mails out of the spam folder that have been falsely detected (personally don't have any false positives with rspamd).

Then set up bayes learning with rspamd, either when mails are moved between folders or every few hours.

@Shimitar @yunohost - / #yunohost has email hosting with dovecot and #spamhaus configured in it. There were some issues with spamhaus when running version 11 on vps but i read v12 fixed them.

Rspamd seems to be common, it's included in the mailcow stack and others. Seems to work pretty good, I've been on Mailcow for several years now with no major spam issues after I dialed it up a bit.

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.

Not 100% on topic, but as a preventative method, I use an email forwarding service (like SimpleLogin, Anonaddy, etc), because you can just delete an alias if it starts spamming.

Might be too late for that now though, I'm guessing once your email gets out there, it's gonna be rough going for a long while until they stop spamming, if they ever do.

Are you serving from a homelab or VPS? If a homelab, then you could use pFsense to filter spam. I don't run my own email server but I do use pFsense to filter 95% of the junk from my inbox. I'm not sure how you'd accomplish that on a VPS other than employing some type of spam filtering software.

The best way I found to combat spam was to change my email address. Was it a pain? Yes. Was it worth it? Absolutely yes.

Suddenly I can just give my email address out to services I trust, and I set up a temporary alias for anything I don't (although I tend to avoid those these days anyway).

I definitively also observe the recent increase of spam (mostly on info@domain) however spamassassin (after some training) does a decent job sorting the trash out. Also I use a unique email address for each website I register, this way a lot of spam was removed by blocking an email-address I've used for login to facebook 10 years ago.

I still run SpamAssissin on my own mail server, but only because I haven't yet seen any objective measurement showing some other solution to be better.

I just use some dnsbl. Spam tagging seems pointless to me, as i would sift through the spam anyways to .make sure not to miss anything.

It's been a while since I selfhosted my email, but I found it pretty efficient to set up a spam filter that periodically logged into my Gmail address and used its spam folder to train a bayes classifier.

@Shimitar@downonthestreet.eu This, part of a series https://floof.sbs/#06