Live data from Hacker News

Maddy: Composable all-in-one mail server in Go

github.com

101–110 of 115 posts

Re: Maddy: Composable all-in-one mail server in Go

#101

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). This looks like something worth combining with alps[0] for easy self-hosted email. I might give it a go and ditch gsuite! [0] https://git.sr.ht/~migadu/alp…

With mailcow [0] it's pretty simple to setup your own email server in about half an hour with all the security included and having your email not being treated on reception as spam. It also ships with a webmail interface (SOGo [1]), rspamd UI and an admin interface for your server. I used to be a Kolab [2] user and "promoter" for many years but the project seems stalled a bit recently and although it is still being w…

The recent addition of FIDO to mailcow seems pretty exciting! https://mailcow.email/2020/11/16/welcome-fido2-web-authentic...

Re: Maddy: Composable all-in-one mail server in Go

#102

Earlier quoted context omitted.

I recently set up simple standard setup (postfix/dovecot/spamassassin) and it works fine. There's small amount of spam, like few mails per week, nothing to worry about. I can receive and send mail just fine. Though I admit that for someone who did not tinker with UNIX for years, configuring this kind of setup might be daunting. Personal mail could be solved by some kind of daemon which provides SMTP, IMAP, built-in s…

I've been running my own mail servers for ~15 years and yes you can run your own, but the biggest issue I've run into is other servers blocking me as spam: https://battlepenguin.com/tech/how-google-and-microsoft-made... I still prefer to host my own though.

I've tried to self-host email for my domain a couple times over the past few years, and I always end up falling back to a paid host for this reason; I rarely use email these days, but when I do (or usually when I'm expecting an email from a recruiter or other business-related sender) I need some sense of confidence that it will go through correctly. The lack of ability to confidently send via self-hosted setup definitely feels intentional, which sucks.

Great article btw!

Re: Maddy: Composable all-in-one mail server in Go

#103
post #83
post #61

Earlier quoted context omitted.

alps was created by the same person who started maddy, by the way. It is not me. Just wanted to give a little tribute to the amazing person who put a lot of work into email libraries for Go: https://github.com/emersion/

