So I’m migrating stuff from my old server to a new provider and only thing left is email.
The problem is I used luke smith’s emailwiz script ( the script and setup itself isn’t a problem ) because it uses system users for managing users with dovecot and friends to setup a mail server.
So now I’m looking for a new email server to selfhost (preferably docker/podman) that in the future I can easilly migrate.Would also love if somebody has a reccomendation on how I could backuo and import emails from the old server.
NOTE: I use caddy as webserver, so the server should have a simple way on getting ssl certs, or abikity to easilly make use if caddy one’s.
You must log in or register to comment.
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.
Can’t beat Mox: https://www.xmox.nl/
I’ve never messed with it but I’ve heard mail servers are a pain in the ass.
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.
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…
It would be more reliable to use a ‘clean’ not blacklisted static IP.
But in theory you could just use ddns and update the IP. But I actually never tried it.
Mailcow comes ready out of the box. Just change the DNS entries according to Mailcow and you are good to go.
I’ve heard that using ddns for mail gets u into all sorts of IP blacklisting issues. I don’t even have a non cgnat iv4 and I’m not sure if email can work with an ipv6 only
Yes thats why i said in theory. I doubt that many residential IPs are blacklisted, but still not optimal.
IPv6 only works but there are probably many Mail Servers that are IPv4 only, so you will not receive mails from them.
If you are serious about it, rent a VPS or get a static IP on your residential connection.
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.
@muntedcrocodile @crony I used to run Exchange and have had various others for my 2 person house. Sometimes overkill. These days I don’t think I’d bother running mail at home, even on reliable hardware, a decent connection and with a static IP. Hassles with getting on/off blacklists even with all DKIM, SPF etc being in place are things I don’t want to deal with these days.
My incoming mails are a couple of bank notifications, monitoring alerts and notes from schools and sports clubs. A lot of system admin for not much actual use.
I might revisit it once the winter evenings come in.Extremely.
I have used mailinabox.email (I think there is a docker version of it) and am quite happy with it.
Stalwart is gaining momentum. I haven’t used it, but it’s worth a look. https://stalw.art/
Looks amazing. But the dual licensing scares me. The open variant could be artificially limited in functionality or could end up basic abandon ware.
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.
They use AGPL so even if they broke their promise and restricted features, it could still be developed further (even if no new features got added). NGINX also uses a dual license.
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’m the same way. If it’s split license, then it’s a matter of when and not if it’s going to have some MBA come along and enshittify it.
There’s just way, way too much prior experience where that’s what eventually will happen for me to be willing to trust any project that’s doing that, since the split means they’re going to monetize it, and then have all the incentive in the world to shit all over the “free” userbase to try to get them to convert.
This is probably the way, because a traditional “mail server” is actually 4-5 different servers working together.
- postfix for SMTP
- dovecot for IMAP
- amavis to plug in…
- spamassassin as anti spam
- clam-av as antivirus
And they can all be very easily misconfigured to break everything completely. Great learning experience though.
I’ve been using mailu for years without probelms
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.)
Another vote for Mailcow-dockerized. Used it for about 5 years now and never had a problem.
Mailcow is amazing.
Importing exporting i would just use any mailclient and drag-drop them over. Depending on how many Mailboxes you have to transfer.
I was going to ask if anyone had experience with Maddy, which is an all-in-one solution I’ve been eyeballing for a while.
Getting DKIM and postfix set up correctly was such a PITA, and then dovecot, I’m nervous about having to go through all that again and fretting about accidentally configuring an open relay, so I haven’t tried it yet. But it looks nice, and has been around for a couple of years.
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.
Thank you. I may try it; postfix seems to give me grief ever other update, like they can’t leave the damned config file alone.
If only this wasn’t asked 50 times in the past 7 days. SEARCH.
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.
