Live data from Hacker News

How to Run Your Own Mail Server (2017)

c0ffee.net

161–170 of 339 posts

Re: How to Run Your Own Mail Server (2017)

#161
post #61

Slightly tangential, but is there something for RSpamd, where it can be run as just a blind mail relay? I.E. like this: Internet Email (SMTP) -> [MTA + Rspamd] -> [Real MTA + Inboxes] I ask because I've got a mail server system I'm happy with, but just want to bolt a better anti-spam filtering system on in front of it. Thanks.

Have you looked at assp, lots of parameters but does the job.

Re: How to Run Your Own Mail Server (2017)

#162

I run my own mail infrastructure. To say the least I wouldn't recommend it even to my worst enemies. It's horrible. Actually it's fine until it's not. Then your email doesn't work and you could be missing out on important communications. And then you're scrambling to figure out how the spammers managed to exploit your setup this time. And you have to learn a tonne of crap in order to manage it... and the text files!…

What stack are you using for SMTP and POP/IMAP? Do you use a secondary relay to hold you e-mail in case it goes down?

Re: How to Run Your Own Mail Server (2017)

#163

Earlier quoted context omitted.

smtp will eventually give up retrying, and if you're not willing to "always" respond within a few hours, you're going to lose emails.

Is there any server with such a short default? The RFC recommends at least 4-5 days.

I've seen Exchange bounce an email after receiving a 450 on the first attempt, although it's quite possible that was due to clueless Exchange admins.

Postfix default is 2d, Exim 3d, and sendmail 5d, last I knew.

Re: How to Run Your Own Mail Server (2017)

#164

Earlier quoted context omitted.

This is actually frustrating, e.g. with a large power outage when you expect an important message. I run my mailhost (single-node) since 2005 and I thought that I need HA more than once or twice. Sadly, I haven't figured out a proper fully-redundant solution. Syncing mailboxes with e.g. Syncthing is way too fragile. Recently, I wanted to experiment with DBMail + CockroachDB cluster but haven't yet found time for that…

Redundancy requirement was one of the reasons I started building WildDuck mail server. It can be set up with no-spof components, everything can be replicated. https://github.com/nodemailer/wildduck#no-spof-architecture

Whoa! That's very interesting, thanks a lot!

Haven't seen this project before - and I've tried to search for mail servers using document-oriented DBs, although not sure if I've searched specifically for MongoDB. Will definitely take a look.

Re: How to Run Your Own Mail Server (2017)

#165
post #149

> Before we dive in, an important caveat: You will become a sysadmin of your own mail server. This for me is the deal breaker. I say this as a sysadmin. It's all well and good running a single server but if that shits the bed then you have to deal with it immediately. So to run something that doesn't require 24/7 support I now have to run a cluster of servers. I'll also need something to manage those servers like sal…

"So to run something that doesn't require 24/7 support I now have to run a cluster of servers." My two most recent uptimes for my personal FreeBSD mail+web server were each over 1200 days. My current months sent-mail folder stretched back for years - which is to say, my (al)pine process itself was 3+ years old. No, you don't need a cluster of servers for your personal mail server.

Isn't this like saying:

> "I've never personally experienced a BSOD in Windows ME, so obviously it's incredibly stable. Those other people are just doing something wrong."

Re: How to Run Your Own Mail Server (2017)

#166
post #143

I run my own mail infrastructure. To say the least I wouldn't recommend it even to my worst enemies. It's horrible. Actually it's fine until it's not. Then your email doesn't work and you could be missing out on important communications. And then you're scrambling to figure out how the spammers managed to exploit your setup this time. And you have to learn a tonne of crap in order to manage it... and the text files!…

"And then you're scrambling to figure out how the spammers managed to exploit your setup this time." ... " ... writing a MTA with the goal of minimizing configuration and being secure and resistant to attacks by default. " As a 20+ year UNIX sysadmin and fellow owner of my own email infrastructure for 18 of those, I am surprised to read this and am not even sure what you are talking about. Can you explain what you me…

In the age of password leaks it is really common that email accounts are easy targets and get hijacked – most users are probably still using the same password for their email as they used for LinkedIn in 2012. So it might happen from time to time that an otherwise normal account suddenly sends 20 000 emails to hotmail.com unless you have somehow predicted that and configured the mail server to not allow it.

Re: How to Run Your Own Mail Server (2017)

#167
post #124

I've been pretty happy paying Fastmail to run my email server for me.

I've recently moved to Fastmail and I'm blown away by the service. Everything feel well thought, well integrated, their web interface is fast, their mobile app is great, they respect standards... I could continue all day.

From reading their blog[0] you can tell that they are passionate about email.

It is a bit pricey for a personal email with a few accounts, but I'm happy to give them their well-earned money.

[0] https://blog.fastmail.com

Re: How to Run Your Own Mail Server (2017)

#168

Would a better and easier alternative be to run your mail service through AWS?[1] Sure it's _hosted_ in a centralised place but since you're paying for it Amazon shouldn't have an incentive to harvest your data. [1]: https://aws.amazon.com/ses/

Use a cheap dedicated server. A Raspberry Pi 3 can do it. You can use a cheap VPS to tunnel a "proper" IP address to your home network.

Or rent a cheap dedicated server like Kimsufi or online.net for a couple of bucks per month.

Re: How to Run Your Own Mail Server (2017)

#169
Running your own personal, non-commercial server may be just fine. But if you’re business is pumping out volumes of email, no amount of DMARC, DKIM, SPF, CFL participation and fighting to stay off IP blacklists will prevent you from eventually succumbing to the user that clicks the Junk button to delete their emails. This will tank your domain’s reputation and get your emails routed to Junk (or silently discarded) for all recipients at the big ESPs like Gmail, etc. SPAM scoring is outsourced to companies like Symantec, CloudMark and others. They are the mail-zapping, score-keeping monoculture of the email ecosphere. You basically need a large company who will take your word for it that you’re not SPAMming and interface with the filtering industry on your behalf to de-nerf your domain once the Junkie McJunkbuttons of the Internet screw your reputation over.

Re: How to Run Your Own Mail Server (2017)

#170
post #168

Would a better and easier alternative be to run your mail service through AWS?[1] Sure it's _hosted_ in a centralised place but since you're paying for it Amazon shouldn't have an incentive to harvest your data. [1]: https://aws.amazon.com/ses/

Use a cheap dedicated server. A Raspberry Pi 3 can do it. You can use a cheap VPS to tunnel a "proper" IP address to your home network. Or rent a cheap dedicated server like Kimsufi or online.net for a couple of bucks per month.

> Before we dive in, an important caveat: You will become a sysadmin of your own mail server.

I don't want to become a sysadmin of my own mail server, however I'd appreciate not having my personal data harvested by webmail providers (e.g. gmail, outlook.com). Using a Pi or dedicated server would make me a sysadmin.

Using AWS email seems like a decent middle ground which isn't too expensive ($0.10 per 1000 sent and $0.10 per 1000 emails received).

Post reply on HN