nixos-mailserver VS emacs-overlay

Hello. I have a server running NixOS. Webserver etc. works well and without problems. I tried to install the Simple NixOS Mailserver (https://gitlab.com/simple-nixos-mailserver/nixos-mailserver). After configure it the incoming mail works fine (IMAP: mail.domain.com on port 993) but the mails won't go out.

If you are familiar with NixOS, and like to have everything declared in Nix configuration, Simple NixOS Mailserver is very robust and easy to use. Have been using it for ~2 years.

https://gitlab.com/simple-nixos-mailserver/nixos-mailserver

I was able to set up a reliable email server using Simple NixOS Mailserver following the guide.

I just finished setting up my mail server on my nixos VPS (also huge thanks to nixos-infect devs), it was super easy. Just follow the guide and you have a working 10/10 mail server, I had no bumps along the way and everything just works. It even has flake support which I used. Check out the repo simple-nixos-mailserver/nixos-mailserver.

I’ve been using nixos-mailserver for a while now: https://gitlab.com/simple-nixos-mailserver/nixos-mailserver It’s using dovecot and postfix.

If your willing to do some tinkering I recommend simple-nixos-mailserver. I don't use nixos much, but I do find its very good at this one thing.

If you have the option to install NixOS (or convert the preinstalled distro), I can recommend Simple NixOS Mailserver. It is a complete solution (postfix, dovecot, rspamd), and can easily be extended with roundcube webmail.

I recently got into running my own NixOS server—setting up Nextcloud[0], a website[1], DNS server and most recently a mail server[2] were all incredibly easy, in fact, setting up DNS records is more involved than configuring a mail server on NixOS! This was all done on a server with less than 10 GB of disk space as well.

With additional software such as NixOps, personal servers can also be easily spun up and provisioned.

While inevitably there are rough edges if you look deeply enough, I think the default OOTB experience has been incredible for use on a server and as a day-to-day distro. Highly predictable and declarative configurations is the way to go.

[0] https://github.com/siraben/dotfiles/blob/ffaaacf8888a5c4167b...

[1] https://siraben.dev

[2] https://gitlab.com/simple-nixos-mailserver/nixos-mailserver

{ config, pkgs, ... }: let nixos-unstable = import { config = removeAttrs config.nixpkgs.config [ "packageOverrides" ]; }; in { imports = [ # Include the results of the hardware scan. ./hardware-configuration.nix (builtins.fetchTarball { url = "https://gitlab.com/simple-nixos-mailserver/nixos-mailserver/-/archive/nixos-21.05/nixos-mailserver-nixos-21.05.tar.gz"; sha256 = "1fwhb7a5v9c98nzhf3dyqf3a5ianqh7k50zizj8v5nmj3blxw4pi"; }) ]; disabledModules = [ "services/misc/mautrix-telegram.nix" "services/misc/matrix-synapse.nix" "services/misc/matrix-appservice-irc.nix" "services/web-apps/jitsi-meet.nix" "services/networking/jitsi-videobridge.nix" "services/networking/jicofo.nix" ]; nixpkgs = { overlays = [ # *snip* some local package definitions ]; config = { allowUnfree = true; packageOverrides = pkgs: { mautrix-telegram = nixos-unstable.mautrix-telegram; matrix-synapse = nixos-unstable.matrix-synapse; matrix-appservice-irc = nixos-unstable.matrix-appservice-irc; jitsi-meet = nixos-unstable.jitsi-meet; jitsi-meet-prosody = nixos-unstable.jitsi-meet-prosody; jitsi-videobridge = nixos-unstable.jitsi-videobridge; jitsi-videobridge2 = nixos-unstable.jitsi-videobridge2; jitsi = nixos-unstable.jitsi; jicofo = nixos-unstable.jicofo; util-linux = nixos-unstable.util-linux; # required by matrix-synapse }; }; }; # ...

I'm running matrix-synapse, nextcloud (in a nixos container), mumble, gitlab, vaultwarden, some game servers (i.e. Minecraft) and even my own mailserver with simple-nixos-mailserver.

The project uses this overlay: https://github.com/nix-community/emacs-overlay

What that means is if something is broken in Emacs, the community will fix it, and all I need to do is run `nix flake update` to grab the latest commit and then `nix run .#build-switch` to alter my system. Easy.

Thanks for the heads-up on the 404s! I've fixed those links.

In re: to org-agenda, I don't use that as much anymore. But I heavily, heavily using org-roam w/ org-roam-dailies everyday to build my own networked graph of notes. For tasks, nowadays I just use simple docs for projects and Asana to keep a catalog of everything.

Im a newish NixOS user, Ive used it like 20 times before but always quit because I couldnt debug errors, trying not to give up for the 20th time this time lmao; so Ive been trying to learn how to use overlays & flakes for a couple of days now. The ones I want to use/enable are: - Emacs-Overlay - Spicetify-Nix

Nix offers the same advantage through the use of emacs-overlay. Besides, Nixpkgs contains more Linux packages than any other distros. Depending on the user's needs, Nix is another option.

You can use this overlay to get the latest https://github.com/nix-community/emacs-overlay

Depending on your goals, emacs-overlay is also worth a look.

{ pkgs ? import {} }: ((import (builtins.fetchTarball { url = "https://github.com/nix-community/emacs-overlay/archive/master.tar.gz"; })) pkgs pkgs).emacsGit

One option is to install Nix and use emacs-overlay.

You can install Nix on your mac and use https://github.com/nix-community/emacs-overlay/, which supports all the existing tree-sitter-based major modes OOB.

Its great to see both eglot and tree-sitter being merged. However, I am unhappy about the state of 'emacs configurations/distributions' right now. I have been using Doom Emacs, but the development is pretty much stalled there [0], and I don't think there is any distribution that is keeping up with these cutting-edge features (compared to the NeoVim ecosystem, let's say). Somehow it feels like I was seeing a lot more activity about Emacs configurations two-three years ago.

> Compile EmacsLisp files ahead of time

Ooh, this is interesting. Hoping to see a derivation in https://github.com/nix-community/emacs-overlay soon.

[0] I am not complaining though as Doom was the main author's personal config from the get-go. I am just pointing out a void.