I've had a lot of discussions with technical-minded peers about how the only real options for email on your own domain are fastmail or gsuite, which work out to about the same amount of money for a family of 5+, which is a surprisingly large amount (imo worth it).<p>This looks like something worth combining with alps[0] for easy self-hosted email. I might give it a go and ditch gsuite!<p>[0] <a href="https://git.sr.ht/~migadu/alps" rel="nofollow">https://git.sr.ht/~migadu/alps</a>
When I last looked into setting up my own email server, I read that your messages ending up in the spam folder was almost inevitable if the receiver is using a major host (Gmail, iCloud etc.)<p>Is that still an issue?
Another email server like this one that I have used extensively is WildDuck[1] It's written in NodeJS, and is excellent and remarkably simple.<p>[1] <a href="https://github.com/nodemailer/wildduck" rel="nofollow">https://github.com/nodemailer/wildduck</a>
This server seems really promising as it integrates all required functionality into one application, where as compared with most other MTA's (postfix, sendmail, etc) its about a 20 step process to get it all setup correctly (dkim, spf, etc)
Question to those running own mail servers:<p>Putting aside issues with <i>sending</i> mail to recipients using third party providers, have you been able to <i>receive</i> mail reliably from (a) senders using third party providers or (b) senders running their own SMTP.
Hi @foxcpp.<p>Project site says "all-in-one" (one daemon) to replace postfix, etc. Like sendmail?<p>Please say more.<p>For 20+ plus years I've been advocating for postfix instead of sendmail style architectures.<p>I don't know what to call the "one task, one process" style of postfix. What's the opposite of monolithic?<p>This tension is replaying (again) in the web services vs monolithic architecture debate.<p>Ironically, I prefer monolithic web apps over web services based designs. Contradicting myself.<p>I'd like to better understand when each style is better suited to the task at hand.
Does anyone know of a mail server (imap) where the developper can be in control of the mail source? I wanted to expose one of our tool to mail clients, something that handles all the imap talk and gives you onread/onmark/ondelete/... events, but I found very little libraries or servers for that kind of usage
I strongly recommend looking into Chasquid:
<a href="https://github.com/albertito/chasquid" rel="nofollow">https://github.com/albertito/chasquid</a><p>Only SMTP though, for the IMAP part you need to use something else like Dovecot.
One other all-in-one solution which I use (and love): SNM [0]<p>Obviously only usable for NixOS zealots, but just import the class with your desired parameters and good to go.<p>But Maddy-like consolidation seems like the way forward. Setting up 100 moving parts is not always easy.<p>[0]: <a href="https://gitlab.com/simple-nixos-mailserver/nixos-mailserver" rel="nofollow">https://gitlab.com/simple-nixos-mailserver/nixos-mailserver</a>
A fullstack but simple mail server (SMTP, IMAP, Antispam, Antivirus...). Only configuration files, no SQL database.
<a href="https://github.com/tomav/docker-mailserver" rel="nofollow">https://github.com/tomav/docker-mailserver</a>
What's the license for project? It's a bit odd to see a serious opensource project without any license specified as it prevents adoption for at least some of potensial users. I for example pay close attention to licensing as a personal user. It's just too risky to invest my time learning to use project which can any time in the future become paid or restricted in other way.