• 1 Post
  • 46 Comments
Joined 1 year ago
cake
Cake day: July 23rd, 2023

help-circle
  • shrugal@lemm.eetoSelfhosted@lemmy.worldSimple mail server
    link
    fedilink
    English
    arrow-up
    8
    ·
    edit-2
    6 months ago

    I agree with everyone here that self-hosting email is never easy, but if you still decide to go down this route then here are two tips that I personally found very helpful, especially when you decide to host it at home:

    The first is to get an SMTP relay server. That’s just another mail server that yours can log into to actually send its mail, just like an email client would. That way you don’t have to worry about your IP’s sending reputation, because everyone will only see the relay’s reputable IP.

    Second is to configure a Backup MX. That’s an additional MX DNS entry with lower priority than the primary, and it points to a special mail server that accepts any mail for you and tries to deliver it to the primary server forever (or something like an entire week). So when your primary server is unreachable other sending servers will deliver mail to the backup, and it delivers the mail to the primary as soon as that’s back online.

    You can get these as separate services, but some DNS providers (like Strato for example) offer both with the base domain package. It makes self-hosting an email server much simpler and more reliable in my experience.










  • shrugal@lemm.eetoSelfhosted@lemmy.worldBeeper Self Hosting
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    8 months ago

    I started using their Signal and WhatsApp bridges today, probably one of the easiest setups I ever did. You just run a Docker container for every bridge, and login to your Signal/WhatsApp account by chatting in the app with the Matrix bot it creates.

    Literally takes like 5 minutes if you’ve used Docker before, and you don’t need a domain or forwarded ports or anything.









  • We really must have read two different posts and sets of comments. All they did was to ask for a foss license that makes for-profit endeavors give back some of the money they earn by using foss projects, just like they have to give back code under most foss licenses. There is nothing bad about that general idea imo, we’ve hopefully all heard about the problems os projects have to sustain themselves, even when they are being used by commercially successful businesses.

    They were then told by some levelheaded people that this doesn’t really work with foss alone, and so accepted that the best course of action would be to dual-license their work going forward.

    Everything else (including what you just wrote) is heavy projection and very toxic behavior by some people imo. Reading things between the lines that absolutely aren’t there, accusing the OP of nefarious motives without any valid justification, claiming that there is only one correct way to do foss or be against “the community”, and so on. That’s cult and herd behavior, it has no place in foss imo, and that’s pretty much exactly what the OP said when they called some of the more toxic responses childish.

    I would encourage you again to realize that there is more than one valid way to think about foss, and that people who don’t 100% agree with your way still aren’t bad people!




  • I believe the thinking should be the other way around.

    No one wants to store your code, and you shouldn’t store anybody’s code either. But suppose you have a group of people who want to collaborate on (or just mirror) a codebase, so they already decided to store it on their machines. This project gives them a decentralized tool to coordinate their efforts, and their code/issues/patches will be stored and accessible as long as they are interested in it.

    Like, the tool doesn’t give you a reason to use it, but if you have a reason then here is a tool to help you.