Live data from Hacker News

Self-hosting email like it's 1984

maxadamski.com

11–20 of 190 posts

Re: Self-hosting email like it's 1984

#11

[flagged]

Isn't that what DMARC is for?

DMARC is for setting policy to authenticate email which ends up becoming a requirement to even send mail to other providers, amongst an evolving set of policies which may cause your emails to be silently undelivered.

Re: Self-hosting email like it's 1984

#13
Modern email providers, especially ones offered by ISPs often have the same problems that people criticize self-hosted providers for. Even Google has problems. For example, I regularly order via companies that use Shopify. Now, all of the shopify emails are going straight to spam in Gmail, despite constantly marking them as not spam. (These even pass dmarc/spf/dkim etc, so who knows what's going on here.)

Email delivery and receiving is not hard, but it's inevitably going to be imperfect, no matter the provider you use. There are so many bad actors out there, it's surprising that it works as well as it does.

Re: Self-hosting email like it's 1984

#14

[flagged]

I self-hosted for well over 20 years, I did not throw the towel and I do not plan to. Self-hosting is a sign of pride. Neither my government nor my Prime Minister nor even my Ministry of Interior or Foreign Ministry can host their own email.

Last time I checked, only State Security self-hosted.

I was probably lucky, but I rarely had delivery problems. The last one was a couple years ago with Microsoft swallowing my emails and it was due to the combination of a fairly old exim and a TLS certificate verification quirk at *.protection.outlook.com. I found a fix in the form of a configuration option somewhere on SO.

In all fairness, there is very little maintenance involved, and whenever I have to do maintenance work, I take the opportunity to learn something new. Like this year, I decided to finally replace my aging Debian jessie setup by Arch Linux, and I rewrote all cron jobs as systemd timers.

I must admit that when I send a really important email, I check the mail server log if it went off without errors, but this does not bother me as checking logs manually once in a while is a good thing anyway.

Lastly, a piece of advice: treat self-hosting like a hobby and learn to enjoy it.

Oh and the very last thing: the person who designed Exim configuration for Debian deserves a special place in hell for all the hours wasted. If you set up Exim on Debian, just figure out how to use the upstream exim config and adapt it to your needs.

Re: Self-hosting email like it's 1984

#15

Here is my advice to anyone wanting to test out self-hosting email. Start by using your self-hosted email to sign-up for accounts. You don't have to use the email address for your personal correspondence Use Mail-in-a-box to get started [1]. You can literally set it up in a couple of hours by following the instructions and everything should just work. After a few years, you can think about switching your personal cor…

I've been running MIAB for a few years now with generally good success as an outgoing sender using a rented cloud machine and a "clean" reputation IP. I've had to email the Microsoft postmaster on one occasion when my emails weren't reaching Outlook users, but they were surprisingly helpful and it's been working fine for years now. It's a good learning exercise in setting up stuff like DKIM/SPF/DMARC.

That said - receiving account sign-up emails is the absolute biggest pain in the backside with Mailinabox! The greylisting anti-spam feature relies on bouncing unknown senders and waiting for a retry. The trouble is, many legit sites just don't bother retrying. So email verification for new accounts and 2FA-type stuff often takes ages to come through, if at all. MIAB stubbornly has no easy, mail user-facing way to temporarily disable spam filtering and it's a real PITA at times.

Re: Self-hosting email like it's 1984

#16

[flagged]

One problem in this are bad actors. German Telecom for example (t-online.de) only accepts mails from servers it whitelists.

To get whitelisted you have to apply with them and your domain HAS to have a website with an Impressum, your clear legal name AND an email that is NOT your domain for emergency contact. It is insane. If every provider would act like that, email would die in a month.

Re: Self-hosting email like it's 1984

#17
post #15

Here is my advice to anyone wanting to test out self-hosting email. Start by using your self-hosted email to sign-up for accounts. You don't have to use the email address for your personal correspondence Use Mail-in-a-box to get started [1]. You can literally set it up in a couple of hours by following the instructions and everything should just work. After a few years, you can think about switching your personal cor…

I've been running MIAB for a few years now with generally good success as an outgoing sender using a rented cloud machine and a "clean" reputation IP. I've had to email the Microsoft postmaster on one occasion when my emails weren't reaching Outlook users, but they were surprisingly helpful and it's been working fine for years now. It's a good learning exercise in setting up stuff like DKIM/SPF/DMARC. That said - rec…

Oh! That's what it is. I just thought some websites just took longer to send an email to my unknown domain.

I see that the only way to disable greylisting is to configure the underlying tool [1]. But it also means that SPAM will increase a lot.

[1] https://discourse.mailinabox.email/t/how-to-turn-off-edit-gr...

Re: Self-hosting email like it's 1984

#19

What about mail servers generally rejecting email (or marking as spam) from residential IP ranges? Decades of malware sending spam has spoiled self hosting emails. I needed some minimal mail delivery for user registration confirmation and password recovery, and I finally caved and just use some free service. It's okay since those emails are really, really, sparse in my case. But it sucks that email, this one old and…

Yeah, hosting on or at least tunneling through a commercial IP address is definitely required in order not to be flagged as spam. Personally, I chose the latter option of hosting my MTA at home but tunneling its traffic through a VPS in a datacenter. It's been working pretty well ever since, although I'm not sure it's worth the effort versus just using a cheap hosted provider.
Post reply on HN