• 2 Posts
  • 72 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle


  • I have self hosted my email since 2006. I gave up on self hosting outgoing mail in 2021, but I still keep the server up for incoming mail, and still set up throwaway accounts on there.

    The hard part of hosting email is getting Google and Microsoft to accept outgoing mail. Tons of businesses that do not have visibly outlook .com or gmail .com addresses are still hosted by those servers.

    I had SPF, DKIM, and a static datacenter IP address with no reputation problems. I still couldn’t get through to Microsoft, not even in people’s junk mail directory, until they manually whitelisted my address. Microsoft didn’t allow them to whitelist a whole domain. Google was a little easier, but they added new demands monthly.

    In 2025, I can’t get reliable delivery to gmail .com addresses even sending from a hotmail .com address in the outlook .com web interface.



  • Limonene@lemmy.worldtoSelfhosted@lemmy.worldHow to selfhost with a VPN
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    2
    ·
    3 months ago

    Not sure how much you’re paying for your VPN, but a virtual private server can be had for about $5 per month. You’ll get a real IPv4 address just for you, so you won’t have to use non-standard port numbers. (You can also use the VPS as a self-hosted VPN or proxy.)

    $5 per month doesn’t get you much processing power, but it gets you plenty of bandwidth. You could self-host your server on your home computer, and reverse-proxy through your NAT using the VPS.













  • My favorite is Debian, with systemd uninstalled. At this point, you can’t install Debian without systemd, but you can uninstall systemd after OS installation.

    It used to be that most desktop environments in Debian depended on libpam-systemd, which depended on systemd and systemd-sysv. More recently, desktop environments just depend on libpam-elogind and elogind which is only part of systemd, and allows you to use sysvinit.

    I prefer sysvinit mainly because I find it easier to create custom services out of my own programs. My success rate at doing this in systemd is 1/3, and in sysvinit about 10/10.

    I also had a problem where a Debian-based embedded system had some kind of broken NTP client running on startup, and due to systemd, I couldn’t figure out how to disable it. It would set the time to several years into the future, as soon as it first got a network connection on each startup.