90
My first E-Mail server
(lemmy.world)
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 31 Jul 2023
90 points (97.9% liked)
Selfhosted
38652 readers
321 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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- 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 1 year ago
MODERATORS
Take it from someone who's got over 15 years experience in the field... Or not. Your call :)
As someone who also has 15+ years of experience in the field and is currently infosec management, it's not that bad. Certainly not something I'd say "you're in for a world of hurt" about like somebody just bought a bad timeshare.
Especially if you're not hosting production email for a company and you're not leaving the server as an open relay, it isn't very painful at all.
You could also be less condescending, but as you said: your call. :)
Wasn't intending to come off condescending. IMO exposing your internal network to the internet without a proper firewall is a risk, one I wouldn't take unless I had a DMZ and a dedicated VLAN.
In addition, you'd have to be on top of patch management. And when you do that, there's a chance of something breaking too. My preference is not to have to muck around troubleshooting my own email server when a patch window goes bad since that's what I deal with all day anyway. There will always be zero days, I'll just pawn that off the the big boys.
All of that is inherent in self hosting anything publicly accessible. You wouldn't start off a reply to someone setting up openvpn with "you're in for a world of hurt," would you?
I've also been doing that for ~10 years. It's not the easiest service to run, but it's definitely not the one I had the most issues with. I would agree that in the professional field, there isn't much advantage to host it yourself, and I would advise going with hosted services in this case. But on a selfthosted community forum I see no reason to say such things to a new user trying it out, especially if they don't plan to host other people mailboxes.
I'd say the difficulty depends mostly on the stack you decide to run. I've tried Microsoft Exchange, which is very complex, postfix which is okay once you get the hang of the config file syntax, and opensmtpd which is delightful to configure given its simplicity. Docker also helps tremendously compared to what was available 15 years ago.
Actually delivering emails into inbox is another difficult aspect, but now there are just so many good resources to learn from that you can easily figure out what to do.