Then when you die I'll buy your domain, setup a catch all and scoop up your accounts.
Self-host your mail server
61–70 of 143 posts
Re: Self-host your mail server
#62The biggest problem with self-hosting a mail server is reliably being able to send email and have it be delivered to the recipient. Something I have been thinking about setting up is self-hosting a dovecot server so that all of my emails that I receive are on my system, but using another provider for sending email. I don't send that many emails, so there is not much privacy loss in regards to a third-party being able…
> but I still get the benefit of noone but me having access to my received emails.
Other than every smtp relay hop and any network tap along the way that could keep a copy. Hope you're encrypting and not worried about the envelope. Email is fundamentally not private. Self-hosting doesn't help all that much (though it may keep it out of certain companies' hands, aside from the emails copied to or sent from that provider)
Re: Self-host your mail server
#63Earlier quoted context omitted.
I take a middle path. Self-host receiving mail, and use smtp2go.com for outgoing
How do this work? Do you need to use two different programs to send and read email?
It's moslty due to how the protocol works. Sending and Receiving are asynchronous and may or may not follow the same path.
When sending the other side is the server, when receiving, you are the one. The protocol also has the concept of relaying, where message can go trough intermediary nodes.
So you can set one server for receiving email (yours) and another one for sending (smtpgo).
For actually reading, the server for receiving need to deliver the message (either built-in feature or through a program) to the correct mailbox. That would probably means writing it on disk somewhere. And then you need to use a mail user agent (MUA) to read that file. Protocol like imaps and pop3 are for transfering your inbox to another computer, not for receiving or delivering email.
Re: Self-host your mail server
#64I ran my own self-hosted email server from 2008-ish to 2018, and I would highly recommend against doing it! Especially when Fastmail and Proton are so cheap. I was running Postfix+Dovecot+Seive+SpamAssassin+Fail2ban+certbot+spf+dkim+reverse-ip+ It worked! Receiving email was overall pretty easy. I know I also did things the "hard way" by ad-hoccing all that together, and today there are a lot more out-of-the-box solu…
I take a middle path. Self-host receiving mail, and use smtp2go.com for outgoing
Yes, I do something similar (with Amazon SES in my case) but only for domains I know are problematic (Microsoft-hosted domains are the main difficulty - I've never had issues with eg Gmail).
Re: Self-host your mail server
#65I ran my own self-hosted email server from 2008-ish to 2018, and I would highly recommend against doing it! Especially when Fastmail and Proton are so cheap. I was running Postfix+Dovecot+Seive+SpamAssassin+Fail2ban+certbot+spf+dkim+reverse-ip+ It worked! Receiving email was overall pretty easy. I know I also did things the "hard way" by ad-hoccing all that together, and today there are a lot more out-of-the-box solu…
That’s something I have hard time explaining to the business.
Yea we do all the best practices but still no one can guarantee 100% deliveries. Just not possible for e-mail.
Yes we can have 100% over a year but after that it still is a lottery, can’t say anything about future not having suddenly 40% not delivered
Re: Self-host your mail server
#66I was going to self host my email server, but somehow my email provider (Migadu) is cheaper than a VPS ($19 USD per year) and offers custom domains, catch-all, and unlimited addresses.
Re: Self-host your mail server
#67Re: Self-host your mail server
#68I ran my own self-hosted email server from 2008-ish to 2018, and I would highly recommend against doing it! Especially when Fastmail and Proton are so cheap. I was running Postfix+Dovecot+Seive+SpamAssassin+Fail2ban+certbot+spf+dkim+reverse-ip+ It worked! Receiving email was overall pretty easy. I know I also did things the "hard way" by ad-hoccing all that together, and today there are a lot more out-of-the-box solu…
Had no problems at all self-hosting for two decades; then a provider went bust and I lost my static IP block, and with it its two decades of reputation.
I still self-host, but now I cheat for deliverability: route the problematic destinations (I'm looking at you, Outlook) through Amazon SES. At a few cents for five-figure numbers of emails, it's as close to free for personal/vanity email quantities as it gets to have someone whose full time job it is to make sure outgoing mail stays deliverable on your side while still keeping everything else under your control.
One thing to note is that Amazon are not very good at keeping amazonses.com up to date, so despite including it you can't set DMARC to hard-fail SPF or you will have mail bounce days.
Re: Self-host your mail server
#69I ran my own self-hosted email server from 2008-ish to 2018, and I would highly recommend against doing it! Especially when Fastmail and Proton are so cheap. I was running Postfix+Dovecot+Seive+SpamAssassin+Fail2ban+certbot+spf+dkim+reverse-ip+ It worked! Receiving email was overall pretty easy. I know I also did things the "hard way" by ad-hoccing all that together, and today there are a lot more out-of-the-box solu…
you can check your delivery rate with services there are lots that are free to check and they also offer to "warm" your reputation. I have not done that yet (money!) and outside this: - Outlook.com consumer mail addresses you can still get >99% delivery rate if you have spf, dkim and all the new cool stuff. So no, please DO NOT recommend against doing it because ONLY if mail stays a decentralized service providers wi…
Running your own email infra is not at the same level as the usual “self hosting”. Not to mention that email can be critical and missing an important email can burn a lot. Why put in that much effort on your free time, and take the risk?
You don’t build your own fridge. If it’s important and not your strong suit, pay someone to do it for you.
Re: Self-host your mail server
#70I'd run my own email server since the early 2000's - in several forms over time. A VA Linux 2U rack server that I got from work (noisy, overkill), a personal Mac Mini (Frankenstein macport upgrade-resistant), and now a single-node k8s instance with everything neatly managed (an excuse to really dive into k8s from the ground up).
I use dyndns to handle IP changes (incredibly rare with Frontier FIOS, actually). I use mailhop.org to handle secondary MX records in case my machine is down (as well as mail filtering) Everything else is postfix, spamassassin, dovecot imap
It's not a trivial system, and it took a while to get everything working how I wanted. It's a terrific learning opportunity, but it's by no means simple to mentally model the process of all that happens inside.