• 5 Posts
  • 386 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2023

help-circle
  • It’s not Nix-specific, but I use Mailcow-dockerized and it is completely hassle-free, been using it for 4 or 5 years now without a bobble (though I’ve run my own mailserver for 30 years).

    I would agree that a static IP is necessary, but I don’t have one and I get by, even without a PTR record. That’s probably due to a fairly small ISP with not many spammers having found it.

    Make sure you set up your DKIM and DMARC right from the start and pay heed to the reports. But I’ve never had to fight to get off a blacklist, even with new domains I’ve added to it.


  • Yes. You can just get by with 2 devices but you need to set expected_votes=1 in the cluster config somewhere, don’t recall where, and I’ve encountered issues with stability with that solution, seems like it’ll get undone though I haven’t used it for years to say if that’s still the case.

    The q-device will work on anything Linux that’s available when the second node is down. Not having the tie-breaker isn’t the end of the world, it just means you have to go in after you bring up the second node and start some things manually, and if you’re replacing nodes in a 2-node cluster, it’s much nicer to have the q-device.



  • It works well. I have my docker hosts on HA as well because they’re almost as important as the router.

    If you just use 2 nodes, you will need a q-device to make quorum if you have one of the nodes down. I have the tiebreaker running on my Proxmox Backup Server shitbox I3.

    Proxmox is basically just debian with KVM and a better virt-manager. And it deals with ZFS natively so you can build zpools, which is pretty much necessary if you want snapshotting and replication, which are necessary for HA.


  • I run OPNsense on a 2 node proxmox server and have for a few years now. I have HA set up and have had it fail over gracefully when I’ve been away and not even noticed it having failed over for more than a week. If I want to upgrade it, I snapshot it, and if I upgrade the host I live migrate it, and I’ve done this all remotely more than a few times with no issues.

    It takes some planning and I’d say you’d want a cluster (at least a pair of nodes) where you can do HA. But I wouldn’t do it any other way at this point. If you have only one port, you can VLAN it for using on both LAN and WAN.



  • If you’d done a docker commit on your earlier changes, they’d have stuck as well.

    The proper way to do this is to fork their image project and alter the nginx files that get incorporated in the build. Then you can run the stack with a build command instead of an image reference, and git pull your fork whenever there’s upstream merges. Or Action the fork to build an image for you every time it gets merged that you reference in your docker compose instead.















  • Might be easiest to just find a mail host that supports push notifications and keep using the mail client that works for you. Unfortunately, I don’t see how you’re getting a webmail client with multiple mailboxes without hosting that yourself with something like Snappymail. Maybe someone offers a paid and hosted Snappymail.

    I host my own mailcow server and enable notifications for mailboxes I want to get notified for via Pushover. I have Snappymail in the stack, but rarely use it because I like K9 on mobile better.