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
Do you know if 24h is the typical timeout for re-trying to send an email. How about I put a traditional email provider as second priority in MX records in case my server goes down? That should work, right?
The standard is to retry for 5 days before bouncing emails as undeliverable (and send a warning message that the email hasn't yet been delivered after 4 hours). However, every server can configure it to be whatever they want, so there's no guarantee.
You can't just use any old provider as a secondary mx, you need a server which is configured to accept mail for your domain but not try and deliver it locally. It's pretty simple to set up. The biggest issue is that you need the same spam protections on the secondary as on the primary, as spammers will send directly to the secondary to try and bypass spam protections.