Selfhosted
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:
- selfh.st Newsletter and index of selfhosted software and apps
- 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!
view the rest of the comments
Yeah, residential ISPs do that because if they don't, spammers will just turn every botnet member into a spam host. You'll probably have to get a business connection or change ISPs.
Or just don't self-host email. I wouldn't recommend it unless you're a masochist.
@SheeEttin @AdrianTheFrog +1 Email for me is basically irrelevant. MFA resets, adverts from companies I forgot to unsubscribe from and a couple of bills. No personal correspondence or anything I would think is worth self-hosting it for these days. Other than many headaches.
Yes, blocking port 25 outbound is incredibly common by default. Even on some server connections. It is probably better overall for exactly the reasons that you mentioned.
IMHO this is a bit overblown. Hosting inbound is fairly easy. Mail senders (probably for the worst) are very forgiving even if your TLS cert is expired you will probably get mail. Plus senders are supposed to retry for days if you have downtime.
However it is unfortunately true that due to spam sending is a huge pain because IPv4 reputation is a huge component. Sure you can get GMail to trust your domain after a month or so of sending if you have decent volume. But other providers who you may mail once a year are just going to go off of IP reputation. However email was basically designed for forwarding and you can use a service like AWS SES to forward your email from a trusted IP pretty easily. If you are low volume (like personal mail) there are tons of services that will do this for free.
Inbound spam is also a problem. Gmail's filter is pretty good, and it responds to what you personally mark as spam. Other providers aren't as good, and I don't know if there's any good self-hosted filter at all.
Its a problem but it isn't a major problem. I am using rspamd without any sort of exotic configuration (basically just enabling things that are provided, not my own rules) and I only get a few spam messages leaking through a week. Maybe slightly worse than GMail but not considerably slow.
IMHO the only real missing thing out of the box is contacts checking. Which is a huge thing because it is great to have reliable delivery from contacts. But my false-positive ratio is so low anyways that it isn't a big issue and things like the
known_sendersmodule mostly mitigates it.I don't really stay on top of my gmail that often, but my spam folder has basically exactly the same stuff in it that my inbox has. Just a bunch of random emails from services that I signed up for an account on or bought something from and none of which I particularly care about. There's not really much that I can tell differentiating what gets marked as spam or not either.