this post was submitted on 29 Jun 2023
55 points (100.0% liked)
Technology
37708 readers
336 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Short answer: Don't.
Long answer: It is a massive amount of work, not just to setup, but also to maintain. On top of the fact that the big email providers block smaller email servers like crazy. Even if you had business class Internet service at home, the IP range is most likely already in their block lists. And if you have it on a VPS, the amount of time and effort it takes to get the security and filtering going properly is nightmarish.
It really sucks, but it's a fait accompli.
Would agree.
Even when done 100% by the book and correct. Companies like Google and Microsoft, in particular, will just randomly send the email to spam.
I gave up after years of fighting the good fight and went to googles free tier. That is now over and I probably just need to move to some other service.
Also dont use a gTLD or if you do, have a backup .com or .us as well. Many forms dont recognize things like .email as legit.
Even if you set up everything perfectly you encounter email providers that only have allow lists and you have to jump through hoops to be allowed to send emails to them (like publishing your whole name and address). I loved the fact that I had a mail server but in the end it didn't make sense.
Additionally, these days the sheer amount of flak that a self-hosted mail server gets are enough to make a lot of providers ask you to either shut it down or go somewhere else. Probably 80-90% of the server's inbound network traffic will be bots trying to brute force access (usually over POP3 or IMAP4, though occasionally SSH) to use it as a spam relay as well as relatively dumb bots just assuming that your server is an open relay and trying to send garbage through it. That kind of traffic hogs a lot of bandwidth and the hosting provider will have to do something about it to keep their infrastructure stable. Also, figure that you'll be spending about as much CPU time on the server for anti-spam processing on a 24x7 basis.
I have to agree with other commenters, it's just not worth the hassle and kinetic pattern baldness these days.