• 5 Posts
  • 267 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle
  • It happens every now and then. Support personnel claims that they are not blocking your address/IP even after you send them the message Microsoft servers send where it clearly states that your IP is blocked. Then you wrestle with the support for few emails, the problem magically goes away (which M$ support claims was never there) and then it comes back after few months or even few years.

    They (as a company) are just being assholes, there’s no technical reason nor explanation. And that’s one of the reasons more and more people should self-host and complain loudly every time they’re blocked without any particular reason.


  • Go for it. More people should. I’m running postfix+dovecot combo on a VPS running Debian.

    As others have already mentioned, you’ll need a server with static public IP address and a way to change DNS PTR record for it, so in practice for majority of people that means a VPS from (preferably) a reputable vendor. Then you’ll need to set up DNS records for your domain, MX and SPF are sufficient. DKIM and DMARC are nice to have, but not strictly speaking needed, at least for now.

    When configuring your SMTP service make sure that no one other than intended users can send mail trough it. That’s pretty much the most important thing if you want to stay out of blocklists. You’ll still end up in a few and it needs some manual work to resolve, but the longer you run your own server the fewer false positives there will be.

    Some will suggest mailcow or some other ‘all in a box’ service. They very likely work and may even work better than good’ol postfix, but I’d still recommend postfix (or exim, if you lean that way) because they really teach you the ropes and also they support maildir format for mailbox storage which makes it pretty trivial to move and backup stuff between installations as needed.

    When you get the setup running make absolutely sure your backups are in order. Email is so important for a lot of things that losing your inbox may be a costly mistake. Also set up some sort of server monitoring so that you’ll get alerts if something is not right. Email is pretty resilient, it can easily handle couple of hours downtime from a server, but the longer your downtime is the more you risk of lost emails (senders will get a notification that delivery failed, but it’s up to them to react for it).

    There’s a handful of different parts to figure out, but nothing is really that difficult. Sure, you’ll need to understand how email works under the hood and the whole stack is more complex than throwing a jellyfin docker image on your personal server but it’s very much doable. Have fun!





  • There’s been rumours about insufficient capacity on Microsoft cloud services around Europe for a while. Unofficial of course, and who knows how many “broken phones” has been on the chain before me, so don’t take that as a fact. However, Microsoft stated that the problem started when they increased capacity, so maybe some initial synchronization or load balancing starting up caused extra load on the servers already running on pretty much full load and caused cascading failure.

    Of course I don’t know for sure and I don’t expect we’ll get a full technical brief with details and the main reason is management problems no matter what’s the technical cause. I hope at least someone wearing a suit starts to think that maybe cloud isn’t really the answer to everything. And it’s not just 3654, a shit ton of different cloud services relies on AWS, Cloudflare and other players and if any of those goes down they’ll take considerable chunk of business critical infrastructure with them.


  • I do excactly this too. My personal domain has been around since 2008 and my setup has a few domains from friends too. I’m running ispconfig to manage the whole mess and it’s really not that difficult. Getting your server removed from blocklists every now and then is annoying but at least my emails aren’t feeding some marketing machine and, at least for the last 24 hours, my service availability is better than Microsoft can do.


  • Stalwart and other similar projects might be decent to use, but they lack one detail which is a deal-breaker for me: maildir format for storage. It’s really easy to move between installations and even between different servers, easy and efficient to back up, doesn’t require any fancy databases or anything to be in order and it just works. Sure, it might need few megabytes more memory and search times might be couple milliseconds longer but it just works. My personal maildir has been around from at least 2008 and it’s moved around between servers multiple times without any hiccups ever.


  • IsoKiero@sopuli.xyztoSelfhosted@lemmy.world•Do I need https on everything
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    14 days ago

    Is this a problem or does it not matter

    It’s not a problem, but it does matter. With plain HTTP traffic everything you send and receive from a given site is unencrypted, so anyone in the chain delivering your package can read what you’re doing, collect your passwords and do all kinds of shenanigans. If it’s just your local network which is secured from the public internet then it’s pretty much just you who can intercept that traffic and it’s generally fine, as you already have all the passwords and such. And if you connect to the services via VPN that takes care of ‘secured from public interenet’ -part of the equation.

    HTTPS is the same traffic, but encrypted with certificates. To achieve that you’ll need to have a server certificate and then browsers can use the public part of certificate to encrypt your traffic. With docker that’s commonly achieved either with docker-proxy or external proxy like nginx. Your computer already has a bunch of certificate authorities which it trusts and they are bundled in your operating system and/or browser. Without a trusted certificate your browser throws a warning about it, but if you proceed with ‘untrusted’ certificate the traffic will still be just as strongly encrypted as it would be with a ‘known’ certificate. The catch is that anyone can create their own certificates, so there’s no guarantee if the server actually is what it claims to be. For example I could sign my own certificate for gmail.com and offer that to users and steal their passwords. That would of course be trivial to figure out as the browser wouldn’t show the “good” lock symbol on address bar, but the certificate would be technically speaking a working certificate.

    Now, to get a certificate for your own services you need to either build your own certificate authority and add that to trusted list of your devices or obtain a certificate from a already known authority like letsencrypt. With letsencrypt (and other similar services) you need to provide a proof that you own a domain which you’re obtaining the certificate for, so with those you can’t get a certificate for gmail.com or any other random domain name. Letsencrypt uses ‘certbot’ tool to validate certs, other services ask for spesific DNS entry or something else for proof that the domain is actually yours. But the main part is that all the ‘commonly known’ certificate authorities work only on publicly available services and domains (a bit simplified explanation, but that’s roughly it).

    But once you have the certificate you’ll need to configure something on your network to use it. Actual best practice and configuration depends on the service you’re running. If your services run only on your local network and they are never allowed to public internet you’re likely fine to run everything without HTTPS encryption, but it’s still good to understand the differences and effects between unencrypted and encrypted traffic.






  • I don’t know about long term, but it’s running on my pile of virtual servers and does it’s job just fine. The openmediavault itself is a pretty good web-interface on top of Debian and it’s just configuring the underlying operating system so you can get exactly the same setup by writing configurations manually for the services. OMV is just a convenient tool to manage simple fileshares.

    I use it only for samba and wireguard, so can’t really say if it’s as solid with other extensions, but for me it’s been a decent tool for the job.




  • Just for comparison, my VPS server has ~20 active email boxes (postfix,dovecot,spamassassin,clamav), a few small-ish active wordpress sites (apahce,php-fpm,mariadb), radicale and some other smaller services running with 2 cores and 4GB RAM and it’s mostly just fine. Occasionally, specially during heavier updates on wordpress-sites, memory tends to get pretty full, but it’s still just fine. Tweaking memory cache for php (or running something else than php) would increase performance by a lot, but even without optimization the 5€/month VPS is quite capable to keep your internet presence around and on your own hands.


  • Nothing wrong with good old ssh. My VMs are different enough that building and maintaining ansible playbooks or something similar would be a bigger task than actually doing it in the traditional way. Maybe I could benefit by building simple playbooks to populate user accounts, ssh keys, smtp relay settings and other common things, but I don’t really set up new servers that often that it would justify spending time to set up tools for that.



  • My ISP offers unauthenticated SMTP for their customer addresses. It’s pretty heavily rate limited, but well enough for the occasional status email my system throws out. At least around here they are pretty common for residential customers, so that might be an option.

    Other possibility is to set up SMTP relay to your network and give it credentials to an actual email account (with SMTP support, which isn’t granted these days). It can take in emails from your network without credentials and throw them to the internet with your account. It’s pretty simple to set up, search for postfix + smarthost. Added bonus is that you can read the replies to that address too via your email provider services.