Good mail server for selfhosting
-
A project ending as abandonware is always a possibility. One reason projects get abandoned is losing funding, which can be secured by using dual licensing and selling some features to businesses.
That is not my point.
Having a CE or OS version and an Enterprise Version can lead to conflict of interest. Do you add a feature to the OS Version or do you spend time on the Enterprise feature? There are a lot of examples, Emby is one, others are escaping me right now.
There are other models that work well like paid support etc. Nonetheless i will stay away.
-
I've never messed with it but I've heard mail servers are a pain in the ass.
-
If only this wasn't asked 50 times in the past 7 days. SEARCH.
-
I use OpenSMTPD for mail delivery, dovecot for IMAP, fdm for filtering and some tool I forget the name of for DKIM signing.
To bulk move mail around, just move the maildirs.
(Hosting email is a pain)
-
After 20+ years of hosting my email in a similar way (postfix...) I decoded to explore the "all in ones" like stalwart and mailcow.
Stalwart looks promising because its a new approach, supposedly more streamlined and efficient. Will post back in a few months.
I am not worried about stalwart dual license, the overall feeling seems to be of trust.
-
A forum is good for searches. Social media is good for blind repost and "me me me" posting.
That's life
So sad we abandoned the forum approach.
-
It's a bit unconventional maybe, but I vote
simple-nixos-mailserver- IF you are curious / willing to learn nix. It's essentially just sanely configured dovecot, postfix, rspamd.My config for those three combined is about 15 lines, and I have never had an issue with them. Slap on another 5-10 lines for Roundcube as a webmail client.
Since it's Nix, everything is declarative, so should SOMETHING happen to the server, you can be up and running again super quickly, with the exact same setup.
-
I use nixos on my desktop, the server is a debian one but might be good to install nix on it.
-
In that case I can really highly recommend it. Nixos on the server is fantastic anyways, and the only hurdle to recommending simple-nixos-mailserver is that most people are not familiar with nix...
-
Another vote for Mailcow-dockerized. Used it for about 5 years now and never had a problem.
-
https://mxtoolbox.com/ will help a lot with making sure you're configured correctly.
And look at Mailcow if you're nervous about setting up another server, it's bulletproof and mature.
-
I miss the old days, before you had to worry about spam.
I'm not OP, and I have everything set up fine now; Mailcow would replace what I currently have with the same software components, so I don't see any value there - for myself.
Something like Maddy is completely at odds with the Unix philosophy, and yet I've fought enough with postfix to dislike it enough to want to try an all-in-one. I dread the DKIM setup, though; that took so much time, and the mail server configuration wasn't the hard part. Maybe now I've got it configured for my domains, switching email server software will be easier.
-
Yeah, all the threads I came across when I looked into this were like "Self host everything! Except email" so I haven't looked into it.
-
Mailcow was effortless and I've never had to intervene in the stack. And after 20 years of fighting postfix and dovecot, that was a pleasant change. I can see why you'd want to try something different, but don't expect it to be easy.
-
This has been said over and over again. I have been hosting Mail now for over 2 years and have yet to encounter any problems. Although, i would not recommend to set it up manually and rather advise to use one of the 'all in one' suggested solutions here in the thread.
-
Don't u need a static ipv4 or something? I looked into it a while back even got the point of deploying a docker container but the config was so awful I gave up.
-
Same! Okay, not without problems, because running a mailserver isn't maintenance-free. But Mailu has been generally solid and it works with Docker. (And Podman, unofficially.)
-
I have used mailinabox.email (I think there is a docker version of it) and am quite happy with it.
-
In theory you could use an smtp relay.
Which pulls the messages from the relay and also sends for you.
This way you won't have to fiddle around with IP reputation.But you are still interacting with a cloud service...
-
I've been using Maddy for about a year. I haven't had any complaints, although my use case is very basic (running on bare metal, with just a handful of inboxes). DKIM is never pleasant but the Maddy configuration is straightforward enough.