Not sure if Maddy covers this use case specifically (I didn't see it covered in the documentation, but I figure it actually is possible). I'm hoping to use a Golang-based application as a simple SMTP Relay, which also allows for ranges of IP addresses to be whitelisted to connect openly to it from within our campus network. Basically, the scenario is as follows: a number of internal services are older and may not sup…

Haraka covers this. Though it's a NodeJS SMTP server.

Re: Maddy: Composable all-in-one mail server in Go

#104

Hi @foxcpp. Project site says "all-in-one" (one daemon) to replace postfix, etc. Like sendmail? Please say more. For 20+ plus years I've been advocating for postfix instead of sendmail style architectures. I don't know what to call the "one task, one process" style of postfix. What's the opposite of monolithic? This tension is replaying (again) in the web services vs monolithic architecture debate. Ironically, I pref…

Postfix's architecture is the classic UNIX style of "do one thing and do it well", of composable processes.

So it's not a monolith, it's a composite. If that makes sense.

Sure, the components of postfix are not standalone tools, they are very much like systemd. One codebase (monorepo, yaay, old is new), sharing a lot of common internal code.

In the end multi-process composite (like oracle and postgresql RDBMSes) or a multi-threaded monolith (like MySQL or anything that runs on a JVM) is not that big of a difference nowadays. Both can be performant, both can be maintained well/efficiently by big teams and by a one-man-army (see how postfix is mostly maintained by Wietse Venema).

Re: Maddy: Composable all-in-one mail server in Go

#105

Earlier quoted context omitted.

I recently set up simple standard setup (postfix/dovecot/spamassassin) and it works fine. There's small amount of spam, like few mails per week, nothing to worry about. I can receive and send mail just fine. Though I admit that for someone who did not tinker with UNIX for years, configuring this kind of setup might be daunting. Personal mail could be solved by some kind of daemon which provides SMTP, IMAP, built-in s…

I've been running my own mail servers for ~15 years and yes you can run your own, but the biggest issue I've run into is other servers blocking me as spam: https://battlepenguin.com/tech/how-google-and-microsoft-made... I still prefer to host my own though.

A lot of this is due to newness and perhaps bad IP reputation. You can fix the reputation by requesting your removal from blocklists. The newness should be fixed after a few years - have you run it on the same IPs for those 15 years? In my experience after a year or so the problems go away (admittedly this is on a much larger scale than personal email).

Re: Maddy: Composable all-in-one mail server in Go

#106
post #16
post #11

Earlier quoted context omitted.

It isn't even necessarily 'residential' IP's. It's IP's that don't have a valid reverse dns, preferably one that is also forward resolvable. Most ISP's won't let you set your reverse DNS on 'residential' connections, so it ends up being a blocker. Now you could set up a vpn tunnel to a vps provider that lets you set your reverse dns, and then things get a bit easier. So prereqs - 1) Valid reverse DNS on your sending…

You're right, that's the basic ingredient #1 I forgot to mention. Functional rDNS is essential. You don't want to have your mail server running at home anyhow. A friend of mine had a janky setup at home until I convinced him it's a bad idea.

> You don't want to have your mail server running at home anyhow

I do in fact want this. It may not be possible, but I definitely want it to be.

Re: Maddy: Composable all-in-one mail server in Go

#107
post #96

Earlier quoted context omitted.

There’s also Zoho Mail: https://www.zoho.com/mail/ — starting at €10.80/user/year.

I've been testing zoho mail for the last few months (in order to find a decent alternative to g suite, and not-so-expensive as fastmail)...and so far, zoho has been performing quite well. I certainly can not complain about the price; as i'm able to use their "lite" plan at $12 per user oer year.

Considered proton?

Re: Maddy: Composable all-in-one mail server in Go

#108

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). This looks like something worth combining with alps[0] for easy self-hosted email. I might give it a go and ditch gsuite! [0] https://git.sr.ht/~migadu/alp…

I use proton with my own domain.

Re: Maddy: Composable all-in-one mail server in Go

#109
post #51

Earlier quoted context omitted.

I've been using a docker mail server[0] pre-configured for years without issues. I switched from DigitalOcean to Vultr and finally landed on Hetzner. Always had no issues delivering or receiving messages from/to the big guys. I'm also addicted to watchtower[1] to keep it automatically updated without hassle. [0] https://github.com/tomav/docker-mailserver [1] https://github.com/containrrr/watchtower

I moved from DigitalOcean to Hetzner, and Gmail started marking all my emails as spam, most likely due to bad IP reputation. I moved to Zoho Mail [0] (at €10.80/user/month), which doesn’t have problems like these, and requires less work to manage. [0]: https://www.zoho.com/mail/

That's weird. I'm running a mail server at Hetzner for years now and never got a mail rejected. Maybe you just got bad luck with the IP, which could be flagged at Spamhaus, etc.

Re: Maddy: Composable all-in-one mail server in Go

#110

Hi @foxcpp. Project site says "all-in-one" (one daemon) to replace postfix, etc. Like sendmail? Please say more. For 20+ plus years I've been advocating for postfix instead of sendmail style architectures. I don't know what to call the "one task, one process" style of postfix. What's the opposite of monolithic? This tension is replaying (again) in the web services vs monolithic architecture debate. Ironically, I pref…

> What's the opposite of monolithic? The web's answers for a suitable antonym seem inappropriate [0] (all referring to "small" rather than "many parts". I reckon megalithic is the way to go. Although I've been hosting my own mail server (postfix/dovecot) for years I must admit that I treat most of its parts as a single black box. My head just doesn't grok the entirety of processes and the various sub components (spam…

Heh. Small chuckle, thanks.

Mono - one, lithic - stone. "One stone". It's in the name, right?

Post reply on HN