I would think this should work, but might be overkill. Email clients often support plugins, where you could install a spam filter plugin to deal with it on your workstation.
Assuming you still want to do all the setup for mailcow:
Your hosting provider’s email could be auto-forwarded to a mailbox set up on the mailcow server, subjecting it to the spam filters on there.
Then you can simply manage your email from said mailbox on the mailcow server.
Mailcow is dockerize with Docker Compose, so its pretty easy to install. Just follow the instructions:
You can host it in a public cloud, but most (if not all) providers block outbound email by default. You have to submit a support ticket to request your server’s IP to have the email ports unblocked.
But doing this would require you do several things to get all this setup and working properly. Upside is you can control your own email domain and email addresses :-) And you’d have calendaring, a web interface to access your email from anywhere, and the ability to customize the web interface with your own logos and color schemes.
- Buy a new domain for your mail server
- Setup MX record for your mail.<domain> server
- Setup A/AAAA records and rDNS records for your mail.<domain> server
- Setup TXT records in DNS for DKIM and SPF records to ensure proper email delivery from your server
- Ideally setup a TXT record for DMARC reporting
- Install mailcow on your server via docker compose.
- Configure SPAM blacklists on your mailcow to block well known spammers
- Submit the support ticket to your cloud provider requesting the email ports for your IP be unblocked
- Make sure your IP assigned to the server won’t change for any reason!
Hope this helps!