Live data from Hacker News

Maddy: Composable all-in-one mail server

maddy.email

11–20 of 122 posts

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

#11

Unrelated but: what VPS hosts are reliable for email? I've had trouble with Linode being blocked in the past. I'm aware Google Cloud blocks port 25. I haven't tried EC2 but I assume the worst.

I've run mail servers on EC2 before. You'll need to raise a request to remove the SMTP 25 restriction (both inbound and outbound), and also apply for a DNS reverse ptr update for that IP for it to work.

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

#12
post #7

I've been using Maddy now for about a month for my email, and it's incredible. The dev says it's not caddy for email – but in my experience, it's certainly been that easy. I've got to write a longer article about this, but self-hosting email is incredibly liberating. I now own my entire digital identity. I can work on open source projects with developers around the world completely while relying only on my own capabi…

What hosting service do you recommend to run it on?

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

#13
This is a great initiative. The last time I remember setting up a mail server using Postfix or Dovecot was around 2015.

It was a traumatizing experience. It rarely worked, all my email went to spam and I absolutely hated the amount of hackery and duct tape required to keep it working. Configuration files, missed emails...

It was so unpleasant, to this day I avoid messing with mail on servers at all costs. I'd much rather pay for Mailgun or some provider.

Lately I've been seeing an uptick of these apps making self-hosted email easier. Mail in a box, Maddy, etc. I will unconditionally support anything that makes doing this easier.

I'm not switching from GSuite, but I'm happy to see progress in the space.

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

#14

Unrelated but: what VPS hosts are reliable for email? I've had trouble with Linode being blocked in the past. I'm aware Google Cloud blocks port 25. I haven't tried EC2 but I assume the worst.

This doesn't answer your question, but I gave up on hosting my own email. I host my own other stuff where I can but email is just too much of a pain; constant delivery problems (especially to MS), spam is a pain to keep up with etc.

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

#15

This is a great initiative. The last time I remember setting up a mail server using Postfix or Dovecot was around 2015. It was a traumatizing experience. It rarely worked, all my email went to spam and I absolutely hated the amount of hackery and duct tape required to keep it working. Configuration files, missed emails... It was so unpleasant, to this day I avoid messing with mail on servers at all costs. I'd much ra…

Your mail will go to Spam too with Maddy, this is not about the MTA.

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

#16
post #7

I've been using Maddy now for about a month for my email, and it's incredible. The dev says it's not caddy for email – but in my experience, it's certainly been that easy. I've got to write a longer article about this, but self-hosting email is incredibly liberating. I now own my entire digital identity. I can work on open source projects with developers around the world completely while relying only on my own capabi…

How did you get around deliverability issues?

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

#17

Earlier quoted context omitted.

Mail is one of the easier things to backup IMO. It's just a directory if you use Maildir. Just tar it up with other important stuff on your filesystem you probably also want to save. No need for fancy "streaming SQLite replication."

I recall Litestream citing a ~3s streaming replication lag. What replication lag could tar-on-a-cronjob reasonably achieve for a moderate 5GB mail store? Even tar'ing isn't trivial: I've seen casing of people having missed preserving file permissions, making restoration difficult.

Replication and backups are usually different things. If you need replication, yes, backup tools won't cut it latency wise.

But proper backup tools like rsnapshot, borg, etc. pp. have no trouble correctly backing up email servers even at 10 or 100 times your mail store size.

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

#18
post #8

Earlier quoted context omitted.

I recall Litestream citing a ~3s streaming replication lag. What replication lag could tar-on-a-cronjob reasonably achieve for a moderate 5GB mail store? Even tar'ing isn't trivial: I've seen casing of people having missed preserving file permissions, making restoration difficult.

At 5G size you could do something with ZFS and tons of snapshots and zfs send.

Depends on how much latency/what big a time window for data loss between runs you can afford. We went from streaming cyrus-imapd replication to minutely send/receive for availability, but that introduces a 30-90 time window where data can be lost. Fine for us (esp. considering the reduction in ops overhead), but not necessarily for everyone.

(Backups are done by rsnapshot pulling from a snapshot, so we have another copy outside ZFS just in case.)

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

#19
Personally i use a mail server that's preconfigured and lives inside of a Docker container with all of the dependencies that it needs: https://hub.docker.com/r/mailserver/docker-mailserver ( GitHub: https://github.com/docker-mailserver/docker-mailserver ). With it, adding a new e-mail account is as simple as running a script with some parameters and it interoperates nicely with most clients such as Thunderbird or even the one built into Nextcloud (for a lightweight hosted solution without a separate app to manage).

It is pretty awesome to see new projects that try to improve the user experience for the system admins, for example, the Caddy web server and now the Maddy mail server. I'm not sure whether i'd have been able to set up a mail server the "old fashioned way", seemingly in line with the concerns of the other people here who have tried that more extensively. Somehow, while e-mail is super widespread and works decently for getting text information from place A to place B, it also feels a tad overcomplicated (the different components for sending/receiving mail, SMTP, IMAP, POP3, the sad need for anti virus scanning, SPF, DKIM, DMARC, the similarly sad need for anti spam protection).

That said, the containerized solution above has also worked nicely for me - i'll still probably use GMail/other hosted solutions for personal e-mail stuff and communication, but right now i've already switched over to using my own mail server for all of the automated e-mails that i need, such as from SonarQube and Zabbix, as well as GitLab.

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

#20
Configuration and setup wise, this looks somewhat simpler to setup than the comparable mailcow-dockerized. https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_inst...

I wonder how it compares in multi account management and spam, phishing, & virus blocking, is it extensible?

Post reply on HN