Hey-ho 👋

What is the best approach for selfhosting an email server with static IP or blocked port 25?

I’ve done it many times in many different ways, now doing it again and want to hear what is the best approach these days

My port 25 isn’t even probably blocked, I just prefer to use my vps to help it with this stuff

Any suggestions?

  • originalucifer@moist.catsweat.com
    81·
    10 months ago

    email is one of the only services i just gave up on (after rolling my own exchange for over a decade). its too annoyingly complex, tedious to do correctly for just yourself. its not worth it.

    • Gooey0210@sh.itjust.worksOPEnglish
      2·
      10 months ago

      I do it not really for myself, slow and steady i’m converting everyone I know to using my services

      Sounds impossible, but some people already are using almost the whole suite and are happy. More and more people are asking if they can join.

      The global sentiment is moving towards “tired of google”, “tired of paying for bad services”

      • chiisana@lemmy.chiisana.netEnglish
        3·
        10 months ago

        Self hosting email on non-mission critical domain for learning purposes might be okay if your intention is to get into the industry. Self hosting email for others on more production like setting you’re going to find yourself in a world of pain.

        All it takes is one missed email (be it not making into their intended recipient’s inbox, or them not receiving an important notice in their inbox) and you’re never going to hear the end of it.

        You’d also be liable for content your users send out from your servers — and I don’t mean the spam type, though if you get your IP blacklisted, your provider may want to have a word with you.

        I’d strongly advise against going down this path, but if you do, be sure to have ways to legally shield yourself from any sort of potential liabilities.