Live data from Hacker News

Ask HN: The middle ground for email self-hosting?

news.ycombinator.com

21–30 of 105 posts

Re: Ask HN: The middle ground for email self-hosting?

#21
I have been selfhosting my email stack on a cheap VPS (~ $10) for many years now, probably since 2009 or so. I used to set up everything manually, but that was quite painful and there were some rough edges.

Nowadays, I just use mailcow (https://github.com/mailcow/mailcow-dockerized) for the setup part and have a much more polished experience. Email deliverability is not a problem. Generally, you just have to make sure to correctly setup DKIM/SPF (and DMARC) and check if your IP is on some blacklist. You can get it removed easily. (Edit: Also required is forward-confirmed reverse DNS, see below).

There was one provider that denied incoming mails from me, even though I got the IP removed from every blacklist I could find. I wrote a short mail to the admin contact and got told I had to host a web page with contact information on the same IP. Since being whitelisted there, everything works like a charm, couldn't be happier.

Re: Ask HN: The middle ground for email self-hosting?

#22
I've done this with Amazon SES, which is PAYG and costs me pennies.

https://www.pxeger.com/2020-07-02-hybrid-cloud-email-with-am...

It is a bit overcomplicated, because I also set up SES to receive email, but I could run that instead with an ordinary Postfix server. It would be much simpler for outgoing only, I think

Re: Ask HN: The middle ground for email self-hosting?

#23
I do outbound email for my domain from a generic Gmail account, where my domain address is added as an alternate "Send mail as". This gets sent through Mailgun's free SMTP.

Incoming email to my domain is forwarded through Cloudflare's free service to the generic Gmail account.

This seems to pass all quality checks to avoid being sent to spam.

Re: Ask HN: The middle ground for email self-hosting?

#24
post #18

I just don't understand the attraction of self hosting email. The pain seems extreme, even for those who understand the considerable number of nuances. To me the happy middle ground is email on your own domain but using an existing provider such as G / MS or whoever. That way you've got control but don't need to worry about the pain. It does require paying for but really on balance not much. If you're spending more t…

> I just don't understand the attraction of self hosting email.

For several years I’ve hosted in the “middle ground” sense described by the OP, running my own incoming mail server and relaying outgoing mail through a big provider.

The main benefit for me (compared to using a big provider with my own domain) is personal privacy. When I used Google for mail, Google had access to so many pieces that make up my personal life: Purchase receipts. Flight itineraries. Conference registrations. Emails from my university. Emails from my realtor. Utility bills. Notifications for subscribed forum threads, GitHub repositories, Wikipedia pages. Whatever newsletters I chose to subscribe to. Theoretical access to any site with password reset by email. Running my own MX eliminates Google’s access to most of these things.

There are other some other benefits too. Free infinite aliases I can use to sign up on any website. No fear of dependence on features that might get paywalled. No sudden danger of having to migrate data to another provider.

> If you're spending more than an hour a year maintaining your self hosted email (which you will, big time!) then your Google Workspace / O365 is paid for.

Reducing my data footprint is something I care about enough to spend my spare time on.

Re: Ask HN: The middle ground for email self-hosting?

#25

I have been selfhosting my email stack on a cheap VPS (~ $10) for many years now, probably since 2009 or so. I used to set up everything manually, but that was quite painful and there were some rough edges. Nowadays, I just use mailcow ( https://github.com/mailcow/mailcow-dockerized ) for the setup part and have a much more polished experience. Email deliverability is not a problem. Generally, you just have to make s…

> I wrote a short mail to the admin contact and got told I had to host a web page with contact information on the same IP.

Interesting. Was that just to prove to that particular provider that you, the emailer, own the domain? Or is it some more widely used (beyond that provider) practice?

Re: Ask HN: The middle ground for email self-hosting?

#26
post #18

I just don't understand the attraction of self hosting email. The pain seems extreme, even for those who understand the considerable number of nuances. To me the happy middle ground is email on your own domain but using an existing provider such as G / MS or whoever. That way you've got control but don't need to worry about the pain. It does require paying for but really on balance not much. If you're spending more t…

The problem with google email hosting is you can no longer use that account for many of their services such as nest. They just don't support it. Same with google voice. I of course could create another gmail but that defeats the purpose of having my original email, I want everything in one place. If they fixed this I would say it's the best option.

Re: Ask HN: The middle ground for email self-hosting?

#27
post #8

I'm still wondering why there's no go-to choice to spin up a docker container that has everything preconfigured.

Because the problem is mostly about the reputation of the IP address. Setting up an email server is somewhat easy. Ensuring that other servers consider yours as legitimate that is the problem.

Spam is often sent from big providers, too. For several years I hosted my email the “middle ground” way (i.e., relaying outgoing mail via Google Workspace), and despite using DMARC correctly it was not infrequent that my emails would go to spam (even to GMail boxes) or never show up at all.

Obviously GMail is such a giant that email providers have to be very careful when blocking it, but enough spam comes from there that receivers clearly use some heuristics to block some of it. I’ve even received multiple rejection notices because the GMail server my email was sent through happened to be on a blacklist!

I switched last year to sending directly from my VPS. It was partly for privacy from Google, but moreso so I could enforce outgoing TLS. For the first few days they went to spam boxes or moderation queues, but I made sure they were rescued, and ever since I’ve had no deliverability issues sending to Google, some local ISPs, and even Microsoft (which seems crazy, as I never got a mail from my domain to show up in Outlook when I was relaying through Google).

I can only speak for my own experience, of course. But that is what I experienced.

Re: Ask HN: The middle ground for email self-hosting?

#28
The middle ground is to keep copies of all emails on your computer through a email client (via IMAP or POP), so that when you are locked out by your email provider, you can resume your business and communication with your contacts with your new email address. With IMAP, you can even upload your old emails to your next provider.

Re: Ask HN: The middle ground for email self-hosting?

#29
I know this is slightly off topic from OP's question, but I'm chiming in with one piece of first-hand advice:

You can self host mail alongside gmail/outlook on your own domain. More than one email service can run concurrently, without any problems.

That often overlooked fact allows you to quickly set up something like gmail on your domain, then use the trial period to see if you can self-host with any success. If you can, then you can shut down the trial, or move on to trial another paid service like 365 while you're still "trialing" your own host.

It really helped me make the transition.

Re: Ask HN: The middle ground for email self-hosting?

#30

I have been selfhosting my email stack on a cheap VPS (~ $10) for many years now, probably since 2009 or so. I used to set up everything manually, but that was quite painful and there were some rough edges. Nowadays, I just use mailcow ( https://github.com/mailcow/mailcow-dockerized ) for the setup part and have a much more polished experience. Email deliverability is not a problem. Generally, you just have to make s…

Lemme guess, Well-known Security?

As in `http://mydomain.example/.well-known/security.txt ?

https://securitytxt.org/

Post reply on HN