Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to Run Your Own Mail Server (2017)

c0ffee.net

Post reply on HN
Print view View original

321–330 of 339 posts

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

#321

Post by erikb »

lucb1e wrote: post #25

> on FreeBSD using Postfix, Dovecot, Rspamd, and LDAP. That seems like an awful amount of work / overkill. This is not a good introduction for a normal geek, and die-hard open source fans will figure it out without too much trouble anyway. Postfix is not the best choice for novices, FreeBSD is not the most well-supported/documented system just because it's not as popular as some others, and a directory service should…

"just install and run" is not admin friendly though. At some point you want or need to tweek your stuff. I'd argue the most logically tweakable is the most admin friendly.

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

#322

Post by saltybytes »

cpncrunch wrote: post #317
clan wrote: post #304

Earlier quoted context omitted.

In my experience live.com was an easy fix. But gmail was not. Even as a business user with support. Gmail rejects me as an ugly spammer at the gate when using IPv6 but not when using IPv4. My IP addresses are not listed in any public blacklists. And the Borg hivemind is not able to tell me why. Gmail support is friendly but have no knowledge of their filter nor an escalation path. The amusing part is they reject me a…

Did you fill in the delivery problem form? https://support.google.com/mail/contact/msgdelivery?vid=0-35... I had a problem with ipv6 myself with gmail, but the problem was that I just didn't have ipv6 fully set up on my server, so either SPF or reverse DNS wasn't working or something like that. I think I just configured sendmail to only use ipv4 and that solved the gmail issue.

"I think I just configured sendmail to only use ipv4 and that solved the gmail issue."

This was my experience, too. I took this advice [1] configuring postfix and Gmail started to accept my emails.

[1] https://christian.skala.me/blog/gmail-why-are-you-doing-this...

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

#323

Post by ryanlol »

kakarot wrote: post #266
ryanlol wrote: post #177

Earlier quoted context omitted.

>most users are probably still using the same password for their email as they used for LinkedIn in 2012 This is absolutely not true.

What? That is totally true. Most users that reuse passwords statistically did not rotate their passwords across all websites because most users that reuse passwords statistically do not rotate their passwords. We aren't talking about the overall Linkedin userbase, just that specific subset that reuses passwords for secure services.

>We aren't talking about the overall Linkedin userbase, just that specific subset that reuses passwords for secure services.

I have absolutely no idea what you mean.

>most users are probably still using the same password for their email as they used for LinkedIn in 2012.

Suggests that more than 50% of all users currently use their 2012 linkedin password as their email password, which is absolutely not true.

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

#324

Post by icelancer »

aaron_m04 wrote: post #296
icelancer wrote: post #268

Earlier quoted context omitted.

iRedMail will do this for you in one shot. I've done it. I still don't recommend it, but it's pretty easy.

Why don't you recommend it?

For the same reason(s) everyone else in this thread is crapping on running your own mail server. There's really no need to.

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

#325

Post by cpncrunch »

saltybytes wrote: post #322
cpncrunch wrote: post #317

Earlier quoted context omitted.

Did you fill in the delivery problem form? https://support.google.com/mail/contact/msgdelivery?vid=0-35... I had a problem with ipv6 myself with gmail, but the problem was that I just didn't have ipv6 fully set up on my server, so either SPF or reverse DNS wasn't working or something like that. I think I just configured sendmail to only use ipv4 and that solved the gmail issue.

"I think I just configured sendmail to only use ipv4 and that solved the gmail issue." This was my experience, too. I took this advice [1] configuring postfix and Gmail started to accept my emails. [1] https://christian.skala.me/blog/gmail-why-are-you-doing-this...

My issue was that I wasn't very familiar with ipv6, and my ISP (OVH) apparently gave my server a range of about 256 ipv6 addresses, and I didn't really know how to properly set up reverse DNS and SPF. After spending a day or two getting nowhere, I just decided to turn off ipv6 completely for the server.

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

#326

Post by saltybytes »

ilammy wrote: post #308
smolsky wrote: post #200

Earlier quoted context omitted.

