Live data from Hacker News

Self-hosting email like it's 1984

maxadamski.com

21–30 of 190 posts

Re: Self-hosting email like it's 1984

#21

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 deliv…

That behaviour is the whole problem. If you use a self hosted or small time email provider you're much less likely to have email blocked or filtered by aggressive anti-not-gmail filters.

Hilarious Gmail addresses send tonnes of spam so filtering by provider doesn't do much there days anyway. But Google insists to continue

Re: Self-hosting email like it's 1984

#22
Say I want to test the waters for selfhosting email, and I already have my how domains setup with SaaS like Google workspace and equivalent. Is there a way to setup mx records so that both google and my own server gets email for a while? This would be useful to test the waters over a few months before fully migrating

Re: Self-hosting email like it's 1984

#23

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 deliv…

> These even pass dmarc/spf/dkim etc, so who knows what's going on here.

Those have nothing to do with being spam, right? Spam is about content, those are about authenticity. Anybody can send authentic trash, or unauthenticated gold.

Re: Self-hosting email like it's 1984

#24
post #12

[flagged]

It's addressed in the article: > The elephant in the room is real-world deliverability. With self-hosting you risk not receiving mail or someone missing your mail. I accept this for my personal projects, but you may not. Keep this in mind.

I've never heard of "not receiving" as a problem. Does that happen in the real world? In what cases?

Re: Self-hosting email like it's 1984

#25
post #12

[flagged]

It's addressed in the article: > The elephant in the room is real-world deliverability. With self-hosting you risk not receiving mail or someone missing your mail. I accept this for my personal projects, but you may not. Keep this in mind.

Not self-hosting if you actually need email does not address the elephant that self-hosting email doesn't actually do email. I say this as someone who self-hosted for several years but had to give up because important emails were discarded. Until the deliverability issue is actually addressed, self-hosting is not viable for email.

Re: Self-hosting email like it's 1984

#27
post #26

Not sure why someone would go through the pain of cobbling up a self hosted solution based on Postfix when you have fully integrated solutions like https://stalw.art/ , which are a breeze to setup.

Because postfix is foss, will work with everything and for all time and if there's a problem with it you'll actually be able to fix it.

Re: Self-hosting email like it's 1984

#28
post #15

Earlier quoted context omitted.

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...

It's better to whitelist the domains you'll be getting mfa from.

Re: Self-hosting email like it's 1984

#29

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 can recommend Stalwart [1] which is a complete mail service contained in a single binary, that doesn't really have any external dependencies, and is really easy to install and update.

I've looked (and tried) a few other projects in the past, but Stalwart was the easiest to setup, and I haven't had any issues with it so far.

[1] https://github.com/stalwartlabs/stalwart

Post reply on HN