Should I run my own mail server, or should I not?
(Mostly incoming mail)
@algernon @cwebber I found others servers tend to be good at accepting email from independent mail servers. What you need to watch out is that your server doesn't get hijacked for sending spam. That will put you on blacklists.
Owning your own mail server is great fun. You learn a lot and realise that internet is not just HTTP.
@orbifx @cwebber I used to run my own between ~1998 and ~2010, then spam overwhelmed me, and I switched to a hosted solution. I have better tools to combat spam now, so hence the renewed interest. I've ran enough mail servers (one for an ISP with 10k+ users in the early 2000s) in the past to have a rough idea how they work. Wasn't great fun the last time.
But, owning my own data, having more control over what gets accepted and what does not, may worth the trouble. (ATM my host is being annoying)
@cwebber @orbifx greylisting, Spamassassin, CRM114, along with using throw-away addresses. This last part is the new thing this time: for every service, place, whatever that wants my email, I'll use a unique one. If it is a one-off thing, I'll make the address time-limited, and start rejecting it afterwards. If it is something I plan to use later, a unique address allows me to figure out which service leaks my address.
Been using this method for the past two years, surprisingly effective.
@orbifx @cwebber Blacklists are something we used to use at the ISP back in the day. Our relationship didn't end well... had too many false positives at times, or was too slow to add new spam hosts, or they went out of business and started returning positive for everything.
Things may have improved since, but seeing as most spam that gets through to me now is from hosts that are a few hours old, and which don't last long, I'm sceptical about their effectiveness.