Live data from Hacker News

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

github.com

61–70 of 115 posts

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

#61

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…

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/

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

#62

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.

Currently the license is GPLv3, you can find it in the COPYING file.

There are some messy bits related to licensing because it was MIT licensed in the past (back then when I did not take this "little pet project" very seriously).

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

#63

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.

It's GPL: https://github.com/foxcpp/maddy/blob/master/COPYING

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

#64
post #57

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…

My current position is that spam filtering is a whole another problem space so I am not trying to address it now while Maddy is a "single man show". P.S. As far as I am aware, redis is optional for rspamd. I certainly run it for @hexanet.dev email without having redis installed.

Look into doing greylisting. I do that for my own setup, and I've found it easily cuts down on the spam by at least 50% and that's without even looking at the email.

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

#65
post #57

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…

My current position is that spam filtering is a whole another problem space so I am not trying to address it now while Maddy is a "single man show". P.S. As far as I am aware, redis is optional for rspamd. I certainly run it for @hexanet.dev email without having redis installed.

Rspamd falls back to sqlite if you do not have Redis configured

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

#67

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.) Is that still an issue?

Yes and no. It certainly is possible to get good deliverability, but you gotta play by the rules (which is: all the RFCs). But when you do, there are also a lot of poorly configured email servers out there that don't comply to the RFCs at all, so email services need some tolerance to processing email from badly configured sources. It is almost always a compromise.

It is easy to get an email server running initially, but hard to get all the auxiliaries (SPF, DKIM, DMARC, MTA-STS, TLSRPT, BIMI, etc) set up correctly. It's even harder to debug deliverability issues, since there is 0 feedback on why your email is not being delivered. To a point where it inspired me to build an email hardening monitoring/validation service [0].

At the risk of being downvoted by people who are frustrated by email deliverability (and it is frustrating, I know): when you have email deliverability issues, it is almost always because you did something wrong on your end. Remember that false positives in spam detection hurts the $EVIL_BIG_CORP receiver as much as it does to you as a sender.

[0] https://www.mailhardener.com

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

#68
post #2

Kinda disappointing there's no JMAP support. I understand why, though.

As soon as there’s an IMAP/JMAP module that’s useable I’m going work on my email client concept again. I got far enough, receiving and displaying mail but IMAP is super frustrating to deal with. Maddy looks great though, I may start playing around with it.

I had similar issues where I wanted to remove IMAP complexity from client app, so I created a daemon proxy that sits between client and an IMAP server and “translates” REST API requests to IMAP commands: https://github.com/andris9/imapapi
Post reply on HN