Live data from Hacker News

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

github.com

1–10 of 115 posts

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

#3
post #2

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

The relevant issue: https://github.com/foxcpp/maddy/issues/19

> Status update: JMAP is a big complex protocol that is not used by any popular clients and has no server libraries available for Go. IMAP is a big complex but also widespread protocol that is well-known, supported by any email client and has server library available for Go. Some of IMAP disadvantages come from incomplete client implementations, not protocol flaws, as JMAP developers want to convince you. I do not expect wide JMAP adoption in next several years, therefore the decision was made to prioritize improving IMAP implementation.

> If somebody insists on having JMAP, I recommend looking at Cyrus email server, perhaps write a Go library for its SASL delegation protocol so it could be used with maddy just as easy as Dovecot.

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

#4
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/alps

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

#6

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?

I run my own mail server and have never experienced such issues. The important thing is that your mail server is not an open relay and you set up DKIM and SPF. Oh, and never run a mail server with an ip originating in a residential area, you'll get blacklisted almost instantly by virtually any mail provider.

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

#7

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?

I’ve been able to send to gmail and iCloud ok, but outlook/office365/hotmail has been a no-go, even after going though their self-service system to open up your IP address.

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

#8

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…

Most people don't realize, but you can actually send email from a custom domain with a free Gmail account.[0] You have to go through a 5-minute process for each sender address, but I used it fine for ~10 years.

I recently switched to Fastmail, and one of the features I like about them is that they support wildcard sender aliases, so if I sign up for a service with someservice@mydomain.com, when I hit reply to any emails to that address, it automatically sends from someservice@mydomain.com even though I've never specifically registered that identity with Fastmail.

[0] https://thedigitalnonprofit.com/use-gmail-own-domain-free/

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

#10

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?

It's hit and miss. I've been running hosted mail services for years, both for myself and for a handful of other people and businesses.

SPF and DKIM are pretty much required now, as are TLS/SSL. From there, it turns into a dice roll. Gmail is terrible about this; they have a totally opaque and very frustrating engine that sometimes filters messages into a junk folder and sometimes doesn't. Outlook.com uses a somewhat more traditional internal RBL, but they are happy to block network segments and they don't offer any way to query their blacklist or request removal from it, so you could do everything right but a neighboring VPS or IP will get you blacklisted anyway. Comcast will simply accept delivery of messages and then disappear them depending on an arrangement of the stars that I haven't quite figured out yet. And those old sbcglobal/Yahoo services users... just, uggghh.

A popular solution is to rely on a third-party service to handle your outbounds. Sendgrid specifically is really bad, they carry way too much junk traffic, so don't go with them if you decide to try this out.

I have a post banging around in my head that's titled "Email is fractally broken", and getting outbound non-spam messages to reliably land in other people's inboxes would be a significant part of that writeup.

Post reply on HN