I ran my own mail server (a few VMs in the cloud) for about five years. It's fun as you have control over accounts, aliases, forwarding, sieve tricks as well as backups. It's good to know that your broker and doctor's mail is delivered directly to your server and not Google. It sucks ass when your mail does not get through as GMail/Hotmail rejects a connection from the IP address your cloud company allocated for you,…

> It's good to know that your broker and doctor's mail is delivered directly to your server and not Google. That's only if your broker and doctor are not using Gmail or G Suite, otherwise your email (with them) is likely to be read by Alphabet regardless of your server setup.

Google announced recently that it will stop reading your emails since it doesn't pay off anymore [0]

[0] https://www.bloomberg.com/news/articles/2017-06-23/google-wi...

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

#327

Post by brongondwana »

Shoothe wrote: post #303
brongondwana wrote: post #300

Earlier quoted context omitted.

Yeah, it's still underway at the IETF. Last session we came close to finialising most of the documents in the UTA working group, which includes MTA STS. Meanwhile, there's ARC which is still in early stages of deployment, and hopes to fix the indirect mailflow problems of DKIM. (and of course there's JMAP on the client side, which is super exciting for those of us working on it)

I've seen some providers like Gmail already using MTA STS records and subdomains, but they don't read the records of my domains yet. Still it's an interesting solution. I'm disappointed in the mailing lists software and configuration "in the wild". Refusing to just change From address and put the original From into Reply To and breaking DMARC (that I've seen some operators just claim "is badly designed") is a very sa…

Having used a JMAP-style API for years, it works really nicely with batching in a way that other APIs I've worked with don't. Of course, as one of the original designers of JMAP, I'm bound to like it.

It would be quite easy to write a REST mapping for people who like more chatty protocols of course.

I'm not a giant fan of Foo/get either - it's a very recent change from the previous getFoos|setFoos|getFooUpdates naming, and there are pros and cons of the change. I try not to interfere too much with stylistic details like that though.

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

#328

Post by Shoothe »

brongondwana wrote: post #327
Shoothe wrote: post #303

Earlier quoted context omitted.

I've seen some providers like Gmail already using MTA STS records and subdomains, but they don't read the records of my domains yet. Still it's an interesting solution. I'm disappointed in the mailing lists software and configuration "in the wild". Refusing to just change From address and put the original From into Reply To and breaking DMARC (that I've seen some operators just claim "is badly designed") is a very sa…

Having used a JMAP-style API for years, it works really nicely with batching in a way that other APIs I've worked with don't. Of course, as one of the original designers of JMAP, I'm bound to like it. It would be quite easy to write a REST mapping for people who like more chatty protocols of course. I'm not a giant fan of Foo/get either - it's a very recent change from the previous getFoos|setFoos|getFooUpdates namin…

Thanks for the context!

Are there intentions to standardize JMAP under IETF?

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

#329

Post by brongondwana »

Shoothe wrote: post #328
brongondwana wrote: post #327

Earlier quoted context omitted.

Having used a JMAP-style API for years, it works really nicely with batching in a way that other APIs I've worked with don't. Of course, as one of the original designers of JMAP, I'm bound to like it. It would be quite easy to write a REST mapping for people who like more chatty protocols of course. I'm not a giant fan of Foo/get either - it's a very recent change from the previous getFoos|setFoos|getFooUpdates namin…

Thanks for the context! Are there intentions to standardize JMAP under IETF?

I'm literally RIGHT NOW writing up an email to the IETF EXTRA mailing list, following up from the email I sent as co-chair to the IETF JMAP mailing list about conflicts for our session in London at IETF101 in March.

We've been working inside the IETF on JMAP since Chicago (IETF98) in March last year.

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

#330

Post by Shoothe »

brongondwana wrote: post #329
Shoothe wrote: post #328

Earlier quoted context omitted.

Thanks for the context! Are there intentions to standardize JMAP under IETF?

I'm literally RIGHT NOW writing up an email to the IETF EXTRA mailing list, following up from the email I sent as co-chair to the IETF JMAP mailing list about conflicts for our session in London at IETF101 in March. We've been working inside the IETF on JMAP since Chicago (IETF98) in March last year.

Excellent! Is there a place to look for progress on this front? IETF mailing lists? jmap.io?
Post reply on HN