• 0 Posts
  • 9 Comments
Joined 9 months ago
cake
Cake day: February 27th, 2026

help-circle





  • I’m not too concerned, for example, if they have to check their spam folders. As long as the email still lands.

    In that case, it really isn’t that much of a hassle. A basic mail system isn’t that complicated to set up (just make sure you have proper authentication and such, don’t host an open relay!). I actually did this not too long ago, using maddy, which unlike the traditional postfix+dovecot setup (which I had also been looking into) means you don’t even have to host separate services for SMTP and IMAP, and it also automates most additional things that are necessary nowadays for you, like TLS, DKIM, DMARC, and so on. Not quite everything though, there’s still stuff needed to do manually, mostly to set the SPF and DMARC records in the DNS, but it’s been working really well so far.

    And really, the only mail provider you have to worry about for putting your mails into spam is gmail. They’re the worst. (maybe microsoft-hosted outlook too, but I haven’t encountered anyone using that)


  • Unrelated to the actual anti-bot topic discussed here, but I would just like to mention this point:

    PROTOCOL = http+unix: because UNIX sockets are said to be faster locally but also because this avoids the painful management of ports. Also feels safer [as] there is no way to connect from outside.

    This is really underrated. I try to use this for all the server software I host, and not having to manage ports is absolutely great, along with knowing that nothing can connect to the service internally when it’s not supposed to.

    Except I actually go a step further and use systemd’s socket activation feature, which has a few additional benefits (like seamless restarts, no need for CAP_NET_BIND_SERVICE (my webserver and reverse proxy runs as a completely unprivileged user!), only starting the service once there is a request (this one is admittedly less useful), and having a quick overview of bound ports and Unix socket paths listed in the .socket file). Unfortunately, most programs need to be patched to support this, including forgejo (outdated codeberg link here because I had to set the forgejo repository on my own code forge to private earlier today because of scrapers…).



  • The information returned by whois depends on the registry. For example, most registries for European TLDs basically just show whether the domain is registered (I say “most” because I’m not sure whether it’s actually all or if there are exceptions, but I know .de is like this). In that case, there aren’t even “whois privacy” services available from registrars. For TLDs from other countries or gTLDs, this might vary.

    In either case, do note what the other comment says. Whois is not the only way to identify who runs a service.

    it returns a lot of information such as registrar name, abuse contact, creation date… even though i paid extra for “whois privacy.”

    If you didn’t pay for whois privacy, it would most likely return your actual name, email address, phone number, and home address instead. “Whois privacy” just means your registrar inserts their information into these fields instead, and forwards any mail they might get to you.